requirements-analysis
Clarify requirements and write PRD/spec with objectives, boundaries, acceptance criteria before code.
SKILL.mdskills/core/requirements-analysis/SKILL.md
GitHubrequirements-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
- Extract: problem, users, jobs-to-be-done, constraints, non-goals; ask only where a wrong guess reshapes the work.
- Specify: objectives, scope boundaries, acceptance criteria per story, success metric, risks/unknowns with owners.
- Review the spec for testability (every claim verifiable) and hand off to planning.
- Verify: stakeholder sign-off recorded; analytics hook identified for the success metric.
References
- Related:
../../product/mvp-discovery/,../planning/.