prdlisted

@.claude/shirabe-extensions/prd.md @.claude/shirabe-extensions/prd.local.md # Product Requirements Documents PRDs capture WHAT to build and WHY -- the problem, goals, requirements, and acceptance criteria. They complement design documents (which capture HOW) and are the input for /design (which produces technical architecture). **Writing style:** Read `skills/writing-style/SKILL.md` for guidance. ## Artifact Lifecycle **Lifecycle:** Durable. Stays in `docs/prds/` after completion. PRD is durable because the requirements captured at PRD-Accepted time are the audit trail of what was promised. Future readers checking whether a shipped feature met its requirements need the PRD to remain in place. ## PRD Format See `references/prd-format.md` for PRD structure, frontmatter, lifecycle states, validation rules, and quality guidance. Load it during Phases 3 and 4. ## File Location PRDs live at `docs/prds/PRD-<name>.md` (kebab-case). No directory movement based on status -- stable paths keep cross-references durable and git blame readable. ## Repo Visibility Before writing content, detect visibility from CLAUDE.md (`## Repo Visibility: Public|Private`). If not found, infer from repo path (`private/` -> Private, `public/` -> Public; default to Private). Load the appropriate content governance skill: - **Private repos:** Read `skills/private-content/SKILL.md` - **Public repos:** Read `skills/public-content/SKILL.md` Public PRDs must not reference private artifacts. --- ##