sdd-init

To bootstrap spec-driven development context, run the initialization action in your project directory to automatically detect your tech stack and configure the appropriate persistence backend for immediate SDD work.

Spec-driven development context initialization detects project conventions and tech stacks to prepare your environment for specification work. You need it when starting SDD to avoid manual, error-prone project discovery and backend configuration.

Yes, project bootstrapping performs discovery across common stacks including Node, Python, and Go. It automatically detects tech stack cues and architecture conventions to tailor the spec-driven development environment to your specific project.

Configuring the persistence backend happens automatically during initialization based on detected project policy. You can select engram, openspec, or none, and if openspec is chosen, the config.yaml, specs, and changes directories are created immediately.

The best way to create the openspec directory structure is to run the SDD initialization action and select openspec as your persistence backend, which automatically generates the config.yaml, specs, and changes folders ready for specification work.

You need context detection because manual SDD initialization is error-prone and time-consuming. Automated discovery identifies your tech stack and conventions upfront, allowing the system to accurately configure persistence backends and tailor the bootstrap.