sdd-apply

Automating task implementation translates change requests into runnable code by reading specs, design documents, and task lists to generate concrete implementation steps. This orchestrator-driven workflow ensures consistent, code-first execution aligned with project configuration.

An orchestrator-driven workflow coordinates the execution of coding tasks by fetching change context, delta, and configuration. It guides the coder through validation and execution while ensuring traceability and conformance with repository conventions.

Yes, automated task implementation reads existing change materials including specs, design documents, and task lists. It uses these inputs to produce runnable code implementations that align with the provided project configuration and repository conventions.

Progress tracking during phase-based task execution updates the tasks.md file and generates mode-aware artifacts. The system modifies these tracking files depending on the configured mode, which includes openspec, engram, or none.

You should avoid automated end-to-end code implementation when your changes lack formal specs, design documents, or task lists. The workflow relies on these structured inputs to translate change requests into runnable code and guarantee consistent execution.