speckit-implement

The orchestration workflow enforces dependencies and parallelization rules while executing tests before corresponding implementations. This ensures tasks are marked completed in tasks.md only after passing validation checkpoints, halting on failures with next-step guidance.

Yes, the orchestration workflow enforces dependencies and parallelization rules while executing tests before corresponding implementations. This ensures tasks are marked completed in tasks.md only after passing validation checkpoints, halting on failures with next-step guidance.

The best way to orchestrate multi-phase development is using a file-driven coordination model that progresses through Setup, Tests, Core, Integration, and Polish phases. It provides progress reporting, validation checkpoints, and error handling with guidance for next steps after each phase.

Yes, you need a formal task plan in tasks.md and supporting configuration in plan.md before execution. The workflow identifies and loads these files to drive the phase-based implementation, automatically marking completed tasks in tasks.md as they pass validation.

The implementation halts on failures to prevent cascading errors, providing next-step guidance instead of continuing. It validates checkpoints and runs tests before code, stopping execution when a task fails its validation to ensure the tasks.md plan remains accurate.