---
name: code-task-brief-writer
description: "Turns a rough feature or bug idea into a scoped brief with acceptance criteria, so a coding agent delivers a clean first pass. Use when a developer has a rough feature, bug or refactor idea and needs a scoped brief to hand to a coding agent. Do not use for reviewing finished code or writing a long-lived project rules file. Related topics: AI, Coding, Productivity."
---

# Claude Code Task Brief Writer

Turns a rough feature or bug idea into a scoped brief with acceptance criteria, so a coding agent delivers a clean first pass.

## When to use

Use this skill when a developer has a rough feature, bug or refactor idea and needs a scoped brief to hand to a coding agent. Do not use it for reviewing finished code or writing a long-lived project rules file.

## Workflow

1. Ask the user for each input listed below in a single message, skipping any they have already given. Where options are listed, offer them, but accept other answers too.
2. Restate the goal in one sentence and classify the work type so the scope matches the chosen level.
3. Convert vague wishes and unsure points into explicit assumptions the agent can confirm or reject.
4. Write acceptance criteria as a checklist where each item can be checked by a command or an observable behaviour.
5. List what is out of scope, including adjacent cleanup that the scope level does not permit.
6. Add a verification section with the exact commands or steps, and confirm the brief fits on one screen.

## Inputs

- **One-line feature or fix** (free text, e.g. "Add CSV export to the reports page")
- **What is actually wanted** (longer free text)
- **Type of work** (choose one: New feature, Bug fix, Refactor, Performance, Tests)
- **Stack and framework** (free text, e.g. "Django 5 and Postgres")
- **Relevant files, commands or constraints** (longer free text)
- **Tests required before it counts as done** (choose one: Yes, No)
- **Scope** (choose one: Smallest change that works, Balanced, Thorough with cleanup)
- **Explicitly out of scope** (longer free text)

## Output

A pasteable brief with five headed sections: goal, context, acceptance criteria as a checklist, out of scope, and how to verify.

## Prompt template

Fill the inputs into this template and follow it as the full instruction.

### Coding Agent Task Brief

Turn a rough idea into a brief that a coding agent can execute well on the first try.

#### The task
- One-line feature or fix: {{One-line feature or fix}}
- What is actually wanted: {{What is actually wanted}}
- Type of work: {{Type of work}}

#### Context
- Stack and framework: {{Stack and framework}}
- Relevant files, commands or constraints: {{Relevant files, commands or constraints}}
- Tests required before it counts as done: {{Tests required before it counts as done}}

#### Scope control
- Scope: {{Scope}}
- Explicitly out of scope: {{Explicitly out of scope}}

Write the brief with these sections: goal, context, acceptance criteria as a checklist, out-of-scope list, and how to verify the change works. Make every acceptance criterion observable, for example a command that passes or a behaviour a person can see. Turn the unsure parts of the request into stated assumptions the agent may challenge. If tests are required, add a criterion naming which cases they cover. Keep the brief short enough to paste straight into the agent.

## Pitfalls

- Writing acceptance criteria like 'works well' that no one can check.
- Omitting the out-of-scope list, which lets the agent refactor neighbouring code.
- Hiding uncertainty instead of flagging it, so the agent guesses silently.
