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

  1. Read existing strategy, jobs, research, decisions, system constraints, and neighboring specs before asking for missing context.
  2. Define the problem, affected segment, situation, evidence, and consequence.
  3. State desired outcomes, success evidence, and strategic contribution.
  4. Describe the user journey or scenarios and write prioritized, testable product behavior.
  5. Define quality attributes and constraints: accessibility, privacy, trust, reliability, performance, compatibility, compliance, and operations as relevant.
  6. State non-goals, dependencies, assumptions, risks, rollout, measurement, and unresolved questions.
  7. Link evidence and decisions. Mark facts, hypotheses, commitments, and proposals distinctly.
  8. Review for altitude, contradictions, ambiguity, solution leakage, and verifiability.

BuildBetter Acceleration

Installs
1
GitHub Stars
4
First Seen
Oct 27, 2026