executing-plans
Use when you have a written implementation plan to execute in a separate session with review checkpoints
Skill by muratmirgun
Install
Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.
npx agentmarket install skill/muratmirgun-executing-plans
Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.
Get the weekly diff
The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.
About
Reviews
Write a reviewNo reviews yet. Installed it? Reviews come from verified installers only. How reviews work
Permissions: not checked yet.
What's inside
- Skill name
executing-plans- Description
- Use when you have a written implementation plan to execute in a separate session with review checkpoints
- License
- Apache-2.0
- Instructions
- 63 lines in SKILL.md · view on GitHub
Files (1)
- SKILL.md
SKILL.md (first lines)
# Executing Plans ## Overview Load plan, review critically, execute all tasks, report when complete. **Announce at start:** "I'm using the executing-plans skill to implement this plan." **Note:** OpenCode can dispatch subagents through its native `task` tool. When the plan has independent tasks and the user wants delegated execution, use `subagent-driven-development`; otherwise continue with this inline workflow. ## The Process ### Step 1: Load and Review Plan 1. Ensure an isolated workspace: use `using-git-worktrees` to create one or verify the existing one 2. Read plan file 3. Review critically - identify any questions or concerns about the plan 4. If concerns: Raise them with your human partner before starting 5. If no concerns: Create todos for the plan items and proceed ### Step 2: Execute Tasks For each task: 1. Mark as in_progress 2. Follow each step exactly (plan has bite-sized steps) 3. Run verifications as specified 4. Mark as completed ### Step 3: Complete Development After all tasks complete and verified: - Announce: "I'm using the finishing-a-development-branch skill to complete this work." - **REQUIRED SUB-SKILL:** Use `finishing-a-development-branch` - Follow that skill to verify tests, present options, execute choice ## When to Stop and Ask for Help **STOP executing immediately when:** - Hit a blocker (missing dependency, test fails, instruction unclear) - Plan has critical gaps preventing starting - You don't understand an instruction - Verification fails repeatedly **Ask for clarification rather than guessing.** ## When to Revisit Earlier Steps **Return to Review (Step 1) when:** - Partner updates the plan based on your feedback - Fundamental approach needs rethinking **Don't force through blockers** - stop and ask. ## Remember - Review plan critically first - Follow plan steps exactly - Don't skip verifications - Reference skills when plan says to - Stop when blocked, don't guess - Never start implementation on main/master branch without explicit user consent
From muratmirgun/witch, Apache-2.0.
More from muratmirgun/witch
- 0.563score
witch-delegation
muratmirgun
Use after design and plan approval to execute a plan through Witch's fixed work and review lanes
SkillBFreshness: B★ 3Claude Code +9 - 0.553score
using-witch
muratmirgun
Use at the start of every Witch session to select the governing process skill and preserve Witch routing boundaries
SkillBFreshness: B★ 3Claude Code +9 - 0.543score
subagent-driven-development
muratmirgun
Use when executing implementation plans with independent tasks in the current session
SkillBFreshness: B★ 3Claude Code +9 - 0.538score
systematic-debugging
muratmirgun
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
SkillBFreshness: B★ 3Claude Code +9 - 0.538score
requesting-code-review
muratmirgun
Use when completing tasks, implementing major features, or before merging to verify work meets requirements
SkillBFreshness: B★ 3Claude Code +9 - 0.538score
writing-plans
muratmirgun
Use when you have a spec or requirements for a multi-step task, before touching code
SkillBFreshness: B★ 3Claude Code +9 - 0.536score
brainstorming
muratmirgun
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior.
SkillBFreshness: B★ 3Claude Code +9
Signals
- Stars
- 3
- Forks
- 0
- Open issues
- 0
- Last commit (this folder)
- Aug 2, 2026 (2 months ago)
- Last release
- Aug 15, 2026 (2 months ago)
From GitHub (fetched Oct 24, 2026).
Details
- License
- Apache-2.0
- Repository
- github.com/muratmirgun/witch
- First seen
- Oct 24, 2026
- Last checked
- Oct 24, 2026
- Source
- GitHubgithub-graphql
More from muratmirgun
- 0.563score
witch-delegation
muratmirgun
Use after design and plan approval to execute a plan through Witch's fixed work and review lanes
SkillBFreshness: B★ 3Claude Code +9 - 0.553score
using-witch
muratmirgun
Use at the start of every Witch session to select the governing process skill and preserve Witch routing boundaries
SkillBFreshness: B★ 3Claude Code +9 - 0.543score
subagent-driven-development
muratmirgun
Use when executing implementation plans with independent tasks in the current session
SkillBFreshness: B★ 3Claude Code +9 - 0.538score
systematic-debugging
muratmirgun
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
SkillBFreshness: B★ 3Claude Code +9 - 0.538score
requesting-code-review
muratmirgun
Use when completing tasks, implementing major features, or before merging to verify work meets requirements
SkillBFreshness: B★ 3Claude Code +9 - 0.538score
writing-plans
muratmirgun
Use when you have a spec or requirements for a multi-step task, before touching code
SkillBFreshness: B★ 3Claude Code +9
Cite this page
executing-plans skill. Agent Mart. https://agentmart.dev/skills/muratmirgun-executing-plans (last updated 2026-10-24)