executing-plans

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

Updated Jan 31, 2026
One-click install
npx skills add https://github.com/adrianasiam19/ATLAS --skill executing-plans-adrianasiam19
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: executing-plans
Source: https://github.com/adrianasiam19/ATLAS/tree/main/.agent/skills/executing-plans
Command: npx skills add https://github.com/adrianasiam19/ATLAS --skill executing-plans-adrianasiam19

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 issues 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 verifications specified in the plan. - Stop-and-Ask Discipline: 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 in order, then hands off to a branch-finishing workflow when complete. ## Quick Start Use the executing-plans skill to implement the plan in docs/plans/my-feature-plan.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 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 TodoWrite tracking and runs the verifications specified in the plan.

What should an implementation plan contain before execution?▼

The plan should contain bite-sized steps with explicit verification commands for each task. This skill works best with plans created by a dedicated planning skill such as superpowers:writing-plans, which structures tasks for reliable execution.

What happens when a plan step fails or is unclear?▼

Execution stops immediately when a blocker, failing verification, or unclear instruction is encountered. The skill asks for clarification rather than guessing, and returns to plan review if the fundamental approach needs rethinking.

Can I run plan execution on the main branch?▼

No. The skill never starts implementation on main or master without explicit user consent. It recommends setting up an isolated workspace first, using a git worktree workflow before executing tasks.

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

Use subagent-driven development when your platform supports subagents, such as Claude Code or Codex. The skill notes that output quality is significantly higher with subagent support; executing-plans is the fallback for single-session execution.