executing-plans

Executing Plans Skill

Walks an approved tasks/todo.md plan step by step: pick the next task, execute it, verify it, commit it, mark it done. Does NOT freelance new scope mid-execution and does NOT skip the verification gate.

When to Use

• A plan in tasks/todo.md has been approved.
• Starting or resuming a multi-step implementation.
• User says "go", "start", "execute", or "begin".
• A sub-agent batch finishes and the next batch is ready.
• NOT before the design is approved (use brainstorming first).

Prerequisites

• Approved tasks/todo.md containing ordered steps with acceptance criteria.
• git configured for atomic commits.
• The view, edit, and powershell Copilot tools.
• A green baseline test run.
• The verify-before-done skill available for the verification step.

How to Run

1. Read tasks/todo.md. Identify the next unchecked task.
2. Confirm its prerequisites are satisfied.
3. Execute the task.
4. Run the verify-before-done skill.
5. Append the Verification Results block.
6. Commit. Mark the checkbox `- [x]`.
7. Repeat. Post a short progress note every 2–3 tasks.

Quick Reference

Phase	Action	Tool
Load	Read tasks/todo.md	view
Execute	Make the change	edit, powershell
Verify	Tests + gate + diff	verify-before-done skill
Record	Append Verification Results	edit
Commit	One commit per task	powershell → git commit
Mark done	Flip - [ ] to - [x]	edit

Procedure

Step 1: Load the Plan

Open tasks/todo.md with view. Locate the next - [ ] step. If none exist, the plan is done — hand off to finishing-a-development-branch.

Step 2: Check Prerequisites

Read the task. Confirm any "depends on" notes are satisfied. If a prerequisite is missing, STOP — do not improvise around it; re-plan first.

Step 3: Execute Exactly One Task

Make the change. Resist the urge to bundle "while I'm here" cleanups. Scope discipline is the whole point of the plan.