docs-product

# Docs Product — product documentation («why» & «what») Use this skill to write the **product-facing** documents: vision, requirements, roadmap, feature catalog. Written from an idea forward — **before** (or in parallel with) engineering docs. ## When to use - A project needs its product docs: VISION, PRD, ROADMAP, FEATURES. - User asks for "продуктовая документация", "vision", "prd", "роадмап", "требования к продукту", "product requirements". - Requirements must become the input for engineering docs. ## Do NOT use - For engineering docs (architecture, ADR, tests, dev guide, map) — that is `docs-project`. - For the meta-guide (phases, levels L1/L2/L3, completeness checklist) — `docs-system`. ## Which docs belong here | File | Purpose | When | Template | |------|---------|:----:|----------| | `docs/VISION.md` | Why the product exists: audience, problem, value, principles, scope, long-term success | Phase 1 — first, stays stable | `templates/VISION.tmpl` | | `docs/PRD.md` | What we build: functional + non-functional requirements, priorities, acceptance criteria, success metrics, user stories | After VISION, before architecture | `templates/PRD.tmpl` | | `docs/ROADMAP.md` | What ships when: milestones, value per milestone, proof (metrics) | Phase 2+, updated each milestone | `templates/ROADMAP.tmpl` | | `docs/FEATURES.md` | Feature catalog + status (✅/📋) — the bridge to engineering | From requirements, kept current | `templates/FEATURES.tmpl` | The golden chain: **VIS...