executing-plans

Executing a multi-step implementation plan requires controlled task sequencing and review checkpoints. This Skill breaks work into ordered tasks, enforces critical plan review, tracks progress task-by-task, and runs required verification checks before completion handoff.

Managing plan-driven refactors across separate sessions requires disciplined task tracking and blocker escalation. This Skill reads your approved plan, executes each task with controlled sequencing, pauses for clarification when blocked, and hands off finished work to branch-completion workflows.

Yes, this plan execution approach suits multi-step software delivery with code review checkpoints. It enforces critical plan review before work begins, applies task-by-task tracking, runs verification steps, and escalates blockers to ensure disciplined implementation handoffs.

Handling blockers during implementation plan execution requires pausing for clarification and escalating issues. This Skill stops work when blocked, surfaces concerns during initial plan review, and enforces verification checks before proceeding to the next ordered task.

Yes, you need an approved development plan before starting plan execution. This Skill reads the written implementation plan first, surfaces concerns before work begins, and then executes each task with verification and blocker checks until the work is complete.

You should avoid controlled task sequencing for implementation work when you lack an approved development plan or need ad-hoc coding without review checkpoints. This Skill enforces critical plan review, task-by-task tracking, and verification steps designed for multi-step software delivery.