Create and validate Stage A PRDs with required sections and MoSCoW scope formatting.
npx skills add https://github.com/hardness1020/VibeFlow --skill define-prd
Please help me install this Agent Skill. Skill: define-prd Source: https://github.com/hardness1020/VibeFlow/tree/main/.claude/skills/define-prd Command: npx skills add https://github.com/hardness1020/VibeFlow --skill define-prd
Stage A PRDs are often inconsistently structured and hard to validate, causing misalignment between problem definition, users, scope, and success metrics. This skill automates the creation and validation of PRDs to ensure a consistent, reviewable foundation for feature work in the VibeFlow docs-first workflow.
Issue the /define-prd command to generate or update docs/prds/prd.md.
High-intent search queries and answers about installing and using this skill.
To create a product requirements document, use the /define-prd command to generate docs/prds/prd.md with required sections like Problem, Scope, and Success Metrics. It automatically enforces MoSCoW-based scope formatting to gate progress and maintain traceability.
Stage A in a docs-first workflow defines the foundational problem, users, scope, and success metrics before implementation. You need to validate it using a structure validator to catch missing header metadata and formatting issues, ensuring stakeholder alignment.
You validate PRD structure by running the included validation script against docs/prds/prd.md. This catches missing required sections, header metadata, and formatting issues to ensure a reviewable foundation for feature work.
Yes, the VibeFlow PRD template supports non-goals and risk mitigation tracking. It generates sections for Non-Goals, Risks & Mitigations, and Dependencies alongside Requirements and Analytics to maintain comprehensive traceability.
The best way to align stakeholders is enforcing MoSCoW-based scope formatting within your PRD. This gates progress by categorizing requirements strictly, ensuring design and testing teams share a reviewable, consistent foundation.
PRD validation fails when required sections like Header, Summary, or Success Metrics are missing, or if header metadata and MoSCoW scope formatting are incorrect. The validator enforces these constraints to prevent misalignment.
DaRacciAnalyze code changes and update Markdown files in the docs/src directory.
qte77Convert PRD.md into structured prd.json for Ralph workflows.
AbeJitsuApply user-defined formatting standards across code, documentation, and content outputs using ESLint and Prettier.
bnadlerjrTranslate product briefs into structured PRDs with scope, use cases, and milestones.
