Create 21-section Layer-2 PRDs from BRD inputs with validation rules and KPIs.
npx skills add https://github.com/vladm3105/aidoc-flow-framework --skill doc-prd
Please help me install this Agent Skill. Skill: doc-prd Source: https://github.com/vladm3105/aidoc-flow-framework/tree/main/.claude/skills/doc-prd Command: npx skills add https://github.com/vladm3105/aidoc-flow-framework --skill doc-prd
This Skill guides the creation of Product Requirements Documents (PRD) from Business Requirements Documents (BRD), translating business goals into measurable product features, KPIs, and success criteria.
After BRD completion, use doc-prd to draft a PRD outlining core features and success metrics.
High-intent search queries and answers about installing and using this skill.
Creating a PRD from a BRD involves translating business goals into measurable product features and success criteria. Use doc-prd to structure a 21-section PRD that captures user needs, KPIs, and validation rules aligned with your upstream BRD and downstream artifacts like EARS and ADR specifications.
A comprehensive PRD must include mandatory sections defining product vision, goals, user personas, and KPIs with clear traceability to the BRD above and design artifacts below. doc-prd enforces prerequisites like artifact verification, reference templates, and prohibition of placeholders to achieve SYS-Ready and EARS-Ready scores.
Structured PRD templates are essential when aligning product features across business, design, and development workflows. They ensure consistent section structure, validation rules, and measurable success criteria—preventing ambiguity and enabling traceability from business requirements through implementation.
Yes. A PRD captures user personas, functional needs, and measurable KPIs in a single document. doc-prd structures these as interconnected sections so success criteria directly tie to user needs and business goals, enabling teams to validate that shipped features meet both requirements and outcomes.
Misalignment between PRD and BRD creates gaps in traceability and conflicting requirements downstream. doc-prd requires upstream artifact verification and ADR alignment as prerequisites, flagging inconsistencies before proceeding so features remain grounded in validated business context.
A PRD sits between business requirements and downstream design decisions, so it should capture product scope and success metrics before detailed design. doc-prd works within the SDD workflow and requires BRD completion as a prerequisite; development input typically follows during design and implementation phases.
vladm3105Generate Layer-6 System Requirements documents with traceability to upstream artifacts.
InNoobWeTrustCascade product requirements from PRD to TRD to BDD with traceability matrices.
vladm3105Create formal EARS Layer 3 requirements documents using WHEN-THE-SHALL-WITHIN syntax.
whimzyLiveDecompose large user stories into smaller stories using eight systematic splitting patterns.
