understand-requirements
Establish what a task-splitter run is building. In design mode, conduct a full structured requirements interview covering goals, features, constraints, scope boundaries, and definition of done. In split mode, read most of that out of an existing design doc and ask only what the doc cannot answer. Writes a machine-readable requirements-report.md either way. Use this at the start of every task-splitter run.
Pinned to revision a0910ab3a3bf, so it is the text this page describes rather than whatever the author pushed since.
Files
- skills/understand-requirements/SKILL.md
- skills/understand-requirements/agents/openai.yaml
- skills/understand-requirements/reference.md
- skills/understand-requirements/templates/requirements-template.md
Every link opens the file at its source, pinned to the revision this page describes.