SDSection 5 →

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

FileAudiencePurpose
README.mdHumanProduct overview — what this project is
requirements.mdHuman + AIFeature intent — our SPEC equivalent
constitution.mdHuman + AITeam rules — consistency vs flexibility
tasks.mdHuman + AIAtomic work units with verification
AGENTS.mdAIOperational rules — commands, boundaries, structure

Exact Commands — Not Vague Suggestions

Install

install dependencies

npm install

Build

make sure it builds

npm run build

Dev server

run the app

npm run dev

Lint

check code quality

npm run lint

Maintenance rule

When scope changes, update requirements.md and tasks.md in the same PR. Docs that drift from code are worse than no docs.