Project Docs
Workflow
- At the start of substantial implementation or diagnosis, read
docs/CURRENT_HANDOFF.mdand only relevant sections of the stable documents. - Verify document claims against current repository evidence.
- During exploration or read-only review, report drift without editing unless the user authorizes changes.
- At task start, replace the current goal and next action in
CURRENT_HANDOFF.md. - After a verified milestone, replace current state and verification evidence; do not append a timeline.
- Before handoff, remove completed process details and leave one continuation-ready state.
- Update
BLUEPRINT.mdonly when product intent, users, scope, constraints, or acceptance change. - Update
ARCHITECTURE.mdonly when components, boundaries, data flow, verified commands, deployment, rollback, or risks change. - Before substantial delivery, run
python3 .agents/skills/project-docs/scripts/docs_lint.py.
Boundaries
- Current code, tests, configuration, command output, and user instruction outrank these documents.
- Keep BLUEPRINT at or below 160 lines.
- Keep ARCHITECTURE at or below 160 lines.
- Keep CURRENT_HANDOFF at or below 80 lines.
- Keep AGENTS at or below 90 lines.
- Git stores history. CURRENT_HANDOFF stores only the latest working state.