executing-plans

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

Updated May 16, 2026
One-click install
npx skills add https://github.com/michalo1334/ScenarioImpactDSL --skill executing-plans-michalo1334
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: executing-plans
Source: https://github.com/michalo1334/ScenarioImpactDSL/tree/main/.opencode/skills/executing-plans
Command: npx skills add https://github.com/michalo1334/ScenarioImpactDSL --skill executing-plans-michalo1334

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Written implementation plans often go stale or get executed inconsistently when an AI session improvises instead of following the plan. This Skill enforces disciplined execution of a pre-written plan in a separate session, with critical review up front and verification after every task. ## Core Features & Use Cases - Critical Plan Review: Loads the plan file, identifies questions or concerns, and raises them with the human partner before writing any code. - 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 Guardrails: Halts execution on blockers, unclear instructions, or repeated verification failures instead of guessing. - Use Case: You have a detailed implementation plan produced in a planning session. Hand it to a fresh session with this Skill so every task is executed in order, verified, and finished through the development-branch completion workflow. ## Quick Start Execute the implementation plan in docs/plans/feature-x.md task by task, verifying each step 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 assistant?▼

Provide the plan file path and let the skill load it, review it critically, and raise concerns before starting. It then executes each task in order, runs the plan's verifications, and marks tasks complete as it goes.

What happens when plan execution hits a blocker?▼

Execution stops immediately on blockers such as missing dependencies, failing tests, or unclear instructions. The skill asks for clarification rather than guessing, and returns to plan review if the approach needs rethinking.

Should I use executing-plans or subagent-driven-development?▼

Use subagent-driven-development when your platform supports subagents, since the skill notes quality is significantly higher with subagent support. Use executing-plans as the fallback for single-session execution without subagents.

Can I start implementation directly on the main branch?▼

No. The skill explicitly forbids starting implementation on main or master without explicit user consent, and integrates with a git worktree workflow to ensure an isolated workspace.

What happens after all plan tasks are complete?▼

After all tasks are verified, the skill hands off to the finishing-a-development-branch skill, which verifies tests, presents completion options, and executes the chosen option.