executing-plans

To execute a written implementation plan step by step, load your roadmap into the skill to critique it for gaps, then follow the structured execution workflow to process tasks sequentially while reporting blockers and validation results.

The best way to track progress and handle blockers during a multi-step software task is using a structured execution workflow that marks stepwise progress, detects blockers automatically, and validates each task before moving to the next checkpoint.

To validate task completion during refactoring or feature delivery, apply a controlled engineering workflow that requires explicit verification steps and final reporting after each task is executed from your written plan.

Yes, you can use a development workflow with git worktrees for checkpointed development sessions, as this skill supports isolated execution environments and clean finishes for multi-step engineering tasks like feature delivery and bug fixing.

Yes, this plan execution approach reviews dependencies and hidden assumptions before work begins by critically checking task order, validation criteria, and potential gaps in your written implementation plan.

You should not use a structured plan execution workflow for simple, single-step software tasks that do not require explicit task sequencing, blocker detection, checkpointed development, or final validation reporting.