executing-plans

executing-plans is a skill for Claude Code, Codex from DollarDill/beads-superpowers. It costs 22 tokens per session (1,688 once invoked), scanned A, original, MIT.

A procedure for carrying out a written software implementation plan in a separate work session. It breaks the plan into tracked tasks and uses review checkpoints while the work is completed.

In plain words
What is it for?
Use it to execute an approved feature plan, create related tasks, manage dependencies, and report progress as the implementation proceeds.
Why use it?
It helps turn a broad plan into organized, reviewable coding work instead of leaving steps unclear or untracked.

Skill for Claude CodeCodex

Part of the beads-superpowers plugin — 22 skills, 1 agent, 1 hook shipped together

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add skills/dollardill/beads-superpowers/executing-plans
Any agent
npx skills add DollarDill/beads-superpowers --skill executing-plans
Clone the repo
git clone --depth 1 https://github.com/DollarDill/beads-superpowers

Made for: Claude Code, Codex.

Or install beads-superpowers, the plugin that ships this one along with the rest of its 22 skills, 1 agent, 1 hook.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for executing-plans

README.md
[![agentmods](https://agentmods.dev/badge/skills/dollardill/beads-superpowers/executing-plans.svg)](https://agentmods.dev/skills/dollardill/beads-superpowers/executing-plans)
Your own site
<a href="https://agentmods.dev/skills/dollardill/beads-superpowers/executing-plans"><img src="https://agentmods.dev/badge/skills/dollardill/beads-superpowers/executing-plans.svg" alt="Measured on agentmods" height="20"></a>
Per session 22 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,688 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00022 $0.01688
Opus 5 $0.00011 $0.00844
Sonnet 5 $0.00004 $0.00338
Haiku 4.5 $0.00002 $0.00169

Measured 5d ago against content hash df2ed3cfac80, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

executing-plans scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 5d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skills/executing-plans/SKILL.md · 116 lines

How it starts

The opening of the file, as written. The whole thing — 116 lines — stays where its author put it; the contents beside it link to each section on GitHub.

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: Tell your human partner that this system works much better with access to subagents (Claude Code, Codex, Copilot CLI, and Gemini CLI all qualify). If subagents are available, use beads-superpowers:subagent-driven-development instead of this skill.

The Process

Step 1: Load and Review Plan

  1. Ensure an isolated workspace first — use the beads-superpowers:using-git-worktrees skill.

  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 epic bead and child beads for each task, then proceed

    Create the epic, then import the child tasks as JSONL:

    # 1. Create the epic (→ note its id):
    bd create "Epic: <plan-name>" -t epic -p 2 -d "<goal>
    

Success Criteria

  • <measurable outcome from the plan's Goal>"

    2. Author the tasks as JSONL — one issue per line, id OMITTED (auto-assigned;

    a supplied colliding id would overwrite that bead and reset its omitted fields).

    Parent each to the epic; embed the bd lint-required '## Acceptance Criteria' in

    'description' (or the 'acceptance_criteria' field). Read bd import --help on

    first use; bd export <id> round-trips a real bead as a schema template.

    cat <<'EOF' | bd import - {"title":"Task 1: ","issue_type":"task","priority":2,"description":"\n\n## Acceptance Criteria\n- ","dependencies":[{"depends_on_id":"","type":"parent-child"}]} {"title":"Task 2: ","issue_type":"task","priority":2,"description":"\n\n## Acceptance Criteria\n- ","dependencies":[{"depends_on_id":"","type":"parent-child"}]} EOF

    
    Confirm the import output shows no `Skipped dependency` (a dep to a missing target is skipped, not rolled back). `bd lint` requires `## Success Criteria` in the epic's description and `## Acceptance Criteria` in each task's — embed them as above.
    

Read the full file on GitHub · 116 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 5d ago First seen · 116 lines · 22 tokens per session scan A df2ed3cfac80

Subscribe to this mod's changes

executing-plans is a skill published in the GitHub repository DollarDill/beads-superpowers (26 stars, last pushed 13d ago), licensed MIT. It adds 22 tokens to every session and 1,688 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories

beads-onboard

This skill should be used when the user asks to "onboard beads", "set up beads conventions", "configure beads for this project", "set up project labels", "improve my beads quality", "run beads onboard", "upgrade beads conventions", "re-run beads onboard", or when a project has .beads/ but no .beads/conventions/…

seanmartinsmith/sms-public-mkt · 96 tokens

compound-v

Use when superpowers:brainstorming is about to begin (pre-brainstorm recon), OR has produced a spec, OR when superpowers:writing-plans has produced a plan, OR when about to invoke superpowers:subagent-driven-development or superpowers:executing-plans. Sidekick that intercepts these four Superpowers transitions — runs…

procoders/superpowers-v · 103 tokens

backend-launcher

Use when Compound V's dispatcher needs to run one file-scoped job on a chosen backend (Claude subagent, headless Codex worker, headless Antigravity worker, headless Cursor worker, headless Devin worker, or headless opencode worker) and get back a canonical jobresult. The single jobspec → jobresult contract every…

procoders/superpowers-v · 91 tokens

pr-review

Use when the user wants to deeply review a pull/merge request or a local diff — "review this PR", "grill the MR", "stress-test this diff", "deep-dive code review", "code review before merge", or when they name a PR/MR URL, number, or feature branch. Works on GitHub (gh), GitLab (glab), or a plain local branch with no…

procoders/superpowers-v · 96 tokens

dolt-mcp-vcs

Universal Dolt version-control workflow. Step 0 auto-detects what kind of Dolt stack is present — every make and model (classic Dolt repo, live dolt sql-server on its ACTUAL bound port, bd embedded store, Doltgres, DoltLite single-file DB, DumboDB) — and emits a ready-to-use connection descriptor, then routes to work…

jeremylongshore/dolt-mcp-vcs-plugin · 252 tokens

linear-workspace

Linear issue management — routes work to specialized agents and slash commands. Use when: creating, updating, searching, bulk-editing, cleaning up, syncing Linear. TRIGGERS: "linear", "ticket", "issue", "create issue", "update issue", "search issues", "my issues", "bulk", "cleanup", "sync", "log bug", "file issue"…

Elnora-AI/elnora-linear · 126 tokens