ECSS Systems Engineering — TS Establishment Process (space-systems/ecss/e1006-process)
Use when the task is to execute the Technical Specification establishment
process of ECSS-E-ST-10C §5, advancing through the phase-0 preliminary
TS tasks (F1.1–F1.4) and the phase-A TS tasks (F1.5–F1.10), verifying
prerequisites at each step, and iterating requirements at each
decomposition level until the baseline is stable.
Domain quick reference
- ECSS-E-ST-10C §5 divides the TS establishment process into two
phases: phase-0 produces a preliminary Technical Specification through
four tasks (F1.1–F1.4), and phase-A produces the phase-A Technical
Specification through six tasks (F1.5–F1.10). Each task has explicit
prerequisites that must be complete before the task may start; no task
may be opened out of order.
- Phase-0 task sequence: (F1.1) establish mission context and top-level
constraints; (F1.2) derive the initial system requirements from that
context; (F1.3) perform the first-pass system decomposition and
allocate requirements to each system element; (F1.4) document and
issue the preliminary TS as the phase-0 output.
- Phase-A task sequence: (F1.5) refine the functional architecture and
establish the functional baseline; (F1.6) allocate performance budgets
to system elements; (F1.7) define interface requirements at element
boundaries; (F1.8) conduct feasibility trade studies and record the
selected approach; (F1.9) iterate requirements at each decomposition
level until all open changes are resolved; (F1.10) issue the phase-A
Technical Specification. Tasks F1.6, F1.7, and F1.8 may proceed
concurrently after F1.5; F1.9 requires all three to be complete before
it may start.
- Iteration at each decomposition level (task F1.9) is not complete
until the open requirement change count at that level reaches zero.
A level with even a single unresolved change blocks issuance of the
phase-A TS. The absence of registered decomposition levels is not
evidence of convergence — every level must be explicitly tracked.
Workflow
- Confirm phase-0 entry: verify that mission objectives, operational
environment description, and top-level constraints are available as
inputs before opening F1.1.
- Execute F1.1 through F1.4 in prerequisite order. For each task,
confirm its prerequisites are complete before opening it; use the
blocking-task check to identify any outstanding dependencies.
- On completion of F1.4, confirm the preliminary TS has been issued
and baselined before opening any phase-A task.
- Open F1.5 as the single gateway into phase-A. After F1.5 is
complete, open F1.6, F1.7, and F1.8 concurrently; track each
independently.
- Open F1.9 only after F1.6, F1.7, and F1.8 are all marked complete.
For each decomposition level, register an open requirement change
count; iterate — revisiting allocations, interface definitions, and
trade-study results as needed — until the count reaches zero at
every registered level.
- Open F1.10 only after F1.9 shows zero open changes at all
decomposition levels. Issue the phase-A Technical Specification.
- Perform a final status check: phase_0_complete and phase_a_complete
must both be True, and all_levels_converged must be True (with at
least one level registered), before declaring the TS establishment
process complete.
Pitfalls
- Opening a task before its prerequisites are complete — F1.2 without
F1.1, F1.9 without all of F1.6, F1.7, and F1.8, F1.10 without F1.9.
A prerequisite check must return True before any task is opened.
- Treating iteration convergence as optional — if any decomposition
level carries unresolved requirement changes when F1.9 is declared
done, the phase-A TS baseline is unstable and F1.10 must not be
executed.
- Conflating phase-0 completion with phase-A readiness — F1.4 issues
only a preliminary TS; all six phase-A tasks must follow before the
process is complete.
- Skipping phase-0 and attempting to enter phase-A directly — the
preliminary TS produced by F1.1–F1.4 is a required input to F1.5.
- Relying on an empty decomposition-level dict as proof of convergence
— the module returns all_levels_converged as True by vacuous logic
when no levels are registered; the correct approach is to register
every level in use and confirm each reaches zero open changes before
completing F1.9.
Behavior contract (gate 3)
The task-validation, prerequisite-checking, iteration-convergence,
phase-completeness, and overall-status logic is exercised by the gate 3
contract test: scripts/test_e1006_process.py against
scripts/e1006_process_logic.py (stdlib unittest, offline). Run:
python3 scripts/test_e1006_process.py
Compliance
- ECSS standards are freely downloadable (ESA); cite the source and
paraphrase per standards-map.yaml.
- compliance: STANDARDS-REF, gated: false.
1---2name: e1006-process3description: "Use when execute the Technical Specification establishment process under ECSS-E-ST-10C §5: advance through phase-0 preliminary TS tasks (F1.1–F1.4), verify that prerequisites are satisfied before starting each task, iterate requirements at each decomposition level until no open changes remain, then advance through phase-A TS tasks (F1.5–F1.10) and issue the phase-A Technical Specification. Trigger: ecss, e-st-10-system-scope, ts-establishment, technical-specification, phase-0, phase-a, requirements-iteration, decomposition, systems-engineering."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/e1006-process15 domain: space-systems16 subdomain: ecss17 tags: [ecss, e-st-10-system-scope, ts-establishment, technical-specification, requirements-iteration, decomposition, systems-engineering]18 version: 0.1.019 author: Aero Agent Skills20---2122# ECSS Systems Engineering — TS Establishment Process (space-systems/ecss/e1006-process)2324Use when the task is to execute the Technical Specification establishment25process of ECSS-E-ST-10C §5, advancing through the phase-0 preliminary26TS tasks (F1.1–F1.4) and the phase-A TS tasks (F1.5–F1.10), verifying27prerequisites at each step, and iterating requirements at each28decomposition level until the baseline is stable.2930## Domain quick reference3132- ECSS-E-ST-10C §5 divides the TS establishment process into two33 phases: phase-0 produces a preliminary Technical Specification through34 four tasks (F1.1–F1.4), and phase-A produces the phase-A Technical35 Specification through six tasks (F1.5–F1.10). Each task has explicit36 prerequisites that must be complete before the task may start; no task37 may be opened out of order.38- Phase-0 task sequence: (F1.1) establish mission context and top-level39 constraints; (F1.2) derive the initial system requirements from that40 context; (F1.3) perform the first-pass system decomposition and41 allocate requirements to each system element; (F1.4) document and42 issue the preliminary TS as the phase-0 output.43- Phase-A task sequence: (F1.5) refine the functional architecture and44 establish the functional baseline; (F1.6) allocate performance budgets45 to system elements; (F1.7) define interface requirements at element46 boundaries; (F1.8) conduct feasibility trade studies and record the47 selected approach; (F1.9) iterate requirements at each decomposition48 level until all open changes are resolved; (F1.10) issue the phase-A49 Technical Specification. Tasks F1.6, F1.7, and F1.8 may proceed50 concurrently after F1.5; F1.9 requires all three to be complete before51 it may start.52- Iteration at each decomposition level (task F1.9) is not complete53 until the open requirement change count at that level reaches zero.54 A level with even a single unresolved change blocks issuance of the55 phase-A TS. The absence of registered decomposition levels is not56 evidence of convergence — every level must be explicitly tracked.5758## Workflow59601. Confirm phase-0 entry: verify that mission objectives, operational61 environment description, and top-level constraints are available as62 inputs before opening F1.1.632. Execute F1.1 through F1.4 in prerequisite order. For each task,64 confirm its prerequisites are complete before opening it; use the65 blocking-task check to identify any outstanding dependencies.663. On completion of F1.4, confirm the preliminary TS has been issued67 and baselined before opening any phase-A task.684. Open F1.5 as the single gateway into phase-A. After F1.5 is69 complete, open F1.6, F1.7, and F1.8 concurrently; track each70 independently.715. Open F1.9 only after F1.6, F1.7, and F1.8 are all marked complete.72 For each decomposition level, register an open requirement change73 count; iterate — revisiting allocations, interface definitions, and74 trade-study results as needed — until the count reaches zero at75 every registered level.766. Open F1.10 only after F1.9 shows zero open changes at all77 decomposition levels. Issue the phase-A Technical Specification.787. Perform a final status check: phase_0_complete and phase_a_complete79 must both be True, and all_levels_converged must be True (with at80 least one level registered), before declaring the TS establishment81 process complete.8283## Pitfalls8485- Opening a task before its prerequisites are complete — F1.2 without86 F1.1, F1.9 without all of F1.6, F1.7, and F1.8, F1.10 without F1.9.87 A prerequisite check must return True before any task is opened.88- Treating iteration convergence as optional — if any decomposition89 level carries unresolved requirement changes when F1.9 is declared90 done, the phase-A TS baseline is unstable and F1.10 must not be91 executed.92- Conflating phase-0 completion with phase-A readiness — F1.4 issues93 only a preliminary TS; all six phase-A tasks must follow before the94 process is complete.95- Skipping phase-0 and attempting to enter phase-A directly — the96 preliminary TS produced by F1.1–F1.4 is a required input to F1.5.97- Relying on an empty decomposition-level dict as proof of convergence98 — the module returns all_levels_converged as True by vacuous logic99 when no levels are registered; the correct approach is to register100 every level in use and confirm each reaches zero open changes before101 completing F1.9.102103## Behavior contract (gate 3)104105The task-validation, prerequisite-checking, iteration-convergence,106phase-completeness, and overall-status logic is exercised by the gate 3107contract test: scripts/test_e1006_process.py against108scripts/e1006_process_logic.py (stdlib unittest, offline). Run:109python3 scripts/test_e1006_process.py110111## Compliance112113- ECSS standards are freely downloadable (ESA); cite the source and114 paraphrase per standards-map.yaml.115- compliance: STANDARDS-REF, gated: false.