Define prd
Create PRDs with success metrics for Stage A of the VibeFlow docs-first workflowFrom its SKILL.md
npx -y skills add hardness1020/VibeFlow --skill define-prdAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 8 stars8 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
1.8 KB, as published. Nobody here has run it
define-prd
Create PRDs with success metrics for Stage A of the VibeFlow docs-first workflow.
Purpose
This skill creates and validates PRD (Product Requirements Document) for Stage A:
- Define problem, users, and scope
- Set success metrics with baseline → target
- Document requirements, dependencies, and risks
Workflow
Stage A: Initiate
│
├── Create/update PRD
├── Define problem, users, scope
└── Set success metrics
Usage
Create PRD
/define-prd
Creates or updates docs/prds/prd.md with required sections.
Document Requirements
PRD (docs/prds/prd.md)
Required sections:
- Header (version, file, owners, last_updated)
- Summary (3-5 lines)
- Problem & Context
- Users & Use Cases
- Scope (MoSCoW format)
- Success Metrics (baseline → target)
- Non-Goals
- Requirements (functional + non-functional)
- Dependencies
- Risks & Mitigations
- Analytics & Telemetry
Validation
scripts/validate_prd.py— Validate PRD structure and content
References
See assets/:
prd-template.md— PRD template
Manifest Update
After completing Stage A, update docs/workflow-state.yaml:
- Set
stage: A - Set
docs.prd: docs/prds/prd.md
Git Commit
After completing this stage, ask the user for permission before committing:
git add docs/prds/prd.md docs/workflow-state.yaml
git commit -m "feat(prd): define product requirements (#ft-<ID>)"
Replace <ID> with the actual work item ID.
Auto-Advance
After the commit is complete, directly run /manage-work advance <ID> to advance to the next stage.