← ClaudeAtlas

gen-prdlisted

Project-local PRD writer. Use when the user invokes "$gen-prd", asks for a PRD, product requirements document, implementation-ready requirements, or wants to turn intake/clarify output into a human-reviewable requirements contract with major technical structure changes, PRD-level tasks, a compact verification contract, required test modes, human verification, risks, guardrails, and an implementation result report contract.
yansfil/sasu · ★ 1 · AI & Automation · score 64
Install: claude install-skill yansfil/sasu
# gen-prd PRDs live under the visible `agents/` namespace (`agents/prd/**`), which is the only namespace the pipeline reads or writes. Use this skill to write an implementation-ready PRD from intake output or the current conversation. The PRD is a human decision contract and an implementation handoff. Do not implement code while using this skill. Match the user's language by default. ## Default Inputs Prefer an explicit context path, passed directly or as `--context <path>` (the form `$interview-me` suggests at handoff). The canonical interview source is: ```text agents/interview/<topic-slug>/qa-log.md ``` If no context path is provided, inspect `agents/interview/` first for the matching or most recent qa-log (then the legacy `agents/intake/` path for interviews started before the rename). If no complete interview source exists and major ambiguity remains, ask one blocking question or recommend `$interview-me`. When qa-log.md is the source, read the complete file. Treat its Current Understanding as a navigation aid, not a substitute for the Decision Register, material Raw Q&A (Decision Packet content lives in each entry's `immediate_notes`), UX Scenario Cards, objections, evidence, and audit findings. The qa-log is the canonical interview source even when a shorter summary exists elsewhere. ## Output Contract Create exactly one file: ```text agents/prd/<topic-slug>/prd.md ``` Do not write side files (context notes, audit reports). Decisions and traceability live