skills.rest
chhpt
chhptCOMMUNITY
Explore all skills by this author →
GitHub

executing-plans

Executes written implementation plans task-by-task with verification checkpoints and review gates.

Updated Aug 23, 2026
Search Tags:#workflow#code review#implementation#verification#plan execution#git worktree#task tracking
One-click install
npx skills add https://github.com/chhpt/skills --skill executing-plans-chhpt
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: executing-plans
Source: https://github.com/chhpt/skills/tree/main/skills/executing-plans
Command: npx skills add https://github.com/chhpt/skills --skill executing-plans-chhpt

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a written implementation plan into working code often goes wrong when steps are skipped, verifications are ignored, or blockers are guessed through. This Skill enforces a disciplined execution loop so plans are followed exactly and failures surface early. ## Core Features & Use Cases - Critical Plan Review: Loads the plan file and raises questions or concerns with you before any code is written. - Task-by-Task Execution: Tracks each task with TodoWrite, follows bite-sized steps exactly, and runs the specified verifications before marking tasks complete. - Stop-and-Ask Guardrails: Halts immediately on blockers, unclear instructions, or repeated verification failures instead of guessing. - Use Case: You have a multi-task implementation plan from a planning session. Hand it to this Skill in a fresh session and it executes every task, runs verifications, and finishes the development branch when done. ## Quick Start Execute the implementation plan in plan.md task by task, running all verifications and stopping to ask if anything is blocked.

Frequently Asked Questions about executing-plans

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I execute an implementation plan with an AI coding assistant?▼

Load the plan file, review it critically for gaps or concerns, then execute each task sequentially while running the specified verifications. Track progress with a todo list and mark tasks complete only after verification passes.

What should I do before starting to implement a written plan?▼

Read the entire plan and review it critically, raising any questions or concerns with your partner before writing code. Also set up an isolated workspace such as a git worktree, and never start implementation on the main branch without explicit consent.

What happens when a plan execution hits a blocker?▼

Execution stops immediately when hitting a blocker such as a missing dependency, failing test, or unclear instruction. The correct behavior is to ask for clarification rather than guessing or forcing through the problem.

When should I revisit the plan instead of continuing execution?▼

Return to the review step when your partner updates the plan based on feedback or when the fundamental approach needs rethinking. Do not push through blockers; stop and reassess the plan first.

Does this execution workflow require subagents?▼

Subagents are not strictly required, but the workflow notes significantly higher quality on platforms with subagent support such as Claude Code or Codex. If subagents are available, a subagent-driven development approach is recommended instead.

Related Skills

Explore More Software Engineering Skills→
joshsymondsjoshsymonds

writing-plans

Generate implementation plans as Claude Code Tasks with file paths and verification commands.

Community
Advanced
cristoslccristoslc

finishing-a-development-branch

Guides completion of development branches through structured merge, PR, keep, or discard options.

Community
Intermediate
dEitY719dEitY719

ai-worktree:spawn

Create an isolated git worktree for the active AI agent.

Community
Advanced
PlazaCCPlazaCC
2

subagent-driven-development

Execute implementation plan tasks with fresh subagents and two-stage reviews.

Official
Advanced