cdd-boot
CDD Boot (explicit-only)
Use this skill when the user wants a one-time vanilla CDD context boot and does not intend to use another cdd-* skill for the task.
Boot the current repo into vanilla AGENTS.md-driven work by reading role, project, and development context without changing repo files.
Required contract
AGENTS.mdat repo root- If
AGENTS.mdis missing, stop and tell the user the repo is not CDD-ready for vanilla boot. - Recommend
cdd-init-projectwhen the repo is missingAGENTS.md.
Preferred inputs
Role:
AGENTS.md
Project:
README.mddocs/INDEX.mddocs/specs/blueprint.md
More from ruphware/cdd-skills
cdd-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).
10cdd-audit-and-implement
Convert audit bullets into implementation-ready TODO steps, then implement the first dependency-ordered step (two approvals, explicit-only).
10