ECSS Per-Phase SE Task Overview (space-systems/ecss/e10-phase-task-overview)
Use when checking which system engineering tasks belong to each
project lifecycle phase under ECSS-E-ST-10C clause 4.3.3-4.3.9, and
whether the project is tracking them against SEP-driven deliverables.
When to use
- Planning phase content: which SE tasks run in phase 0 (mission
analysis) vs A (feasibility) vs B (definition) vs C/D (design and
qualification) vs E (operations) vs F (disposal).
- Auditing a project plan against the generic per-phase task list.
- Preparing for a phase review when the phase task list must be
complete and its outputs delivered.
Domain quick reference
Generic per-phase SE task clusters (informative, E-ST-10C 4.3):
- Phase 0: mission needs capture, feasibility assessment, top-level
requirement drafting.
- Phase A: system requirement definition, concept trade-off,
preliminary specification tree.
- Phase B: preliminary design definition, requirement baseline
freeze, interface definition.
- Phase C: detailed design definition, verification planning,
requirement closure.
- Phase D: qualification test execution, acceptance test execution,
as-built documentation.
- Phase E: in-orbit commissioning, operational maintenance support,
anomaly resolution.
- Phase F: disposal execution, close-out reporting.
The concrete deliverable set is not fixed by this list alone: the
project's System Engineering Plan (SEP, clause 5.1) tailors it.
Procedure
- Run the offline test to confirm the module contract:
python3 scripts/test_e10_phase_task_overview.py.
- From Python:
import e10_phase_task_overview_logic as pt
pt.tasks_for("B") # tuple of SE tasks for phase B
- Compare the returned task list with the project plan's phase
content. Missing tasks are plan gaps to resolve before the phase
review.
Verification
- The offline unittest suite passes.
- Every phase 0 through F returns a non-empty task tuple.
1---2name: e10-phase-task-overview3description: "Use when checking per-phase system engineering task lists and outputs under ECSS-E-ST-10C: confirm the project's tasks for lifecycle phases 0 through F (mission analysis through disposal) are identified and tracked against the System Engineering Plan (SEP) deliverables. ECSS-E-ST-10C clause 4.3.3-4.3.9 gives the informative per-phase task overview. Trigger: ecss, e-st-10c, phase task, lifecycle phase, phase 0, phase A, phase B, phase C, phase D, phase E, phase F, systems engineering, 4.3.3, space 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/e10-phase-task-overview15 domain: space-systems16 subdomain: ecss17 tags: [ecss, e-st-10c, phase-task-overview, lifecycle, phase-0, phase-a, phase-b, phase-c, phase-d, phase-e, phase-f, systems-engineering]18 version: 0.1.019 author: Aero Agent Skills20---2122# ECSS Per-Phase SE Task Overview (space-systems/ecss/e10-phase-task-overview)2324Use when checking which system engineering tasks belong to each25project lifecycle phase under ECSS-E-ST-10C clause 4.3.3-4.3.9, and26whether the project is tracking them against SEP-driven deliverables.2728## When to use2930- Planning phase content: which SE tasks run in phase 0 (mission31 analysis) vs A (feasibility) vs B (definition) vs C/D (design and32 qualification) vs E (operations) vs F (disposal).33- Auditing a project plan against the generic per-phase task list.34- Preparing for a phase review when the phase task list must be35 complete and its outputs delivered.3637## Domain quick reference3839Generic per-phase SE task clusters (informative, E-ST-10C 4.3):4041- Phase 0: mission needs capture, feasibility assessment, top-level42 requirement drafting.43- Phase A: system requirement definition, concept trade-off,44 preliminary specification tree.45- Phase B: preliminary design definition, requirement baseline46 freeze, interface definition.47- Phase C: detailed design definition, verification planning,48 requirement closure.49- Phase D: qualification test execution, acceptance test execution,50 as-built documentation.51- Phase E: in-orbit commissioning, operational maintenance support,52 anomaly resolution.53- Phase F: disposal execution, close-out reporting.5455The concrete deliverable set is not fixed by this list alone: the56project's System Engineering Plan (SEP, clause 5.1) tailors it.5758## Procedure59601. Run the offline test to confirm the module contract:61 `python3 scripts/test_e10_phase_task_overview.py`.622. From Python:6364```python65import e10_phase_task_overview_logic as pt66pt.tasks_for("B") # tuple of SE tasks for phase B67```68693. Compare the returned task list with the project plan's phase70 content. Missing tasks are plan gaps to resolve before the phase71 review.7273## Verification7475- The offline unittest suite passes.76- Every phase 0 through F returns a non-empty task tuple.