executing-plans

Installation

Summary

Execute a written implementation plan with critical review and task checkpoints.

Requires loading and critically reviewing the plan before execution; raises concerns with the human partner if issues are identified
Executes tasks sequentially, marking progress and running verifications as specified in the plan
Stops immediately on blockers (missing dependencies, test failures, unclear instructions) rather than guessing; asks for clarification
Integrates with git-worktrees for isolated workspaces and finishing-a-development-branch to complete the work after all tasks verify
Works best on platforms with subagent support; recommends subagent-driven-development skill as the preferred alternative when available

SKILL.md

Executing Plans

Execute the plan yourself, task by task, in this session: no implementer subagent per task, no reviewer per task. One fresh-context review of the whole branch at the end.

Why inline: Subagent-driven development pays for a fresh implementer and a fresh reviewer on every task, each re-reading the codebase from zero. Inline execution pays for one context (yours) plus one reviewer at the end. What it gives up is a fresh context per task and a second pair of eyes per task. This skill keeps what those two things bought, by other means: the brief is the spec, the ledger is your memory, TDD is the per-task gate, and the final reviewer is the second pair of eyes.

Core principle: The plan already did the thinking. Execute it exactly, prove each step with a test you watched fail and then pass, and leave a record that survives your own forgetting.

Related skills