Generate structured Product Requirements Documents from approved business statements and scope artifacts.
npx skills add https://github.com/pingmepi/pm-os --skill pm-stage-03-prd
Please help me install this Agent Skill. Skill: pm-stage-03-prd Source: https://github.com/pingmepi/pm-os/tree/main/skills/pm-stage-03-prd Command: npx skills add https://github.com/pingmepi/pm-os --skill pm-stage-03-prd
This skill automates the creation of high-quality, consistent Product Requirements Documents (PRDs) by synthesizing approved business statements, briefs, and scope documents, ensuring alignment across design, engineering, and QA.
Invoke the pm-stage-03-prd skill to generate the product requirements document for the current project stage.
High-intent search queries and answers about installing and using this skill.
PRD generation from approved business statements requires synthesizing upstream scope artifacts into structured documents. This skill automates drafting epics, user stories, and functional requirements while enforcing traceability to ensure alignment across design, engineering, and QA.
Traceability in a product requirements document links business goals directly to technical requirements and acceptance criteria. This skill enforces strict traceability requirements during PRD generation to validate upstream dependencies and maintain consistency throughout the gated product development lifecycle.
Preventing scope creep during PRD creation involves managing stage-gate approvals within a gated product development lifecycle. This skill validates upstream project context and enforces governance rules to ensure only approved business statements and scope artifacts are included in the final document.
PRD generation within a gated product development lifecycle requires validating upstream dependencies before drafting. This skill operates explicitly within stage-gate frameworks to enforce consistency between product definition and technical execution, ensuring documents are delivery-ready for team review.
Automating user stories and acceptance criteria drafting is achievable by reading existing project context. This skill generates comprehensive PRDs including epics and functional requirements based on upstream project state, producing a structured document ready for immediate team review.
Automated PRD generation limitations include strict dependency on approved upstream business statements and scope artifacts. This skill cannot draft documents without validated upstream project context, requiring prior stage-gate approvals to successfully enforce traceability and prevent unapproved scope creep.
pingmepiGenerate a structured Product Scope document for the MVP phase.
CaptainCrouton89Automate software tests to verify functionality against acceptance criteria.
pingmepiApprove product lifecycle artifacts by computing content hashes and tracking stage state.
infinith4Translate product ideas into structured requirements documentation with traceability matrix.
