executing-plans

Load the plan file, review it critically and raise concerns before starting, then execute tasks in batches of three with TodoWrite tracking. After each batch, report what was implemented with verification output and wait for feedback before continuing.

Execute the default batch of the first three tasks, marking each in_progress then completed after running its specified verifications. When the batch finishes, show the implementation and verification output, say ready for feedback, and wait before starting the next batch.

Stop executing immediately when you hit a blocker, unclear instruction, or repeated verification failure. Ask your human partner for clarification rather than guessing, and return to plan review if the fundamental approach needs rethinking.

No. Never start implementation on main or master without explicit user consent. The workflow requires setting up an isolated workspace first, using the using-git-worktrees skill before executing any plan tasks.

After all tasks complete and pass verification, the workflow hands off to the finishing-a-development-branch skill. That sub-skill verifies tests, presents completion options, and executes the chosen option to close out the development work.