MarkThatDownTemplates
Write the user problem, intended behavior, boundaries, and acceptance checks. A feature spec should make the result reviewable.
# Feature spec
Feature. [Name]
Owner. [Name]
## User problem
[Who needs what]
## Proposed behavior
[Trigger, action, and result]
## States
| State | What the user sees | Action |
| --- | --- | --- |
| Empty | [Content] | [Action] |
| Ready | [Content] | [Action] |
| Error | [Content] | [Recovery] |
## Boundaries
- [What is not included]
## Acceptance checks
- [ ] [Observable result]
## Open decisions
- [Question and owner]
An ordinary Markdown file. No signup required.
Name what starts the behavior and what changes. Include empty and error states when users can reach them.
Use a check that another person can perform. Keep unresolved decisions visible instead of quietly choosing behavior in the draft.
Reviewed October 2, 2026. Maintained by Humenhuk.
Original practical template. Adapt the examples to your own work.