Skip to content
Agentmart
Submit a tool

executing-plans

Use when implementing an approved written plan with dependent tasks in the current session.

Skill by tsergeytovarov

IndexedMIT★ 15
Write a review

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/tsergeytovarov-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.

We use your email only for this newsletter. Privacy

About

Use when implementing an approved written plan with dependent tasks in the current session. Do NOT use when the plan is missing, unapproved, or naturally parallel.

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this skill can do and what it asks for, from its SKILL.md and code. Checked Oct 25, 2026.

Tools
No tools found
Secrets
None asked for
Install scripts
None found

Network hosts it talks to 1

  • codeload.github.com · found in install command

Files it touches

  • ~/.claude/skills/executing-plans

What's inside

Skill name
executing-plans
Description
Use when implementing an approved written plan with dependent tasks in the current session. Do NOT use when the plan is missing, unapproved, or naturally parallel.
License
MIT
Instructions
32 lines in SKILL.md · view on GitHub

Files (2)

  • CHANGELOG.md
  • SKILL.md

SKILL.md (first lines)

# Executing Plans

Execute the plan in the current agent by default.

## Process

1. Read the plan and applicable project instructions.
2. Confirm the workspace and existing user changes are safe.
3. Flag only gaps that block or materially change the outcome.
4. Track tasks by useful deliverable, not every command.
5. For each task, implement the scoped outcome and run its risk-appropriate
   verification.
6. Update the plan or canonical backlog when reality changes.
7. Review the complete diff once at the end.

Read `../using-superpowers/references/risk-policy.md`.

Do not switch to subagent-driven development merely because subagents exist.
Delegate only when the user requests it or tasks are independent enough to
benefit from parallel work.

## Stop and Ask

Stop when authority is missing, a destructive action is newly required, a
critical requirement is ambiguous, or repeated evidence invalidates the plan.
Ordinary implementation details are resolved from the codebase.

When implementation is verified, use
`superpowers:finishing-a-development-branch` only if an integration decision is
actually needed.

From tsergeytovarov/ai-settings, MIT.

More from tsergeytovarov/ai-settings

Signals

Stars
15
Forks
4
Open issues
2
Last commit (this folder)
Jul 31, 2026 (2 months ago)
Last release
Oct 12, 2026 (16 days ago)

From GitHub (fetched Oct 24, 2026).

Details

License
MIT
First seen
Oct 24, 2026
Last checked
Oct 24, 2026

More from tsergeytovarov

Cite this page

executing-plans skill. Agent Mart. https://agentmart.dev/skills/tsergeytovarov-executing-plans (last updated 2026-10-24)