executing-plans

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

Updated Jun 5, 2026
One-click install
npx skills add https://github.com/zMynxx/bifrost-with-opencode --skill executing-plans-zmynxx
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: executing-plans
Source: https://github.com/zMynxx/bifrost-with-opencode/tree/main/.agents/skills/executing-plans
Command: npx skills add https://github.com/zMynxx/bifrost-with-opencode --skill executing-plans-zmynxx

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? AI agents often improvise when given a plan, skipping steps, ignoring verifications, or guessing through blockers. This Skill enforces disciplined execution of a written implementation plan in a separate session, with critical review upfront and explicit checkpoints throughout. ## 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: Marks each task in progress, follows bite-sized steps exactly, runs specified verifications, and marks tasks completed. - Stop-and-Ask Discipline: Halts immediately on blockers, unclear instructions, or repeated verification failures instead of guessing. - Workflow Integration: Hands off to finishing-a-development-branch after all tasks pass, and recommends subagent-driven-development when subagents are available. - Use Case: You have a written implementation plan from a planning session. Start a fresh session, hand the plan to the agent, and it executes every task with verifications, stopping to ask whenever something is ambiguous. ## Quick Start Ask the agent to execute the implementation plan in docs/plans/feature-x.md using the executing-plans skill.

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 agent?▼

Provide the plan file path and invoke the executing-plans skill. The agent reviews the plan critically, raises concerns before starting, then executes each task in order, running the verifications specified in the plan and marking tasks complete as it goes.

What should an AI agent do when a plan step fails verification?▼

The agent should stop executing immediately rather than guessing or forcing through the blocker. It reports the failure—such as a failing test, missing dependency, or unclear instruction—and asks the human partner for clarification before continuing.

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. Subagent-based execution produces higher quality results; executing-plans is the fallback for single-agent sessions.

Can an agent start implementing a plan on the main branch?▼

No. The skill explicitly forbids starting implementation on main or master without explicit user consent. It integrates with git worktree workflows to ensure development happens in an isolated workspace.

What happens after all plan tasks are completed?▼

After every task is executed and verified, the agent invokes the finishing-a-development-branch skill. That skill verifies the test suite, presents merge or cleanup options, and completes the development workflow.