manage-project-docslisted

# Manage Project Docs Treat documentation as durable project state, workflows as state transitions, and executable checks as invariant proofs. Optimize for a future maintainer or agent returning without conversational memory. ## Preserve authorization - Read and obey the repository's existing agent instructions first. - Treat discussion, exploration, critique, resume, and audit requests as read-only unless the user explicitly requests changes. - Treat a direct bounded change request as implementation authorization for that change. - Require an explicitly accepted spec before starting a new project or a substantial, ambiguous, or cross-cutting feature. - Never promote a draft spec to accepted on the user's behalf. - Never change a normative contract merely to make implementation and prose agree. Surface the conflict and request a decision. ## Select one operation | User need | Operation | Read | |---|---|---| | Start or retrofit a documentation system | Bootstrap | [references/bootstrap.md](references/bootstrap.md) | | Return after lost context or prove the happy path | Resume | [references/resume.md](references/resume.md) | | Shape a material implementation slice | Plan | [references/plan.md](references/plan.md) | | Reconcile a completed implementation slice | Close | [references/close.md](references/close.md) | | Compare documentation claims with live evidence | Audit | [references/audit.md](references/audit.md) | | Turn a recurring failure into a reusable guard