How do I install the Verification skill?

Run npx skillmds@latest add ashfordeou/verification-2 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 Verification 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 Verification?

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 Verification free to use?

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

Who published Verification?

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

Verification by ashfordeou — Agent Skill

Name: Verification
Author: ashfordeOU

Verification

Use when you must verify DO-178C airborne software against its requirements: review software architecture, design, and code, run requirements-based tests, and analyze structural coverage at the depth the software level demands: A requires MC/DC, B decision coverage, C statement coverage, D and E require none. Determine whether verification must be independent, which applies at levels A and B, and produce the verification results, coverage analysis, and review records the software verification process must deliver. Trigger: DO-178C verification, MC/DC coverage, decision coverage, statement coverage, structural coverage analysis, requirements-based testing, independent verification.

ashfordeOU 1cc2634 3 files · 6.3 KB Updated Sep 17, 2026

File contents

DO-178C Verification (avionics/do178c/verification)

Use when the task is DO-178C verification-phase work: proving the software meets its requirements and analyzing structural coverage to the depth the software level demands.

Domain quick reference

Verification (DO-178C): review of architecture, design, and code, plus requirements-based testing; every requirement is exercised.
Structural coverage depth scales with level: A = MC/DC, B = decision, C = statement, D/E = none required.
Coverage must reach 100% of the required metric for the level.
Independence: levels A and B require independent verification; C/D/E allow the developer's organization to verify.
Verification results, problem reports, and coverage analysis are the outputs the process must deliver.

Workflow

Confirm the software level and the applicable coverage depth.
Review software architecture, design, and code against requirements.
Run requirements-based tests; confirm every requirement is exercised.
Analyze structural coverage at the required depth (A MC/DC, B decision, C statement).
Levels A/B: perform the independent verification activities.
Produce verification results, coverage analysis, and review records.

Pitfalls

Coverage depth mismatched to level (A requires MC/DC, not statement).
Structural coverage below 100% of the required metric.
Requirements-based testing without exercising every requirement.
Missing independence at level A or B.

Behavior contract (gate 3)

The coverage-depth and independence logic is exercised by the gate 3 contract test: scripts/test_verification.py against scripts/verification_logic.py (stdlib unittest, offline). Run: python3 scripts/test_verification.py

Compliance

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

---name: verification-2description: Use when you must verify DO-178C airborne software against its requirements: review software architecture, design, and code, run requirements-based tests, and analyze structural coverage at the depth the software level demands: A requires MC/DC, B decision coverage, C statement coverage, D and E require none. Determine whether verification must be independent, which applies at levels A and B, and produce the verification results, coverage analysis, and review records the software verification process must deliver. Trigger: DO-178C verification, MC/DC coverage, decision coverage, statement coverage, structural coverage analysis, requirements-based testing, independent verification.license: Apache-2.0---# DO-178C Verification (avionics/do178c/verification)Use when the task is DO-178C verification-phase work: proving the softwaremeets its requirements and analyzing structural coverage to the depth thesoftware level demands.## Domain quick reference- Verification (DO-178C): review of architecture, design, and code, plus requirements-based testing; every requirement is exercised.- Structural coverage depth scales with level: A = MC/DC, B = decision, C = statement, D/E = none required.- Coverage must reach 100% of the required metric for the level.- Independence: levels A and B require independent verification; C/D/E allow the developer's organization to verify.- Verification results, problem reports, and coverage analysis are the outputs the process must deliver.## Workflow1. Confirm the software level and the applicable coverage depth.2. Review software architecture, design, and code against requirements.3. Run requirements-based tests; confirm every requirement is exercised.4. Analyze structural coverage at the required depth (A MC/DC, B decision, C statement).5. Levels A/B: perform the independent verification activities.6. Produce verification results, coverage analysis, and review records.## Pitfalls- Coverage depth mismatched to level (A requires MC/DC, not statement).- Structural coverage below 100% of the required metric.- Requirements-based testing without exercising every requirement.- Missing independence at level A or B.## Behavior contract (gate 3)The coverage-depth and independence logic is exercised by the gate 3contract test: scripts/test_verification.py againstscripts/verification_logic.py (stdlib unittest, offline). Run:python3 scripts/test_verification.py## Compliance- Standards referenced, not reproduced: DO-178C / ARP4754A / ARP4761A text is proprietary (RTCA/SAE); summary-only per standards-map.yaml and brief 06.- compliance: STANDARDS-REF, gated: false.

Frequently asked questions