ECSS Requirement Analysis (space-systems/ecss/e10-req-analysis)
Use when the task is analysing customer or upper-level requirements
under ECSS-E-ST-10C clause 5.2.1: deriving, generating, controlling
and documenting the requirement set for the system and for each lower
level of the product tree.
Domain quick reference
- ECSS-E-ST-10C §5.2.1 requires that customer/upper-level requirements
are analysed and that a requirement set is produced for the system
and for each lower level, and that this set is derived, generated,
controlled, and documented.
- A requirement's origin is either "derived" (traced from analysis of
an upper-level or customer requirement) or "generated" (added at
this level to close a gap not directly implied by the upper level).
- Every requirement must trace, directly or through its parent chain,
to a customer requirement; a requirement whose declared parent does
not exist in the customer requirements or the requirement set is an
orphan and breaks the derivation.
- "Controlled" means the requirement is under configuration control:
released or baselined, not left in draft.
- "Documented" means the requirement carries identifying text and a
rationale, not just an id.
Workflow
- Collect the customer/upper-level requirement ids that the system
(or lower) level requirement set may trace to.
- For each candidate requirement, record id, level, parent (its
upper-level or customer requirement, or None for a customer-level
requirement), text, rationale, origin (derived/generated), and
control_status (draft/released/baselined).
- Validate every requirement record (all fields present and
non-empty, origin and control_status in the allowed sets).
- Check derivation traceability across the whole set: every
requirement's parent resolves to a customer requirement id or
another requirement in the set (no orphans, no duplicate ids).
- Check configuration-control readiness: every requirement is
released or baselined before treating the set as controlled;
list the ones still in draft.
- Review level coverage (counts per level) to confirm the set spans
the system level and each lower level in scope.
Pitfalls
- A requirement recorded with a parent id that was never captured in
the customer requirements or the requirement set (silent orphan).
- Treating a "draft" requirement as controlled because it has an id
and text — control requires released or baselined.
- Requirement text copied from the parent with no rationale, which
is documentation in form only.
- Duplicate requirement ids within the same level or across levels.
Behavior contract (gate 3)
The validation, derivation-traceability, control-readiness, and
level-coverage logic is exercised by the gate 3 contract test:
scripts/test_e10_req_analysis.py against
scripts/e10_req_analysis_logic.py (stdlib unittest, offline). Run:
python3 scripts/test_e10_req_analysis.py
Compliance
- ECSS standards are freely downloadable (ESA); cite the source and
paraphrase per standards-map.yaml.
- compliance: STANDARDS-REF, gated: false.
1---2name: e10-req-analysis3description: "Use when analysing customer or upper-level requirements to derive, generate, control and document the requirement set for a space system and for each lower level, per ECSS-E-ST-10C clause 5.2.1. Checks that every requirement traces to a customer requirement or an existing upper-level requirement (no orphans), carries identifying text and rationale (documented), and is under configuration control (released or baselined). Trigger: ecss, e-st-10c, requirement analysis, derive requirements, requirement derivation, requirement set, lower-level requirements, requirement control, 5.2.1."4license: Apache-2.05compliance: STANDARDS-REF6standards:7 - id: ecss8 reference-only: true9gated: false10domain: space-systems11pack: space-systems12compatibility: "agentskills.io SKILL.md; any SKILL.md host (Claude Code, Hermes, OpenClaw)"13metadata:14 source: https://skillmd.com/skills/ashfordeou/e10-req-analysis15 domain: space-systems16 subdomain: ecss17 tags: [ecss, e-st-10c, requirement-analysis, requirement-derivation, traceability, systems-engineering]18 version: 0.1.019 author: Aero Agent Skills20---2122# ECSS Requirement Analysis (space-systems/ecss/e10-req-analysis)2324Use when the task is analysing customer or upper-level requirements25under ECSS-E-ST-10C clause 5.2.1: deriving, generating, controlling26and documenting the requirement set for the system and for each lower27level of the product tree.2829## Domain quick reference3031- ECSS-E-ST-10C §5.2.1 requires that customer/upper-level requirements32 are analysed and that a requirement set is produced for the system33 and for each lower level, and that this set is derived, generated,34 controlled, and documented.35- A requirement's origin is either "derived" (traced from analysis of36 an upper-level or customer requirement) or "generated" (added at37 this level to close a gap not directly implied by the upper level).38- Every requirement must trace, directly or through its parent chain,39 to a customer requirement; a requirement whose declared parent does40 not exist in the customer requirements or the requirement set is an41 orphan and breaks the derivation.42- "Controlled" means the requirement is under configuration control:43 released or baselined, not left in draft.44- "Documented" means the requirement carries identifying text and a45 rationale, not just an id.4647## Workflow48491. Collect the customer/upper-level requirement ids that the system50 (or lower) level requirement set may trace to.512. For each candidate requirement, record id, level, parent (its52 upper-level or customer requirement, or None for a customer-level53 requirement), text, rationale, origin (derived/generated), and54 control_status (draft/released/baselined).553. Validate every requirement record (all fields present and56 non-empty, origin and control_status in the allowed sets).574. Check derivation traceability across the whole set: every58 requirement's parent resolves to a customer requirement id or59 another requirement in the set (no orphans, no duplicate ids).605. Check configuration-control readiness: every requirement is61 released or baselined before treating the set as controlled;62 list the ones still in draft.636. Review level coverage (counts per level) to confirm the set spans64 the system level and each lower level in scope.6566## Pitfalls6768- A requirement recorded with a parent id that was never captured in69 the customer requirements or the requirement set (silent orphan).70- Treating a "draft" requirement as controlled because it has an id71 and text — control requires released or baselined.72- Requirement text copied from the parent with no rationale, which73 is documentation in form only.74- Duplicate requirement ids within the same level or across levels.7576## Behavior contract (gate 3)7778The validation, derivation-traceability, control-readiness, and79level-coverage logic is exercised by the gate 3 contract test:80scripts/test_e10_req_analysis.py against81scripts/e10_req_analysis_logic.py (stdlib unittest, offline). Run:82python3 scripts/test_e10_req_analysis.py8384## Compliance8586- ECSS standards are freely downloadable (ESA); cite the source and87 paraphrase per standards-map.yaml.88- compliance: STANDARDS-REF, gated: false.