cdd-implement-todo
CDD Implement TODO (explicit-only)
Implement exactly one TODO step in the target repo, run that step's Automated checks, update the active TODO file to mark that step's tasks done on success, and return a UAT checklist.
Do not invent missing product, architecture, sequencing, or validation decisions during implementation. If the selected step is not decision-complete, patch the TODO step first.
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-plan
Plan work by updating the CDD contract + implementation-ready TODO steps (approval-gated, 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).
10