executing-plans

To safely execute a development plan, you process implementation tasks in small batches and pause for human review at critical checkpoints. This ensures errors are caught early through iterative task completion and feedback loops before proceeding.

Batch processing for implementation plans means executing a small group of development tasks sequentially within an isolated git worktree session, then pausing operations to report outputs and await architect or human approval before starting the next batch.

Git worktrees provide isolated workspace setup for development workflow execution by creating separate working directories. This allows batch plan execution and testing without affecting the main repository, ensuring safe review checkpoints and branch isolation.

Yes, during critical plan review, the execution process stops automatically upon encountering uncertainties or blockers. It reviews plans for gaps and pauses batch processing to prevent compounding errors until human oversight is provided.

Yes, you can load a written implementation plan from a file like plan.md and execute specific batches. The workflow starts with the first group of tasks, such as updating dependencies, then reports outputs for approval.

Yes, finishing development branches requires integration with sub-skills. After completing the batch executions and passing review checkpoints within the git worktree, these sub-skills handle the finalization of the development workflow.