Brief the task
one task issue goes in — the same task, in full depth, comes out
A plan names the work. A brief is the written, exact instructions for one task — what to build, which files, when to stop and ask — handed to whoever writes the code. The same conversation can usually keep going.
- What kind of tool
- Still fine in a browser chat — briefing is writing, not filesystem work.
- What you say to it
- Pick one task from the plan and ask it to turn that task into a brief: the exact boundary, the files it touches, how it gets verified, and when to stop and ask instead of guessing.
- What comes out
- A written brief — the durable instructions a coding agent works from, start to finish.
- What to look at in Studio
- The task moves from Todo to Ready once its brief exists.