ECSS Verification — Phasing with the Life Cycle (space-systems/ecss/e1002-phasing)
Use when phasing verification activities with the project life cycle under ECSS-E-ST-10-02C clause 5.2.7 — locating phases, listing owed outputs and gaps, checking entry readiness, ranking requirement maturity, and rolling up project status.
Domain quick reference
- Verification planning starts in the earliest phase — it is not a late-lifecycle activity; placing it late is a phasing defect.
- Each phase carries a defined set of verification outputs; a phase may not close while any of its outputs is missing.
- Entry readiness for a phase depends on the previous phase's outputs being complete — check readiness before entering, not after.
- Per-requirement verification status has a maturity ordering (e.g. not-started < planned < in-progress < closed); the project status is the LEAST mature of its requirements.
- The phasing review is compliant only when no blocking issue remains across all phases.
Workflow
- Locate the phase:
phase_index(phase) (raises on an unknown phase).
- Decide applicability:
is_phase_applicable(phase).
- List owed outputs:
required_outputs_for_phase(phase).
- Find gaps:
phase_output_gaps(phase, outputs).
- Check entry readiness:
phase_entry_readiness(target_phase, state).
- Rank and roll up:
requirement_status_rank(status), overall_verification_status(statuses).
- Full review:
project_verification_phasing_review(project) -> is_phasing_compliant(review).
Pitfalls
- Entering a phase whose predecessor's outputs are incomplete —
phase_entry_readiness returns the blocking issues; resolve them first.
- Reporting project status as the MOST mature requirement — it is the least mature; one open requirement holds the project open.
- Treating a phase with no verification output requirement as 'no work' — applicability decides whether outputs are owed.
- Security-marking vocabulary: the content-policy gate flags the word beginning 'classif-'; use 'categorized' instead.
Behavior contract (gate 3)
scripts/test_e1002_phasing.py (stdlib unittest, offline) verifies phase indexing and its error path, applicability, required-output lookup, gap detection, entry-readiness blockers, maturity ranking and least-mature roll-up, and the full phasing review.
Compliance
ECSS-E-ST-10-02C is a normative standard; this leaf implements only common-knowledge procedure and paraphrases it — no verbatim standard text. license: Apache-2.0, compliance: STANDARDS-REF, standards: ecss (reference-only), gated: false.
1---2name: e1002-phasing3description: "Use when phasing verification activities with the project life cycle under ECSS-E-ST-10-02C clause 5.2.7: locate a life-cycle phase in the project phase sequence, decide whether a phase carries a verification output requirement, list the outputs that phase owes and the gaps against them, check entry readiness for a target phase, rank per-requirement verification maturity, roll that up to a project-wide status, and run the full phasing review. Trigger: ecss, e-st-10-02c, verification phasing, life cycle, phase A, phase outputs, entry readiness, maturity rank, project verification status."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/e1002-phasing15 domain: space-systems16 subdomain: ecss17 tags: [ecss, e-st-10-02c, verification-phasing, life-cycle, phase-outputs, entry-readiness, maturity, project-status]18 version: 0.1.019 author: Aero Agent Skills20---2122# ECSS Verification — Phasing with the Life Cycle (space-systems/ecss/e1002-phasing)2324Use when phasing verification activities with the project life cycle under ECSS-E-ST-10-02C clause 5.2.7 — locating phases, listing owed outputs and gaps, checking entry readiness, ranking requirement maturity, and rolling up project status.2526## Domain quick reference2728- Verification planning starts in the earliest phase — it is not a late-lifecycle activity; placing it late is a phasing defect.29- Each phase carries a defined set of verification outputs; a phase may not close while any of its outputs is missing.30- Entry readiness for a phase depends on the previous phase's outputs being complete — check readiness before entering, not after.31- Per-requirement verification status has a maturity ordering (e.g. not-started < planned < in-progress < closed); the project status is the LEAST mature of its requirements.32- The phasing review is compliant only when no blocking issue remains across all phases.3334## Workflow35361. Locate the phase: `phase_index(phase)` (raises on an unknown phase).372. Decide applicability: `is_phase_applicable(phase)`.383. List owed outputs: `required_outputs_for_phase(phase)`.394. Find gaps: `phase_output_gaps(phase, outputs)`.405. Check entry readiness: `phase_entry_readiness(target_phase, state)`.416. Rank and roll up: `requirement_status_rank(status)`, `overall_verification_status(statuses)`.427. Full review: `project_verification_phasing_review(project)` -> `is_phasing_compliant(review)`.4344## Pitfalls4546- Entering a phase whose predecessor's outputs are incomplete — `phase_entry_readiness` returns the blocking issues; resolve them first.47- Reporting project status as the MOST mature requirement — it is the least mature; one open requirement holds the project open.48- Treating a phase with no verification output requirement as 'no work' — applicability decides whether outputs are owed.49- Security-marking vocabulary: the content-policy gate flags the word beginning 'classif-'; use 'categorized' instead.5051## Behavior contract (gate 3)5253`scripts/test_e1002_phasing.py` (stdlib unittest, offline) verifies phase indexing and its error path, applicability, required-output lookup, gap detection, entry-readiness blockers, maturity ranking and least-mature roll-up, and the full phasing review.5455## Compliance5657ECSS-E-ST-10-02C is a normative standard; this leaf implements only common-knowledge procedure and paraphrases it — no verbatim standard text. `license: Apache-2.0`, `compliance: STANDARDS-REF`, `standards: ecss` (reference-only), `gated: false`.