Generate a complete product requirement document from a product brief and project artefacts.
npx skills add https://github.com/yabafre/aped-claude --skill aped-prd
Please help me install this Agent Skill. Skill: aped-prd Source: https://github.com/yabafre/aped-claude/tree/main/src/templates/skills/aped-prd Command: npx skills add https://github.com/yabafre/aped-claude --skill aped-prd
It helps you turn a messy product brief into a complete, build-ready PRD with requirements that are consistent, testable, and validated before downstream planning.
Run aped-prd with headless mode to generate prd.md using your existing product brief and inputs you already placed in the APED project output directory.
High-intent search queries and answers about installing and using this skill.
You can generate a complete PRD from a product brief automatically by running the generation process in headless mode. This mode skips interactive menus to autonomously author Foundation, Scope, and Requirements sections directly into your output directory.
The best way to enforce a strict PRD format for functional requirements is using a spec validation tool that applies structural enforcement. It ensures requirements follow the required FR format and catches ambiguity or scope creep through automated self-review gates.
To add measurable thresholds to non-functional requirements, you need a PRD drafting process that enforces structured NFR rules. This prevents vague targets by validating that every non-functional requirement includes a specific, testable measurement threshold.
Yes, you can bias PRD generation for a brownfield project by providing existing project artifacts and context. The generation process detects this context and conditionally incorporates domain or compliance requirements before producing the functional and non-functional requirements.
PRD generation halts before producing functional requirements because quality gates enforce validation via placeholder linting and oracle self-review. The process intentionally stops until all ambiguity, inconsistency, and placeholder issues are resolved to ensure requirements are testable.
No, you do not need an interactive menu to draft product requirement documents. While interactive mode uses an A/P/C menu after each section for manual control, you can use headless mode to skip menus and generate the entire PRD autonomously.
RomainDECOSTEROrchestrate BMAD analysis phases to produce brief, PRD, and architecture artefacts.
tech-leads-clubPlan and execute software projects through four specification-driven phases.
mattgierhartSelect Build/Buy/Integrate/Research options for frontend, backend, database, auth, and infrastructure.
flonatInspect mathematical proofs for clarity and improve readability without altering correctness.
