Agent skill
requirements-dev
This skill should be used when the user asks to "develop requirements", "formalize needs", "write requirements", "create a specification", "build traceability", "quality check requirements", "INCOSE requirements", "requirements development", "reqdev", or mentions requirements engineering, needs formalization, verification planning, traceability matrix, or systems engineering requirements. Even for casual phrases like "I need to write some reqs" or "let's formalize the needs", trigger this skill.
Install this agent skill to your Project
npx add-skill https://github.com/ddunnock/claude-plugins/tree/main/skills/requirements-dev
SKILL.md
Requirements Development (INCOSE GtWR v4)
Transform concept development artifacts into formal, INCOSE-compliant requirements through a structured three-phase pipeline with gate-controlled progression.
Deliverables
This skill produces three primary documents plus supporting registries:
| Deliverable | Format | Content |
|---|---|---|
| REQUIREMENTS-SPECIFICATION.md | Markdown | All requirements organized by block and type |
| TRACEABILITY-MATRIX.md | Markdown | Bidirectional chain: source → need → requirement → V&V |
| VERIFICATION-MATRIX.md | Markdown | All requirements with V&V methods, criteria, status |
| *.reqif | XML | Optional ReqIF interchange export |
| JSON registries | JSON | needs, requirements, traceability, sources, assumptions, notes |
<phase name="validation-research" sequence="2">
<depends-on>foundation.deliver</depends-on>
<objective>Cross-block validation sweep, benchmark research for measurable requirements, coverage gap discovery.</objective>
<commands>
<command ref="reqdev.validate.md">/reqdev:validate</command>
<command ref="reqdev.research.md">/reqdev:research</command>
<command ref="reqdev.gaps.md">/reqdev:gaps</command>
</commands>
<gates>
<gate name="validate" condition="User reviews and resolves all validation findings. INCOSE C10-C15 characteristics assessed."/>
</gates>
<note>/reqdev:gaps can be run after ANY phase gate (needs, requirements, deliver) — it adapts scope to the current phase.</note>
</phase>
<phase name="decomposition" sequence="3">
<depends-on>foundation.deliver</depends-on>
<objective>Decompose system-level requirements into subsystem allocations. Max 3 levels. Each level re-enters the quality pipeline.</objective>
<commands>
<command ref="reqdev.decompose.md">/reqdev:decompose</command>
</commands>
<gates>
<gate name="decompose" condition="User approves sub-block definitions and 100% allocation coverage at each decomposition level."/>
</gates>
<constraint>Maximum 3 decomposition levels (configurable in state.json).</constraint>
</phase>
<utility-commands>
<command ref="reqdev.status.md">/reqdev:status — Session dashboard (any time)</command>
<command ref="reqdev.resume.md">/reqdev:resume — Resume interrupted session</command>
</utility-commands>
Didn't find tool you were looking for?