docs-project

# Docs Project — engineering documentation («how») Use this skill to write the **engineering** documents: architecture, decisions (ADR), contracts, dev guides, tests, and the documentation map. Assumes the product docs exist (`docs-product`: VISION/PRD/ROADMAP/FEATURES). ## When to use - A project needs its engineering docs: README, ENTRY, ARCHITECTURE, ADR, tests. - User asks for "проектная документация", "архитектура документация", "adr", "инженерная документация", "контракты openapi", "engineering docs". - Contracts (OpenAPI/AsyncAPI) must be written **before** code. ## Do NOT use - For product docs (VISION/PRD/ROADMAP/FEATURES) — that is `docs-product`. - For the meta-guide (phases, levels L1/L2/L3, completeness checklist) — `docs-system`. ## Root documents | File | Purpose | Phase | Template | |------|---------|:-----:|----------| | `README.md` | Overview: what it is, stack, status, quick start, structure | 1 → 10 | `templates/project/README.tmpl` | | `ENTRY.md` | Entry point: "start here", navigation "topic → file", onboarding checklist | 9 | `templates/project/ENTRY.tmpl` | | `AGENT.md` | Runbook for the autonomous build agent: phases, rules, DoD, commit gate | 8 | — | | `DELIVERY.md` | Delivery gate: build/run/verify, what's in, what's NOT | 8 | — | | Legal/community | LICENSE, CONTRIBUTING, CODE_OF_CONDUCT, SECURITY | 1/9 | — | ## docs/ — engineering documents | File | Purpose | Phase | Template | |------|---------|:-----:|----------| | `docs/REFERENCE.md`...