Menu
CDS development lifecycle — v0.1 thin overlay. Canonical 0–13 steps, S0–S12 state machine, branch rule, pre-flight, and tier structure at CDS.md; mechanics delegate to cnos.cdd role + harness skills.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
α role in CDD. Implements the selected change, produces the review-ready artifact set, and writes α close-out.
β role in CDD. Reviews the change, merges on approval, and writes β close-out. δ owns the release boundary (tag/deploy/disconnect).
Compatibility pointer. Cross-repo handoff doctrine has moved to cnos.handoff/skills/handoff/cross-repo/SKILL.md as of cnos#416 (Sub 2 of cnos#404 handoff extraction).
δ role-skill. Owns the two-sided coherence-cell membrane (outward boundary decision on receipt + V verdict; inward implementation-contract enrichment at dispatch) and the override authority that compose with V's verdict per RECEIPT-VALIDATION.md.
Produce the design artifact for a substantial change: incoherence, challenged assumption, impact graph, acceptance criteria, and leverage.
ε role in CDD — the CDD-specific instantiation of the generic ε doctrine. Reads receipt streams across cycles, surfaces `cdd-*-gap` findings, applies MCA discipline, and writes `cdd-iteration.md` when the cycle's receipt has `protocol_gap_count > 0`.
| name | lifecycle |
| description | CDS development lifecycle — v0.1 thin overlay. Canonical 0–13 steps, S0–S12 state machine, branch rule, pre-flight, and tier structure at CDS.md; mechanics delegate to cnos.cdd role + harness skills. |
| artifact_class | skill |
| kata_surface | pointer |
| governing_question | How does a CDS cycle progress from observation through close-out across the 0–13 steps and S0–S12 state machine? |
| visibility | public |
| parent | cds |
| triggers | ["lifecycle"] |
| scope | lifecycle-phase |
| status | v0.1-thin-overlay |
This v0.1 operational overlay delegates mechanics to existing cnos.cdd
role + harness skills until the v1 role rewrite. Canonical content at
../CDS.md §"Development lifecycle".
The 0–13 step table, the S0–S12 state machine, the cycle/{N} branch
rule, the γ-owned branch pre-flight, and the tier-1a/1b/1c/2/3 skill
loading structure are stated canonically at
../CDS.md §"Development lifecycle". Cite that path.
Per-role mechanics across each state — v0.1 overlay:
../../../../cnos.cdd/skills/cdd/gamma/SKILL.md — γ (Steps 0–3, 11–13).../../../../cnos.cdd/skills/cdd/alpha/SKILL.md — α (Steps 4–7, fix-round, close-out).../../../../cnos.cdd/skills/cdd/beta/SKILL.md — β (Step 8 review + merge; pre-merge gate).../../../../cnos.cdd/skills/cdd/delta/SKILL.md — δ (Steps 9, 12; boundary).../../../../cnos.cdd/skills/cdd/harness/SKILL.md — runtime substrate (dispatch, polling, branch, identity).../../../../cnos.cdd/skills/cdd/release-effector/SKILL.md — tag/release/deploy at S12.../../../../cnos.cdd/skills/cdd/operator/SKILL.md — δ-the-operator session-routing.When v1 lands, this overlay retires or expands into a full CDS-side skill.