Appearance
Brief
What
A brief states the problem, goal, acceptance criteria, boundaries, risks, and verification.
Why
It prevents an implementation from silently becoming the specification.
When
Create one before non-trivial changes.
Example
See templates/task-brief.md.
Common mistake
Describing a preferred implementation instead of an observable outcome.
Checklist
- [ ] Scope and exclusions are explicit
- [ ] Acceptance criteria can be checked
Next step
Build a context pack.