Use this skill to create or review PRDs in this repository.
Default approach
- Keep PRDs concise and implementation-oriented.
- Prefer concrete bullet points over long prose.
- Include only information needed to decide and deliver.
Required sections
- Problem Statement (what is missing/broken and why now)
- Goals (desired outcomes)
- Non-Goals (explicitly out of scope)
- Users / Personas (who benefits or is affected)
- Success Metrics (measurable outcomes)
- Product Requirements (functional and non-functional requirements)
- Risks & Open Questions (unknowns, assumptions, dependencies)
Quality checks
- Every requirement is testable.
- Every goal maps to at least one metric.
- Non-goals clearly prevent scope creep.
- Line length is always limited to 120 characters.
What to avoid
- Adding a Document Control section.