How do I install the Requirements Allocation skill?

Run npx skillmds@latest add ashfordeou/requirements-allocation 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 Allocation 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 Allocation?

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

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

Who published Requirements Allocation?

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

Requirements Allocation by ashfordeou

Name: Requirements Allocation
Author: ashfordeOU

Requirements Allocation

Use when you must allocate system requirements to items and functions per ARP4754A development planning: assign each system requirement to a design item or function, check the allocation coverage to find the unallocated requirements, detect a requirement allocated to more than one item, and group the allocated requirements per item for the item development handoff. Produces the allocation register, the unallocated list, and the double allocation verdict that gate the handoff of requirements to item level development. Trigger: requirements allocation, allocation coverage, item allocation, unallocated requirements, allocate system requirements to items.

ashfordeOU 56a235f 3 files · 8.5 KB Updated Sep 17, 2026

File contents

Requirements Allocation (systems-engineering-safety/arp4754a/requirements-allocation)

Use when the task is ARP4754A requirements allocation: assigning system requirements to items and functions, checking allocation coverage, and grouping the register for item level development.

Domain quick reference

System requirements are allocated to items and functions so each design element owns a defined requirement set.
The allocation register maps every requirement id to one item.
Coverage review finds the unallocated requirements and the share of the requirement set that is allocated.
A requirement must map to exactly one item; a second allocation is a conflict.
The grouped register per item supports the item development handoff.

Workflow

Collect the requirement ids and the design items and functions.
Allocate each system requirement to one item.
Check the allocation coverage and list the unallocated requirements.
Detect any requirement allocated to more than one item.
Group the register per item and gate the item development handoff.

Pitfalls

Allocating the same requirement to two items; the register allows only one allocation per requirement.
Scoring coverage without the full requirement id set; the ratio is only valid over the complete list.
Assigning a requirement to an item that is not in the design breakdown; the item must exist.
Reusing an allocation register across programs without clearing it.

Behavior contract (gate 3)

The allocation and coverage logic is exercised by the gate 3 contract test: scripts/test_requirements_allocation.py against scripts/requirements_allocation_logic.py (stdlib unittest, offline). Run: python3 scripts/test_requirements_allocation.py

Compliance

Standards referenced, not reproduced: ARP4754A text is proprietary (SAE); summary-only per standards-map.yaml. Allocation to items is common development methodology.
compliance: STANDARDS-REF, gated: false.

---name: requirements-allocationdescription: Use when you must allocate system requirements to items and functions per ARP4754A development planning: assign each system requirement to a design item or function, check the allocation coverage to find the unallocated requirements, detect a requirement allocated to more than one item, and group the allocated requirements per item for the item development handoff. Produces the allocation register, the unallocated list, and the double allocation verdict that gate the handoff of requirements to item level development. Trigger: requirements allocation, allocation coverage, item allocation, unallocated requirements, allocate system requirements to items.license: Apache-2.0---# Requirements Allocation (systems-engineering-safety/arp4754a/requirements-allocation)Use when the task is ARP4754A requirements allocation: assigningsystem requirements to items and functions, checking allocationcoverage, and grouping the register for item level development.## Domain quick reference- System requirements are allocated to items and functions so each design element owns a defined requirement set.- The allocation register maps every requirement id to one item.- Coverage review finds the unallocated requirements and the share of the requirement set that is allocated.- A requirement must map to exactly one item; a second allocation is a conflict.- The grouped register per item supports the item development handoff.## Workflow1. Collect the requirement ids and the design items and functions.2. Allocate each system requirement to one item.3. Check the allocation coverage and list the unallocated requirements.4. Detect any requirement allocated to more than one item.5. Group the register per item and gate the item development handoff.## Pitfalls- Allocating the same requirement to two items; the register allows only one allocation per requirement.- Scoring coverage without the full requirement id set; the ratio is only valid over the complete list.- Assigning a requirement to an item that is not in the design breakdown; the item must exist.- Reusing an allocation register across programs without clearing it.## Behavior contract (gate 3)The allocation and coverage logic is exercised by the gate 3 contracttest: scripts/test_requirements_allocation.py againstscripts/requirements_allocation_logic.py (stdlib unittest, offline).Run: python3 scripts/test_requirements_allocation.py## Compliance- Standards referenced, not reproduced: ARP4754A text is proprietary (SAE); summary-only per standards-map.yaml. Allocation to items is common development methodology.- compliance: STANDARDS-REF, gated: false.

Frequently asked questions