Section 4 · Documentation
Living Docs & Exact Commands
Keep documentation relevant and practical. Give AI exact commands — not vague suggestions.
Minimal Living Docs Checklist
Before you merge or sign off a feature, confirm documentation matches reality — not what you intended at the start of the sprint.
Minimal "Living Docs" Checklist
requirements.md (or shaped spec) matches what you actually built.
plan.md / architecture notes describe the system as implemented.
tasks.md checkboxes done and traceable to requirements.
Tests, build, lint, or recorded acceptance proof — not “looks fine.”
Complete before merge: spec, plan, tasks, and verification must match reality.
File Roles
| File | Audience | Purpose |
|---|---|---|
| README.md | Human | Product overview — what this project is |
| requirements.md | Human + AI | Feature intent — our SPEC equivalent |
| constitution.md | Human + AI | Team rules — consistency vs flexibility |
| tasks.md | Human + AI | Atomic work units with verification |
| AGENTS.md | AI | Operational rules — commands, boundaries, structure |
Exact Commands — Not Vague Suggestions
Install
install dependencies
npm installBuild
make sure it builds
npm run buildDev server
run the app
npm run devLint
check code quality
npm run lintMaintenance rule
When scope changes, update requirements.md and tasks.md in the same PR. Docs that drift from code are worse than no docs.