How do I install the Requirements Capture skill?

Run npx skillmds@latest add ashfordeou/requirements-capture in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Requirements Capture safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Requirements Capture?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Requirements Capture free to use?

Yes. Installing skills from SkillMD is free. This skill is licensed under Apache-2.

Who published Requirements Capture?

ashfordeOU (@ashfordeou) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Requirements Capture by ashfordeou — Agent Skill

Name: Requirements Capture
Author: ashfordeOU

Requirements Capture

Use when you must capture and review DO-254 hardware requirements for a complex airborne electronic hardware item: check each requirement for vague terms, missing identifiers, and missing trace links, classify derived requirements from allocated ones, and score capture readiness before the requirements review. Produces the requirement issue list, the derived-versus-allocated classification, and the readiness verdict the design phase consumes. Trigger: hardware requirements, requirements capture, derived requirements, traceability, do-254, requirement characteristics.

ashfordeOU 4d3ee42 3 files · 7.7 KB Updated Sep 17, 2026

File contents

DO-254 Hardware Requirements Capture (avionics/do254/requirements-capture)

Use when the task is DO-254 hardware requirements capture: checking requirement characteristics, identifying derived requirements, and gating the requirements review for airborne electronic hardware.

Domain quick reference

DO-254 hardware requirements must be complete, correct, and verifiable, with unique identifiers and trace links.
Derived requirements: added during design or safety analysis with no direct higher-level source; they must be identified and justified, and they count as requirements for verification.
Allocated requirements trace upward to a system requirement; derived requirements do not.
Vague wording (suitable, adequate, approximately, and similar) fails the verifiability test at the requirements review.

Workflow

Collect each hardware requirement with its identifier, text, and trace status.
Run the characteristic check with req_issues.
Classify each requirement as derived or allocated with classify_derived.
Score capture readiness with capture_readiness.
Gate the requirements review on the issue list and readiness.

Pitfalls

Accepting vague wording because the design intent is clear.
Missing trace links on allocated requirements.
Letting derived requirements appear without a justification note.

Behavior contract (gate 3)

The requirement-characteristic, classification, and readiness logic is exercised by the gate 3 contract test: scripts/test_requirements_capture.py against scripts/requirements_capture_logic.py (stdlib unittest, offline). Run: python3 scripts/test_requirements_capture.py

Compliance

Standards referenced, not reproduced: DO-254 text is proprietary (RTCA); summary-only per standards-map.yaml and brief 06.
compliance: STANDARDS-REF, gated: false.

---name: requirements-capturedescription: Use when you must capture and review DO-254 hardware requirements for a complex airborne electronic hardware item: check each requirement for vague terms, missing identifiers, and missing trace links, classify derived requirements from allocated ones, and score capture readiness before the requirements review. Produces the requirement issue list, the derived-versus-allocated classification, and the readiness verdict the design phase consumes. Trigger: hardware requirements, requirements capture, derived requirements, traceability, do-254, requirement characteristics.license: Apache-2.0---# DO-254 Hardware Requirements Capture (avionics/do254/requirements-capture)Use when the task is DO-254 hardware requirements capture: checkingrequirement characteristics, identifying derived requirements, andgating the requirements review for airborne electronic hardware.## Domain quick reference- DO-254 hardware requirements must be complete, correct, and verifiable, with unique identifiers and trace links.- Derived requirements: added during design or safety analysis with no direct higher-level source; they must be identified and justified, and they count as requirements for verification.- Allocated requirements trace upward to a system requirement; derived requirements do not.- Vague wording (suitable, adequate, approximately, and similar) fails the verifiability test at the requirements review.## Workflow1. Collect each hardware requirement with its identifier, text, and trace status.2. Run the characteristic check with req_issues.3. Classify each requirement as derived or allocated with classify_derived.4. Score capture readiness with capture_readiness.5. Gate the requirements review on the issue list and readiness.## Pitfalls- Accepting vague wording because the design intent is clear.- Missing trace links on allocated requirements.- Letting derived requirements appear without a justification note.## Behavior contract (gate 3)The requirement-characteristic, classification, and readiness logicis exercised by the gate 3 contract test:scripts/test_requirements_capture.py againstscripts/requirements_capture_logic.py (stdlib unittest, offline).Run:python3 scripts/test_requirements_capture.py## Compliance- Standards referenced, not reproduced: DO-254 text is proprietary (RTCA); summary-only per standards-map.yaml and brief 06.- compliance: STANDARDS-REF, gated: false.

Frequently asked questions