prdlisted

# PRD — Author, Parse, and Review Requirements Write the contract that everything downstream depends on. The PRD is the single source of truth for every `Requirement`, `Feature`, and `Task` row in `state.db`. Nothing can be claimed until this document exists, parses cleanly, and clears the review gate. --- ## When to Use - Starting a new project — before any planning, scoring, or task assignment happens. - Revising the PRD after stakeholder feedback changes the scope or acceptance criteria. - Recovering after a scope change mid-project — re-anchor what the work is before resuming claims. - Before any invocation of `/fakoli-state:plan` — planning reads from a parsed PRD; authoring must come first. - When `fakoli-state status` reports `prd-status: draft` or `prd-status: none` and the project can't proceed. - When a co-authored PRD is ready for a formal review and approval step. **Do not use this skill to generate or score tasks.** Once the PRD is approved, proceed to `/fakoli-state:plan` for the task graph. This skill only authors, parses, and reviews requirements. --- ## Prerequisites `.fakoli-state/` must exist. Confirm before proceeding: ```bash ls .fakoli-state/state.db 2>/dev/null || echo "MISSING: run fakoli-state init first" ``` If `state.db` is absent, run: ```bash fakoli-state init --name "<project-name>" ``` Phase 3 commands used in this skill: | Command | Phase | Status | |---|---|---| | `fakoli-state prd parse` | Phase 3 | available | | `fakoli-state pr