Doc Prd

Generates Product Requirements Documents as Layer 2 of the SDD workflow, sitting between a Business Requirements Document upstream and formal EARS requirements downstream. You get 15 structured sections covering personas, success metrics, user journeys, and acceptance criteria, all at the C4 Container level (what the product does, not how). The standout requirement is Section 10, which forces you to write real customer-facing content in at least three categories before you can move forward. It enforces hierarchical element IDs, cumulative traceability tags back to the BRD, and won't let you proceed to EARS unless you hit a 90/100 readiness score. Useful if you need to bridge business goals and technical implementation with actual discipline instead of skipping straight to code.

Install to Claude Code

npx -y skills add vladm3105/aidoc-flow-framework --skill doc-prd --agent claude-code