requirements-analysis

Clarify requirements and write PRD/spec with objectives, boundaries, acceptance criteria before code.

SKILL.md

GitHub

requirements-analysis

No code before the spec is accepted: objectives, boundaries, acceptance criteria.

Activate when

  • New features, products, or significant changes with any ambiguity.

Do NOT activate for

  • Pure technical refactors (see refactoring); task breakdown itself (see planning).

Procedure

  1. Extract: problem, users, jobs-to-be-done, constraints, non-goals; ask only where a wrong guess reshapes the work.
  2. Specify: objectives, scope boundaries, acceptance criteria per story, success metric, risks/unknowns with owners.
  3. Review the spec for testability (every claim verifiable) and hand off to planning.
  4. Verify: stakeholder sign-off recorded; analytics hook identified for the success metric.

References

  • Related: ../../product/mvp-discovery/, ../planning/.