← ClaudeAtlas

prdlisted

Settle what a feature must do and how anyone will know it is done — the behaviour, the numbered acceptance criteria, the cases that are deliberately out. Use it when the problem is already framed and the open question is the substance: "what should this actually do?", "what does done look like for this feature?", "list the acceptance criteria", "the stakeholders disagree about what we're building", "write up what we agreed in that meeting", or a settled BRIEF whose next step is requirements. Without it an agent invents the requirements as it codes and nothing written down can contradict it later. Do NOT use it when neither the requirements nor the technical approach are written down anywhere — that whole run is `/scope`, which calls this as one hop. Do NOT use it to work out the problem and the scope boundary in the first place (`/brief`), to choose the technical approach (`/design`), or to investigate an open question (`/explore`).
tsukumogami/shirabe · ★ 0 · AI & Automation · score 67
Install: claude install-skill tsukumogami/shirabe
!`bash ${CLAUDE_PLUGIN_ROOT}/scripts/skill-preflight.sh prd 2>&1 || true` @.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-con