How do I install the Validation skill?

Run npx skillmds@latest add ashfordeou/validation 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 Validation 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 Validation?

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

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

Who published Validation?

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

Validation by ashfordeou — Agent Skill

Name: Validation
Author: ashfordeOU

Validation

Use when you must run requirements validation for an aircraft or system program per ARP4754A: select the validation method, confirm independence is provided where the development assurance level requires it, and score validation closure before the requirements are released to design. Produces the method verdict, the independence flag, and the closure score that gate the validation phase. Trigger: requirements validation, arp4754a, validation method, independent validation, development assurance, closure.

ashfordeOU 531260d 3 files · 6.0 KB Updated Sep 17, 2026

File contents

ARP4754A Requirements Validation (systems-engineering-safety/arp4754a/validation)

Use when the task is requirements validation per ARP4754A: method selection, independence, and closure scoring before requirements move to design.

Domain quick reference

Validation asks whether the right requirements were captured; verification asks whether they were built right.
Validation methods: analysis, simulation, test, demonstration, and inspection.
Development assurance levels A and B require independent validation of the requirements.
Closure: every requirement validated by a recognized method before release; project thresholds typically require near-full closure.

Workflow

Collect each requirement with its validation status and method.
Confirm the method is recognized with validate_method_ok.
Check independence with independence_required.
Score closure with validation_closure.
Gate the requirements release on the closure verdict.

Pitfalls

Calling review a validation method and closing without analysis.
Missing independent validation at level A or B.
Releasing requirements with open validation items.

Behavior contract (gate 3)

The method, independence, and closure logic is exercised by the gate 3 contract test: scripts/test_validation.py against scripts/validation_logic.py (stdlib unittest, offline). Run: python3 scripts/test_validation.py

Compliance

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

---name: validationdescription: Use when you must run requirements validation for an aircraft or system program per ARP4754A: select the validation method, confirm independence is provided where the development assurance level requires it, and score validation closure before the requirements are released to design. Produces the method verdict, the independence flag, and the closure score that gate the validation phase. Trigger: requirements validation, arp4754a, validation method, independent validation, development assurance, closure.license: Apache-2.0---# ARP4754A Requirements Validation (systems-engineering-safety/arp4754a/validation)Use when the task is requirements validation per ARP4754A: methodselection, independence, and closure scoring before requirementsmove to design.## Domain quick reference- Validation asks whether the right requirements were captured; verification asks whether they were built right.- Validation methods: analysis, simulation, test, demonstration, and inspection.- Development assurance levels A and B require independent validation of the requirements.- Closure: every requirement validated by a recognized method before release; project thresholds typically require near-full closure.## Workflow1. Collect each requirement with its validation status and method.2. Confirm the method is recognized with validate_method_ok.3. Check independence with independence_required.4. Score closure with validation_closure.5. Gate the requirements release on the closure verdict.## Pitfalls- Calling review a validation method and closing without analysis.- Missing independent validation at level A or B.- Releasing requirements with open validation items.## Behavior contract (gate 3)The method, independence, and closure logic is exercised by thegate 3 contract test: scripts/test_validation.py againstscripts/validation_logic.py (stdlib unittest, offline). Run:python3 scripts/test_validation.py## Compliance- Standards referenced, not reproduced: ARP4754A and ARP4761A text is proprietary (SAE); summary-only per standards-map.yaml and brief 06.- compliance: STANDARDS-REF, gated: false.

Frequently asked questions