executing-plans

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

2|Updated May 30, 2026
One-click install
npx skills add https://github.com/virahitvin8/crafty-gis --skill executing-plans-virahitvin8
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: executing-plans
Source: https://github.com/virahitvin8/crafty-gis/tree/main/GIT_STAR/assignment-generator/antigravity-skills-main/antigravity-skills-main/skills/executing-plans
Command: npx skills add https://github.com/virahitvin8/crafty-gis --skill executing-plans-virahitvin8

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Written implementation plans often go stale or get executed inconsistently when developers improvise mid-task. This Skill enforces disciplined execution of a pre-written plan in a separate session, with critical review upfront and verification after every task. ## Core Features & Use Cases - Critical Plan Review: Loads the plan file and raises questions or concerns with the human partner before writing any code. - Task-by-Task Execution: Tracks each task with a todo list, follows bite-sized steps exactly, and runs the verifications specified in the plan. - Stop-on-Blocker Discipline: Halts and asks for clarification when dependencies are missing, tests fail, or instructions are unclear instead of guessing. - Use Case: You have a detailed implementation plan from a planning session. Hand it to this Skill in a fresh session and it executes every task, runs the specified verifications, and hands off to a branch-finishing workflow when complete. ## Quick Start Use the executing-plans skill to implement the plan in docs/plans/feature-x.md and stop if anything is unclear.

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?

Provide the plan file and invoke the executing-plans skill. It reviews the plan critically, raises concerns before starting, then executes each task in order with a todo list, running the verifications specified in the plan.

What should I do before running an implementation plan?

Ensure the plan is written with bite-sized steps and explicit verification commands, and that you are on an isolated branch or git worktree rather than main. The skill refuses to start implementation on main/master without explicit consent.

What happens when a plan step fails or is unclear?

Execution stops immediately when a blocker appears, such as a missing dependency, failing test, or ambiguous instruction. The skill asks the human partner for clarification rather than guessing or forcing through the blocker.

Does executing-plans work without subagent support?

Yes, it works in a single session, but the documentation notes that platforms with subagent support produce higher-quality results. On such platforms, a subagent-driven development skill is recommended instead.

When should I not use a plan-execution workflow?

Avoid it when there is no written plan yet, when the plan has critical gaps preventing a start, or when the fundamental approach needs rethinking. In those cases, return to plan writing or review first.