write-product-requirements
Installation
SKILL.md
Write Product Requirements
Contract
Requirements establish a shared product contract, not a retrospective justification for a chosen solution. Ground claims in evidence, keep outcome separate from implementation, and expose unresolved decisions.
Workflow
- Read existing strategy, jobs, research, decisions, system constraints, and neighboring specs before asking for missing context.
- Define the problem, affected segment, situation, evidence, and consequence.
- State desired outcomes, success evidence, and strategic contribution.
- Describe the user journey or scenarios and write prioritized, testable product behavior.
- Define quality attributes and constraints: accessibility, privacy, trust, reliability, performance, compatibility, compliance, and operations as relevant.
- State non-goals, dependencies, assumptions, risks, rollout, measurement, and unresolved questions.
- Link evidence and decisions. Mark facts, hypotheses, commitments, and proposals distinctly.
- Review for altitude, contradictions, ambiguity, solution leakage, and verifiability.