executing-plans

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

Updated Aug 26, 2026
One-click install
npx skills add https://github.com/danieliudi/trackforge-os --skill executing-plans-danieliudi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: executing-plans
Source: https://github.com/danieliudi/trackforge-os/tree/main/.cursor/skills/executing-plans
Command: npx skills add https://github.com/danieliudi/trackforge-os --skill executing-plans-danieliudi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? It turns a written implementation plan into completed work without losing discipline: plans get reviewed critically before execution, each task is tracked and verified, and blockers trigger a stop-and-ask instead of guesswork. ## Core Features & Use Cases - Critical plan review: Loads the plan, checks it for gaps or concerns, and raises questions with you before writing any code. - Task-by-task execution: Converts plan items into todos, marks each in progress, follows the bite-sized steps exactly, and runs the specified verifications. - Safe completion handoff: Finishes through the finishing-a-development-branch sub-skill, and refuses to start implementation on main/master without explicit consent. - Use Case: You have a multi-task refactor plan written in a previous session. Hand it over in a fresh session and have every task executed, verified, and wrapped up with review checkpoints along the way. ## Quick Start Execute the implementation plan in docs/refactor-plan.md using the executing-plans skill, reviewing it critically first and stopping to ask 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 written plan file and invoke the executing-plans skill. It loads the plan, reviews it critically, creates todos for each task, executes the steps exactly as written, and runs the specified verifications before reporting completion.

What happens if the plan has gaps or unclear instructions?

Execution stops immediately. The skill raises concerns with you before starting if the review finds problems, and during execution it asks for clarification rather than guessing when it hits blockers, failing tests, or ambiguous steps.

Can I run plan execution directly on the main branch?

No. The skill requires an isolated workspace, typically a git worktree, and never starts implementation on main or master without your explicit consent.

When should I use subagent-driven development instead of executing-plans?

Use subagent-driven development when your platform supports subagents, such as Claude Code, Codex CLI, Copilot CLI, or Gemini CLI. The executing-plans skill is the fallback for sessions without subagent access.

What happens after all plan tasks are completed?

The skill hands off to the finishing-a-development-branch sub-skill, which verifies tests, presents completion options, and executes your choice to wrap up the work.