ECSS System Engineering — Specification Tree DRD (space-systems/ecss/e10-spec-tree-drd)
Use when the task is to produce or check a project's specification tree
against the Document Requirements Definition of ECSS-E-ST-10C Annex J --
the hierarchy of technical specifications that mirrors the product tree,
and the flow-down link each specification carries to its parent.
Domain quick reference
- The specification tree is not the product tree; it is the tree of
documents that specify it. The two are checked against each other,
and a specification with no product node is as much a defect as a
product with no specification.
- There is exactly one top-level system specification. Zero roots and
several roots are both structural defects, rejected before any
content check runs, because a malformed tree makes every downstream
finding unreliable.
- Structure is validated in a fixed order: unique identifiers, one
root, resolvable parent links, then reachability from the root.
The reachability pass is what catches a cyclic branch and a branch
detached from the apex, neither of which a parent-link check alone
can see.
- A specification's kind fixes its level -- system, subsystem,
equipment, part. A child must sit exactly one level below its
parent; a skipped level means a decomposition step was never
specified, so the requirements of that step have nowhere to live.
- Product coverage is exact, not minimal: a node with no
specification leaves requirements unstated, and a node specified
twice leaves two documents free to contradict each other. Both are
findings.
- Every non-root specification declares the parent it flows down
from, and that declaration must name its actual parent. A
flow-down link pointing somewhere else is worse than a missing one,
because the trace looks complete while leading to the wrong
requirement set.
- Structural defects raise; content gaps are collected as findings. A
defective tree cannot be assessed at all, while an incomplete one
can be reported on and finished.
Workflow
- Validate identifier uniqueness and the kind of every specification.
- Find the single top-level specification; reject a tree with none or
several.
- Confirm each non-root specification's parent link resolves, then
build the child index.
- Confirm every specification is reachable from the root, which
rejects both cycles and detached branches.
- Check each specification's level against its parent's, and confirm
the root sits at system level.
- Cross-check against the product tree: report nodes with no
specification and nodes specified more than once.
- Confirm every non-root specification declares a flow-down link that
names its actual parent.
- The tree is Annex J compliant only when the finding list is empty.
Pitfalls
- Treating the specification tree as a copy of the product tree.
They are cross-checked precisely because they can disagree, and
collapsing them hides exactly the gaps Annex J exists to surface.
- Validating parent links and stopping there. A branch whose parents
all resolve can still close on itself or hang detached from the
root; only the reachability pass finds it.
- Accepting a level skip as a harmless shortcut when a subsystem
talks straight to a part. The missing intermediate specification is
where that decomposition's requirements would have been written.
- Reading product coverage as "at least one specification". Two
specifications for one product is a live contradiction risk, not
redundancy.
- Accepting any non-empty flow-down field as a trace. A link that
names a specification other than the parent passes a presence check
and still points at the wrong requirement set.
- Listing a duplicate identifier alongside the content findings. It
makes every trace ambiguous, so the assessment must stop instead.
Behavior contract (gate 3)
The kind/level, identifier-uniqueness, root-finding, parent-link,
reachability, level-consistency, product-coverage and flow-down logic
is exercised by the gate 3 contract test:
scripts/test_e10_spec_tree_drd.py against
scripts/e10_spec_tree_drd_logic.py (stdlib unittest, offline). Run:
python3 scripts/test_e10_spec_tree_drd.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-spec-tree-drd3description: "Use when generate or validate a project specification tree against the ECSS-E-ST-10C Annex J Document Requirements Definition: confirm the tree is singly rooted, fully connected and free of duplicate identifiers, confirm each specification sits exactly one level below its parent, confirm every product-tree node carries exactly one specification, and confirm every non-root specification declares the parent it flows its requirements down from. Trigger: ecss, e-st-10-system-scope, specification-tree, annex-j-drd, requirement-flowdown, product-tree-coverage, specification-levels."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-spec-tree-drd15 domain: space-systems16 subdomain: ecss17 tags: [ecss, e-st-10-system-scope, specification-tree, annex-j-drd, requirement-flowdown, product-tree-coverage]18 version: 0.1.019 author: Aero Agent Skills20---2122# ECSS System Engineering — Specification Tree DRD (space-systems/ecss/e10-spec-tree-drd)2324Use when the task is to produce or check a project's specification tree25against the Document Requirements Definition of ECSS-E-ST-10C Annex J --26the hierarchy of technical specifications that mirrors the product tree,27and the flow-down link each specification carries to its parent.2829## Domain quick reference3031- The specification tree is not the product tree; it is the tree of32 documents that specify it. The two are checked against each other,33 and a specification with no product node is as much a defect as a34 product with no specification.35- There is exactly one top-level system specification. Zero roots and36 several roots are both structural defects, rejected before any37 content check runs, because a malformed tree makes every downstream38 finding unreliable.39- Structure is validated in a fixed order: unique identifiers, one40 root, resolvable parent links, then reachability from the root.41 The reachability pass is what catches a cyclic branch and a branch42 detached from the apex, neither of which a parent-link check alone43 can see.44- A specification's kind fixes its level -- system, subsystem,45 equipment, part. A child must sit exactly one level below its46 parent; a skipped level means a decomposition step was never47 specified, so the requirements of that step have nowhere to live.48- Product coverage is exact, not minimal: a node with no49 specification leaves requirements unstated, and a node specified50 twice leaves two documents free to contradict each other. Both are51 findings.52- Every non-root specification declares the parent it flows down53 from, and that declaration must name its actual parent. A54 flow-down link pointing somewhere else is worse than a missing one,55 because the trace looks complete while leading to the wrong56 requirement set.57- Structural defects raise; content gaps are collected as findings. A58 defective tree cannot be assessed at all, while an incomplete one59 can be reported on and finished.6061## Workflow62631. Validate identifier uniqueness and the kind of every specification.642. Find the single top-level specification; reject a tree with none or65 several.663. Confirm each non-root specification's parent link resolves, then67 build the child index.684. Confirm every specification is reachable from the root, which69 rejects both cycles and detached branches.705. Check each specification's level against its parent's, and confirm71 the root sits at system level.726. Cross-check against the product tree: report nodes with no73 specification and nodes specified more than once.747. Confirm every non-root specification declares a flow-down link that75 names its actual parent.768. The tree is Annex J compliant only when the finding list is empty.7778## Pitfalls7980- Treating the specification tree as a copy of the product tree.81 They are cross-checked precisely because they can disagree, and82 collapsing them hides exactly the gaps Annex J exists to surface.83- Validating parent links and stopping there. A branch whose parents84 all resolve can still close on itself or hang detached from the85 root; only the reachability pass finds it.86- Accepting a level skip as a harmless shortcut when a subsystem87 talks straight to a part. The missing intermediate specification is88 where that decomposition's requirements would have been written.89- Reading product coverage as "at least one specification". Two90 specifications for one product is a live contradiction risk, not91 redundancy.92- Accepting any non-empty flow-down field as a trace. A link that93 names a specification other than the parent passes a presence check94 and still points at the wrong requirement set.95- Listing a duplicate identifier alongside the content findings. It96 makes every trace ambiguous, so the assessment must stop instead.9798## Behavior contract (gate 3)99100The kind/level, identifier-uniqueness, root-finding, parent-link,101reachability, level-consistency, product-coverage and flow-down logic102is exercised by the gate 3 contract test:103scripts/test_e10_spec_tree_drd.py against104scripts/e10_spec_tree_drd_logic.py (stdlib unittest, offline). Run:105python3 scripts/test_e10_spec_tree_drd.py106107## Compliance108109- ECSS standards are freely downloadable (ESA); cite the source and110 paraphrase per standards-map.yaml.111- compliance: STANDARDS-REF, gated: false.