Menú
Coherence-Driven Development. Use for substantial changes that require explicit selection, artifact flow, review, release, and post-release closure.
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
α 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 | cdd |
| description | Coherence-Driven Development. Use for substantial changes that require explicit selection, artifact flow, review, release, and post-release closure. |
| artifact_class | skill |
| kata_surface | embedded |
| governing_question | How do we evolve a system through a substantial change without losing coherence across selection, implementation, review, release, and closure? |
| visibility | public |
| triggers | ["review","release","issue","design","plan","assess","post-release","ship","tag"] |
| scope | global |
| inputs | ["substantial-change context","active role","issue or branch context"] |
| outputs | ["canonical method loaded","active role skill loaded","required lifecycle sub-skills selected"] |
| requires | ["CDD applies","CDD.md exists in this directory"] |
| calls | ["alpha/SKILL.md","beta/SKILL.md","gamma/SKILL.md","issue/SKILL.md","design/SKILL.md","plan/SKILL.md","review/SKILL.md","release/SKILL.md","post-release/SKILL.md"] |
This skill is the package-visible loader entrypoint for CDD. External dispatch enters through cdd only — internal sub-skill triggers (alpha, beta, gamma, issue, design, plan, review, release, post-release) are advisory and are used only after cdd and the active role skill have been loaded. The runtime must not expose internal sub-skills as public dispatch entrypoints.
When CDD applies:
CDD.md in this directory as the canonical algorithmalpha/SKILL.mdbeta/SKILL.mdgamma/SKILL.mdCDD.md is the only normative source for:
Role skills may add:
Role skills may not redefine:
CDD.mdalpha/ — α role: implementation, self-coherence, pre-review gatebeta/ — β role: review, release, β close-outgamma/ — γ role: issue quality, dispatch, unblocking, close-out triage, process iterationoperator/ — δ role: external gates, session routing, override authoritydesign/ — design artifact productionissue/ — issue creation and structureplan/ — implementation planningreview/ — code review protocolrelease/ — merge, tag, deploypost-release/ — assessment and closureIf this file and CDD.md disagree, CDD.md governs.
If a role skill and CDD.md disagree on ordered steps, selection rules, or artifact contract, CDD.md governs.
If a role skill adds execution detail, gates, or evidence requirements for a CDD.md step without changing that step's order or meaning, the role skill governs for that local execution detail.