Stats
Actions
Tags
From requirements-dev
Assembles requirements documents (spec, traceability matrix, verification matrix), validates traceability, requires user approval, exports ReqIF, and baselines.
How this command is triggered — by the user, by Claude, or both
Slash command
/requirements-dev:reqdev.deliverThe summary Claude sees in its command listing — used to decide when to auto-load this command
<context>
<read required="true">${CLAUDE_PLUGIN_ROOT}/SKILL.md</read>
</context>
# /reqdev:deliver - Deliverable Assembly
Orchestrates the deliverable generation pipeline: validates traceability, generates documents from templates, exports ReqIF, and baselines requirements.
<prerequisite gate="requirements">
<check>python3 ${CLAUDE_PLUGIN_ROOT}/scripts/update_state.py --workspace .requirements-dev check-gate requirements</check>
<on-fail>The requirements phase is not complete. Run /reqdev:requirements to complete all requirement blocks before delivering.</on-fail>
</prerequis...Orchestrates the deliverable generation pipeline: validates traceability, generates documents from templates, exports ReqIF, and baselines requirements.
python3 ${CLAUDE_PLUGIN_ROOT}/scripts/update_state.py --workspace .requirements-dev check-gate requirements The requirements phase is not complete. Run /reqdev:requirements to complete all requirement blocks before delivering. Run traceability checks and present coverage to the user. - Orphan needs (needs with no derived requirements) - Orphan requirements (requirements with no parent need) - Coverage percentage Warn but do not block delivery. Gaps are reported in the traceability matrix. Invoke the document-writer agent for each deliverable. Requirements organized by block and type Full chain from source to need to requirement to V&V All requirements with V&V methods and criteria .requirements-dev/needs_registry.json .requirements-dev/requirements_registry.json .requirements-dev/traceability_registry.json .requirements-dev/deliverables/ Present each deliverable for review. All three must be approved before proceeding. **{deliverable name}** generated. Please review: [Show document content or summary] Approve? (yes/edit/reject) All three documents must be approved. Export optional ReqIF interchange format. Inform the user and continue. ReqIF is optional. All deliverables approved (step 3). Transition every registered requirement to baselined status. Withdrawn requirements are unaffected. Draft requirements generate warnings. Before closing the deliver gate, resolve all open notes targeting this phase. Present notes and guide user to resolve or dismiss each one. All notes targeting this phase must be resolved or dismissed before the gate can pass. Record deliverable artifacts and pass the deliver gate. Delivery Complete ----------------- Requirements baselined: {count} Deliverables generated: - REQUIREMENTS-SPECIFICATION.md - TRACEABILITY-MATRIX.md - VERIFICATION-MATRIX.md ReqIF export: {Generated | Skipped (reqif package not installed)}Phase: deliver (gate passed) Next: /reqdev:validate or /reqdev:decompose
npx claudepluginhub ddunnock/claude-plugins --plugin requirements-dev/requirements-authoring-flowGuides AI through requirements authoring workflow (create/update/review/improve) with mandatory user approvals per phase, producing final requirements set, validation pack, and traceability matrix.
/flow-requirements-evolutionOrchestrates multi-agent workflows for living requirements refinement, change requests, impact analysis, and traceability maintenance throughout SDLC.
/requirements-endFinalizes active requirements gathering: shows status, generates spec with assumptions and implementation notes, marks incomplete, or cancels/deletes.