MarkThatDownTemplates
Write the intended outcome, scope, constraints, and decision owner. Use the brief to settle what success means before assigning tasks.
# Project brief
Owner. [Name]
Date. [Date]
## Outcome
[What should become possible]
## Why this now
[Evidence of the problem]
## In scope
- [Deliverable]
## Out of scope
- [Explicit boundary]
## Constraints
| Constraint | Effect |
| --- | --- |
| [Time or dependency] | [Practical effect] |
## Acceptance
- [ ] [Observable passing condition]
## Decisions needed
- [Question, owner, and deadline]
An ordinary Markdown file. No signup required.
Describe what a user or team can do after the project. A list of activities does not establish a successful result.
Record a changed constraint or decision. Keep the brief short enough for the decision owner to read before approving more work.
Reviewed October 2, 2026. Maintained by Humenhuk.
Original practical template. Adapt the examples to your own work.