spec-execution

Automating specification implementation with a clean git history is achieved by executing tasks in planned waves and committing code after each wave. This approach breaks down complex feature specifications into manageable parallel and sequential changes, ensuring verifiable progress.

Wave-based task execution works by planning parallel and sequential changes for complex feature specifications. Each wave is implemented, verified through type-checking and testing, and then committed to git, while the specification document is synchronized to reflect completed tasks and deviations.

Yes, sub-agent orchestration is required to execute specification documents. Leveraging sub-agents for individual tasks maintains focused context during implementation, which improves results and ensures methodical, wave-by-wave execution of the defined specification.

The best way to track implementation progress for detailed planning documents is to update the specification document after each execution wave. This synchronization reflects completed tasks and deviations, providing a clear audit trail alongside incremental git commits.

No, executing a specification file includes built-in verification steps like type-checking and testing after each wave. These verification steps are automatically applied during the implementation process to ensure code quality before committing the changes to git.

You should avoid automated spec execution workflows when a detailed planning document or defined specification is not available. This methodical, wave-by-wave execution approach requires a structured specification file to plan, execute, and track implementation effectively.