adopt

To add SDCD planning artifacts additively, inventory your repository to detect stack markers and docs, then scaffold design files like UR_PLAN.md and CURRENT_STATE.md. This approach proposes new planning artifacts and CLAUDE.md updates without modifying existing source files.

A repository state inventory for SDCD adoption scans your existing project to detect stack markers, documentation, and SDCD-like files. It assesses project readiness by classifying suitability and identifying exactly what SDCD practices need to be introduced during mid-flight adoption.

Yes, you can retrofit SDCD scaffolding into a running mid-flight project. The adoption workflow classifies your project suitability and generates an Ur-Plan stub draft to guide user decisions, proposing additive scaffolds and design artifacts without altering existing sources.

SDCD adoption scaffolding generates design/UR_PLAN.md, design/CURRENT_STATE.md, and CLAUDE.md updates. It produces an inventory block, a scaffold plan, and an Ur-Plan stub draft to guide your review when bootstrapping SDCD practices.

No, you do not need to modify your source files when bootstrapping SDCD. The adoption workflow is additive-only, proposing new planning artifacts and design files without touching your existing source code, ensuring a safe mid-project integration.