executing-plans

To execute a written development plan, load and critically review it first, then proceed through each task sequentially. You must follow bite-sized steps exactly, run specified verifications, and stop immediately upon hitting blockers or unclear instructions before moving forward.

The best way to prevent skipping critical steps during plan execution is using explicit review checkpoints. You critically review the written plan before starting, then mark progress and run verifications after each task to ensure precise adherence to the development workflow.

Yes, you can use this workflow for multi-task development with git worktrees. It applies specifically to multi-task development workflows where each step must be followed precisely, requiring you to create and progress through tasks according to the plan.

When a task instruction is unclear during development plan execution, you must stop immediately. The workflow requires stopping on blockers or unclear instructions and resolving concerns with your human partner before proceeding to the next task.

Yes, you need a finishing workflow to complete a development branch after plan execution. After tasks finish and are verified, you must switch to a required finishing-a-development-branch workflow to complete the development and present verification options.