executing-plans

Executes written implementation plans task-by-task with review checkpoints and per-task commits.

Updated Aug 14, 2026
One-click install
npx skills add https://github.com/bill80362/laravel-thread-admin --skill executing-plans-bill80362
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: executing-plans
Source: https://github.com/bill80362/laravel-thread-admin/tree/main/.github/superpowers/executing-plans
Command: npx skills add https://github.com/bill80362/laravel-thread-admin --skill executing-plans-bill80362

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Written implementation plans often fail during execution because steps are skipped, verification is vague, or blockers are silently worked around. This Skill enforces a disciplined workflow: critically review the plan first, execute each task with explicit verification, commit per task, and stop to ask when blocked instead of guessing. ## Core Features & Use Cases - Critical Plan Review: Checks for missing dependencies between steps, vague verification criteria, and hidden environment assumptions before any code is written. - Structured Task Execution: Tracks progress with a todo list, runs the required tests or checks per task, and creates one commit per task referencing its task number. - Blocker Escalation: Defines explicit stop conditions (missing dependencies, repeated test failures, unclear instructions) so the AI asks the human partner rather than guessing. - Use Case: You have a 5-task plan in docs/plan.md for adding user validation to an API. The Skill reviews the plan, flags an unclear verification step, then implements each task, runs the test suite, commits with messages like "feat: add user input validation (task 2/5)", and produces a final execution report. ## Quick Start Ask the AI to use the executing-plans skill to implement the plan in docs/plan.md, reviewing it first and committing after each completed task.

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, critically review it for missing dependencies and vague verification criteria, then execute each task with a todo list, run the specified tests, and commit per task. Stop and ask the human partner when blocked rather than guessing.

What should I check when reviewing an implementation plan before coding?

Check for missing dependencies between steps, verification conditions that are too vague (e.g., 'confirm it works' instead of a concrete test command), and hidden environment assumptions like runtime versions, database connections, or API keys.

When should plan execution stop and ask the human instead of continuing?

Stop when you hit a blocker such as a missing dependency, when the same test fails more than twice, when an instruction is unclear, or when the plan has a serious flaw. Never guess intent or push through a blocker silently.

Should each task in a plan be committed separately to git?

Yes. Commit after each completed task with a message referencing the task number, such as 'feat: add user input validation (task 2/5)'. This keeps the history traceable to the plan and simplifies review and rollback.

Can I start implementing a plan directly on the main branch?

No. Work in an isolated git worktree or feature branch, and never begin implementation on main or master without explicit user consent. After all tasks pass verification, use a branch-finishing workflow to handle merge or pull request.