esdd-apply

Spec-driven task implementation is automated by reading proposal, design, and tasks artifacts, then dispatching parsed work to specialized agents. An orchestrator workflow tracks progress while handling worktrees, lint, and automatic merging and commits.

Spec-driven change orchestration coordinates implementation by reading specification artifacts and dispatching tasks to multiple agents. It is needed when implementing complex changes that require reading context files, parsing tasks, and tracking progress across specialized workers.

To start the orchestrated workflow, begin by generating a proposal which creates the necessary spec artifacts. The orchestrator then reads these context files, parses the tasks, and dispatches workers to execute the implementation automatically.

Yes, the orchestrator handles git worktrees, lint, and automatic merging and commits. It coordinates the specialized agent teams to execute parsed tasks while tracking progress throughout the entire workflow.

Spec-driven orchestration supports an optional dev-mode that surfaces lessons-learned from runs. This feature provides insights from previous executions while the orchestrator continues coordinating agent dispatch and progress tracking.

Orchestration through agent dispatch depends on existing spec artifacts like proposals, designs, and tasks. Without generating these initial context files, the orchestrator cannot parse tasks or dispatch workers to begin the automated implementation workflow.