Missions · 10 min
Run your first mission
Turn a normal request into bounded work with tests, review, and a useful handoff.Last updated August 2026Copy a starter prompt ↓
Describe the outcome like a teammate
A mission is not a ceremony. It gives the agent enough room to finish while keeping scope, verification, and stop conditions explicit.
Follow the workflow from request to verified change →
Ask your coding agent
Let's fix <small real problem> with Brief. First understand the relevant code and team rules, then make the smallest safe change. Reuse an existing pattern if there is one. Run the focused checks, review the diff, and leave me a short handoff with what changed, what passed, and anything still uncertain.
Know what good proof looks like
- The changed behavior works, not just the happy-path unit test.
- The diff follows repo and team rules.
- The agent names the checks it actually ran.
- Unknowns and skipped checks remain visible.
Try a different kind of mission next
Ask your coding agent
Use Brief to research <decision>. Fan out the independent questions, compare primary sources with our repo, and give me a recommendation with evidence, tradeoffs, and the smallest experiment.
Ask your coding agent
Use Brief as a PM, design, and content partner for <surface>. Inspect the current implementation and user flow, identify the highest-leverage layout or copy improvements, then implement and verify a focused pass.
Ask your coding agent
Dogfood Brief on the work we just finished. Look for moments where context arrived late, the mission was vague, or proof was weak. Fix clear product or documentation issues and save larger ideas as follow-ups.
Was this guide useful?Help us make Brief easier to learn.
Ready for another workflow?Choose your next mission →