cdd-plan
CDD Plan (explicit-only)
Treat the target repo’s CDD contract files as the source of truth:
AGENTS.mdREADME.mdTODO.md(and/orTODO-*.md)docs/specs/prd.mddocs/specs/blueprint.mddocs/INDEX.md(if present)
Runnable TODO step contract
For any new or rewritten execution step, produce an implementation-ready step rather than a placeholder summary.
More from ruphware/cdd-skills
cdd-boot
Boot a repo into vanilla AGENTS-driven mode by ingesting AGENTS.md plus project and development docs, gracefully when non-core files differ or are missing (explicit-only).
10cdd-index
Regenerate docs/INDEX.md only, using an embedded local CDD index prompt with phase-based analysis, GitHub-safe diagrams, fixed validation, and post-action review (approval-gated, explicit-only).
10cdd-maintain
Maintain a CDD repo by archiving long TODO and journal files, auditing support-doc drift, proposing approval-gated doc refreshes, and doctoring the codebase for refactor and dead-code signals (explicit-only).
10cdd-init-project
Init or adopt the CDD contract in the current folder (empty dir, docs-seeded folder, fresh boilerplate repo, or existing repo migration) (approval-gated, explicit-only; separate confirmation required for bootstrap copy/download and clone/remote/init/push actions).
10cdd-refactor
Turn refactor candidates in docs/INDEX.md into a TODO refactor plan (approval-gated, explicit-only).
10cdd-audit-and-implement
Convert audit bullets into implementation-ready TODO steps, then implement the first dependency-ordered step (two approvals, explicit-only).
10