yuri-semenenko Context Brief
Create a bounded brief that lets another pass work from evidence instead of chat history.
Process
- State the goal in one or two sentences.
- Capture constraints: scope, non-goals, deadlines, risky areas, and user preferences that affect execution.
- List relevant files, commands, tickets, PRs, docs, and external references with why each matters.
- Summarize observed facts separately from assumptions.
- Identify open questions that block safe implementation or review.
- Recommend the next action: implement, investigate, review, ask the user, or stop.
Output
Use this shape unless the user asks for another format:
## Goal
<what needs to happen>
## Constraints
- <scope, non-goals, verification, timing, ownership>
## Evidence
- `<path or command>` - <why it matters>
## Facts
- <verified fact>
## Assumptions
- <assumption and why it is acceptable or risky>
## Open Questions
- <question or "None">
## Recommended Next Step
<one concrete next action>
Keep the brief compact. Do not paste large file contents, transcripts, or full diffs. Link to local files and quote only the lines needed to make the handoff actionable.