ECSS TRS Flow-Down (space-systems/ecss/e10-trs-flowdown)
Use when the task is establishing next-lower-level technical
requirements specifications (TRS) from a customer technical
specification (TS) under ECSS-E-ST-10C clause 5.2.3.1: one TRS per
product/configuration item, kept consistent with the customer TS and
with each other, and structured per E-ST-10-06.
Domain quick reference
- Flow-down takes the customer TS for a product and produces one TRS
per next-lower-level product (configuration item); each TRS must
stay consistent with the parent TS and with sibling TRS documents
at the same level.
- A requirement "flows down" when at least one child TRS explicitly
carries it (by shared requirement identifier); a TS requirement
with no child carrying it has not been flowed down.
- Consistency has two directions: parent-child (a TRS value must not
contradict the TS value for the same requirement id) and sibling
(two TRS documents must not assign different values to a
requirement id they both carry).
- E-ST-10-06 governs TRS document structure; at minimum a conformant
TRS states its scope, the applicable/reference documents it
depends on, its requirement set, and how each requirement will be
verified.
- This leaf checks flow-down completeness and consistency and DRD
section presence; it does not allocate requirements to functions
(see e10-req-allocation), build the specification tree
(e10-spec-tree), or resolve general internal inconsistencies
(e10-req-consistency).
Workflow
- Collect the customer TS requirement set (requirement id -> value)
for the product being decomposed.
- Collect each next-lower-level TRS as: the DRD sections present,
and its requirement set (requirement id -> value), for every
product/configuration item at that level.
- Check DRD section presence for each TRS against the minimum
section set; list any missing sections.
- Check flow-down coverage: every TS requirement id must appear in
at least one TRS's requirement set; list any that do not.
- Check parent-child consistency: for a requirement id carried by
both the TS and a TRS, the values must match; list mismatches.
- Check sibling consistency: for a requirement id carried by more
than one TRS, the values must match across TRS documents; list
mismatches.
- Flow-down is ready only when there are no missing sections, no
coverage gaps, and no parent-child or sibling conflicts; otherwise
report the specific issues found for correction before proceeding
to consolidation (e10-req-consolidation) and sign-off
(e10-req-agreement).
Pitfalls
- Marking flow-down complete while a TS requirement has not been
picked up by any child TRS (silent coverage gap).
- Letting a TRS restate a parent requirement with a changed value
without recording it as a deliberate, agreed deviation.
- Two sibling TRS documents assigning different values to a shared
requirement (e.g. a common interface constraint) without
reconciliation.
- Treating a TRS as flow-down-complete when it is missing the
scope, applicable-documents, requirements, or verification
sections expected of a technical requirements specification.
Behavior contract (gate 3)
The section-check, coverage, and consistency logic is exercised by
the gate 3 contract test: scripts/test_e10_trs_flowdown.py against
scripts/e10_trs_flowdown_logic.py (stdlib unittest, offline). Run:
python3 scripts/test_e10_trs_flowdown.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-trs-flowdown3description: "Use when flowing customer technical requirements down to next-lower-level technical requirements specifications (TRS) per ECSS-E-ST-10C clause 5.2.3.1: check every customer TS requirement reaches at least one child TRS, that no child TRS value contradicts the parent TS or a sibling TRS, and that each TRS carries the document structure expected by E-ST-10-06. Trigger: ecss, e-st-10c, trs flowdown, technical requirements specification, requirement flow-down, customer TS, next-lower-level requirements, e-st-10-06."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-trs-flowdown15 domain: space-systems16 subdomain: ecss17 tags: [ecss, e-st-10c, trs, flowdown, requirements, e-st-10-06]18 version: 0.1.019 author: Aero Agent Skills20---2122# ECSS TRS Flow-Down (space-systems/ecss/e10-trs-flowdown)2324Use when the task is establishing next-lower-level technical25requirements specifications (TRS) from a customer technical26specification (TS) under ECSS-E-ST-10C clause 5.2.3.1: one TRS per27product/configuration item, kept consistent with the customer TS and28with each other, and structured per E-ST-10-06.2930## Domain quick reference3132- Flow-down takes the customer TS for a product and produces one TRS33 per next-lower-level product (configuration item); each TRS must34 stay consistent with the parent TS and with sibling TRS documents35 at the same level.36- A requirement "flows down" when at least one child TRS explicitly37 carries it (by shared requirement identifier); a TS requirement38 with no child carrying it has not been flowed down.39- Consistency has two directions: parent-child (a TRS value must not40 contradict the TS value for the same requirement id) and sibling41 (two TRS documents must not assign different values to a42 requirement id they both carry).43- E-ST-10-06 governs TRS document structure; at minimum a conformant44 TRS states its scope, the applicable/reference documents it45 depends on, its requirement set, and how each requirement will be46 verified.47- This leaf checks flow-down completeness and consistency and DRD48 section presence; it does not allocate requirements to functions49 (see e10-req-allocation), build the specification tree50 (e10-spec-tree), or resolve general internal inconsistencies51 (e10-req-consistency).5253## Workflow54551. Collect the customer TS requirement set (requirement id -> value)56 for the product being decomposed.572. Collect each next-lower-level TRS as: the DRD sections present,58 and its requirement set (requirement id -> value), for every59 product/configuration item at that level.603. Check DRD section presence for each TRS against the minimum61 section set; list any missing sections.624. Check flow-down coverage: every TS requirement id must appear in63 at least one TRS's requirement set; list any that do not.645. Check parent-child consistency: for a requirement id carried by65 both the TS and a TRS, the values must match; list mismatches.666. Check sibling consistency: for a requirement id carried by more67 than one TRS, the values must match across TRS documents; list68 mismatches.697. Flow-down is ready only when there are no missing sections, no70 coverage gaps, and no parent-child or sibling conflicts; otherwise71 report the specific issues found for correction before proceeding72 to consolidation (e10-req-consolidation) and sign-off73 (e10-req-agreement).7475## Pitfalls7677- Marking flow-down complete while a TS requirement has not been78 picked up by any child TRS (silent coverage gap).79- Letting a TRS restate a parent requirement with a changed value80 without recording it as a deliberate, agreed deviation.81- Two sibling TRS documents assigning different values to a shared82 requirement (e.g. a common interface constraint) without83 reconciliation.84- Treating a TRS as flow-down-complete when it is missing the85 scope, applicable-documents, requirements, or verification86 sections expected of a technical requirements specification.8788## Behavior contract (gate 3)8990The section-check, coverage, and consistency logic is exercised by91the gate 3 contract test: scripts/test_e10_trs_flowdown.py against92scripts/e10_trs_flowdown_logic.py (stdlib unittest, offline). Run:93python3 scripts/test_e10_trs_flowdown.py9495## Compliance9697- ECSS standards are freely downloadable (ESA); cite the source and98 paraphrase per standards-map.yaml.99- compliance: STANDARDS-REF, gated: false.