product-docs-first

# Product Docs First > **Style:** Mode-B-lite. **Artifact-gated** — acts only when `docs/<app>/product.md` exists or the operator asks to create one. ## Purpose Design product documentation per app *before* writing code, so planning and implementation build from a clear product intent instead of guessing. Ingests operator research and the North Star (if present). ## When to invoke - Operator starts a new app and says "design the product docs first", "write product documentation", "what should this app do". - `docs/<app>/product.md` already exists (read it to ground planning). - Operator dropped research in `docs/<app>/research/` and asks to turn it into product docs. ## Do not invoke when - No `docs/<app>/product.md` AND the operator did not ask to create one → silent no-op; do not auto-create. - Mid-implementation edits (planning already done). - Small bug fixes, refactors, copy-only changes, narrow technical tickets, or already-scoped implementation work with no long-lived product-intent change → do not expand product docs (FR-23 / `flow-skills/documentation-budget/SKILL.md`). ## Required inputs | Input | Where it lives | If missing | |---|---|---| | Product intent (operator answers) | chat | ask in chat (FR-19); do not invent | | Research (optional) | `docs/<app>/research/` | proceed without; note it | | North Star (optional) | `docs/north-star.md` | proceed; align if present | | Template | `templates/product.md` | stop; template missing | ## Procedure 1. **Gate...