requirements-verification
Skill for aerospace requirements verification and validation matrix management
Best use case
requirements-verification is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Skill for aerospace requirements verification and validation matrix management
Teams using requirements-verification should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/requirements-verification/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How requirements-verification Compares
| Feature / Agent | requirements-verification | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Skill for aerospace requirements verification and validation matrix management
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Requirements Verification Skill ## Purpose Enable comprehensive requirements verification and validation management including traceability matrices, compliance tracking, and evidence documentation. ## Capabilities - Requirements traceability matrix creation - Verification method assignment (T/A/I/D) - Compliance matrix generation - Requirements coverage analysis - Verification status tracking - Evidence linking and management - Change impact assessment - DOORS/Jama integration ## Usage Guidelines - Establish complete requirements traceability from top level to implementation - Assign appropriate verification methods based on requirement type - Track verification status throughout development - Link verification evidence to requirements - Assess impact of requirement changes on design and verification - Generate compliance reports for design reviews and certification ## Dependencies - IBM DOORS - Jama Connect - Requirements management tools ## Process Integration - AE-018: Requirements Verification Matrix - AE-021: Certification Planning
Related Skills
formal-verification
Formal property verification and model checking skill for FPGA designs
requirements-flowdown
Skill for systematic requirements capture, decomposition, and traceability
requirements-traceability-manager
Design control traceability skill for managing user needs, design inputs, design outputs, and verification/validation linkages
requirements-engineering
Automotive requirements management and traceability expertise
requirements-quality-analyzer
Specialized skill for analyzing and scoring requirements quality against BABOK and IEEE 29148 standards
verification
Verification-before-completion discipline ensuring all success criteria are met, tests pass, and reviews complete before declaring work done.
Completion Verification
Verify all phases are complete with weighted quality scoring before allowing session exit.
requirements-interview
Interactive PM interview with expertise-adaptive questioning for requirements elicitation
verification-suite
Plan structure validation, phase completeness checks, reference integrity verification, and artifact existence confirmation. Provides the structured verification layer ensuring GSD artifacts are well-formed and complete.
verification-before-completion
Evidence requirement enforcement ensuring all claims are backed by logs, test results, or exit codes. Zero = success, non-zero = failure. No guessing allowed.
process-builder
Scaffold new babysitter process definitions following SDK patterns, proper structure, and best practices. Guides the 3-phase workflow from research to implementation.
babysitter
Orchestrate via @babysitter. Use this skill when asked to babysit a run, orchestrate a process or whenever it is called explicitly. (babysit, babysitter, orchestrate, orchestrate a run, workflow, etc.)