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.

View SKILL.md on GitHub Repository
Stars 6
Forks 0

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>

Recommended Agent Skills

Expand your agent's capabilities with these related and highly-rated skills.

ddunnock/claude-plugins

streaming-output

Stream long-form content to markdown files with resume capability. Writes content incrementally with section markers, enabling recovery if context limits are hit. Use when generating long documents (over 1000 lines), B-SPEC or specification writing, multi-section reports, any task where context compaction may occur mid-generation, or when user explicitly requests streaming output. Commands: init, write, status, resume, finalize, repair.

6 0
Explore
ddunnock/claude-plugins

fishbone-diagram

Create comprehensive Fishbone (Ishikawa/Cause-and-Effect) diagrams for structured root cause brainstorming. Guides teams through problem definition, category selection (6Ms, 8Ps, 4Ss, or custom), cause identification, sub-cause drilling, prioritization via multi-voting, and 5 Whys integration. Generates visual SVG diagrams and professional HTML reports. Use when brainstorming potential causes, conducting root cause analysis, facilitating quality improvement sessions, analyzing defects or failures, structuring team problem-solving, or when user mentions "fishbone", "Ishikawa", "cause and effect diagram", "6Ms", "cause analysis", or "brainstorming causes".

6 0
Explore
ddunnock/claude-plugins

streaming-output-mcp

Stream structured content to persistent SQLite storage with automatic session break recovery. Core principle: The content IS the state. Every stream_write is automatically persistent. Supports multi-format export (Markdown, HTML, JSON, YAML, CSV, Text) and 7 document templates. Commands: /stream-init, /stream-status, /stream-read, /stream-write, /stream-export. ALWAYS call stream_status after session breaks to check for resume_from and preserved_context.

6 0
Explore
ddunnock/claude-plugins

fmea-analysis

Conduct Failure Mode and Effects Analysis (FMEA) for systematic identification and risk assessment of potential failures in designs, processes, or systems. Supports DFMEA (Design), PFMEA (Process), and FMEA-MSR (Monitoring & System Response). Uses AIAG-VDA 7-step methodology with Action Priority (AP) risk assessment replacing traditional RPN. Use when analyzing product designs for potential failures, evaluating manufacturing process risks, conducting proactive risk assessment, preparing for APQP/PPAP submissions, investigating field failures, or when user mentions "FMEA", "failure mode", "DFMEA", "PFMEA", "severity occurrence detection", "RPN", "Action Priority", "design risk analysis", or needs to identify and prioritize potential failure modes with their causes and effects.

6 0
Explore
ddunnock/claude-plugins

problem-definition

Guide RCCA/8D problem definition using 5W2H and IS/IS NOT analysis. Transforms scattered failure data into precise, measurable problem statements that bound investigation scope without embedding cause or solution. Use when defining problems for root cause analysis, writing D2 sections of 8D reports, analyzing nonconformances, investigating failures, or when user mentions problem definition, problem statement, RCCA, 8D, failure analysis, or corrective action.

6 0
Explore
ddunnock/claude-plugins

kepner-tregoe-analysis

Conduct Kepner-Tregoe (KT) Problem Solving and Decision Making (PSDM) analysis using the four rational processes - Situation Appraisal, Problem Analysis, Decision Analysis, and Potential Problem Analysis. Use when performing structured root cause analysis, making complex decisions, evaluating alternatives with weighted criteria, conducting IS/IS NOT specification analysis, anticipating implementation risks, troubleshooting complex issues, or when user mentions "Kepner-Tregoe", "KT method", "IS/IS NOT", "situation appraisal", "decision analysis", "MUSTS and WANTS", "potential problem analysis", or needs systematic problem-solving methodology. Includes specification matrices, decision scoring, quality rubrics, and professional report generation.

6 0
Explore

Didn't find tool you were looking for?

Be as detailed as possible for better results