executing-plans

To execute an implementation plan without skipping steps, load the written plan, review it for concerns, and process each task sequentially. You must run specified testing verifications and stop when blocked, ensuring no safety checks are skipped during software development.

Managing multi-step software development in isolated worktrees requires tracking each task sequentially while preserving order. You should apply review checkpoints, handle explicit blockers, and verify all changes before finalizing the development branch.

To handle blockers during task execution, stop the workflow immediately when an issue is encountered. Review checkpoints are managed by explicitly tracking progress and requesting clarification before proceeding to the next phase of the implementation plan.

Yes, a written implementation plan is required before starting branch completion. The workflow depends on loading an existing plan to identify concerns, request clarification, and preserve the specific task order and verification steps needed to finalize changes.

You should not use an automated workflow for implementation plans if your task lacks explicit verification steps or review checkpoints. It requires critical plan review and dependency on other skills, making it unsuitable for simple, single-step edits without testing requirements.