A workflow for carrying out an implementation plan one task at a time with separate workers and review stages.

Executing plan files, assigning implementation and review work to isolated workers, fixing issues, finalizing changes, and producing a run summary.

It keeps larger coding changes organized and adds checks before selected work is committed to Git, the version-control system.

plan-exec — Skill by r13v

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/r13v/pi-feature-dev/plan-exec

Any agent

npx skills add r13v/pi-feature-dev --skill plan-exec

Clone the repo

git clone --depth 1 https://github.com/r13v/pi-feature-dev

Made for: Claude Code, Codex.

Per session 29 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 2,428 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.

Model	Per session	Once invoked
Fable 5	$0.00029	$0.02428
Opus 5	$0.00015	$0.01214
Sonnet 5	$0.00006	$0.00486
Haiku 4.5	$0.00003	$0.00243

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

Security

Grade A, and why

plan-exec 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 2d ago.

The scan reads SKILL.md. This mod also ships 5 executable files (scripts/append-progress.sh, scripts/create-branch.sh, scripts/detect-branch.sh, …), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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/plan-exec/SKILL.md · 323 lines

How it starts

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

Plan Exec

Execute a plan file one task section at a time. The main session is the orchestrator. Implementation, fixing, finalization, and summary work happens in fresh-context isolated workers.

This skill is agent-agnostic, but not lowest-common-denominator. It requires a host agent that can launch isolated workers with repository access.

Required Capabilities

Before starting, verify that the current host agent supports all required capabilities:

Read and edit files in the repository.
Run shell commands in the repository.
Launch fresh-context isolated workers.
Give implementation and fixer workers write authority.
Give review and summary workers read-only authority.
Commit selected files with Git.

If any required capability is missing, stop and explain which capability is not available. Do not perform implementation work in the main orchestrating session.

Compatibility Boundaries

Git only. Stop if the current directory is not inside a Git repository.
In-place execution only. Do not create Git worktrees.
No prompt overrides. Always use the bundled prompt and reviewer files shipped inside this skill.
No custom rules loading. Follow the host agent, user, and repository instructions that are already in effect.
No external review tools. All reviews are performed by isolated workers in the current host agent.
Do not push, open pull requests, or move the plan file unless the plan itself explicitly requires it.

Arguments

Optional plan path. If omitted, choose from docs/plans/.

Bundled Files

Set PLAN_EXEC_ROOT to the absolute path of the directory containing this SKILL.md. Read bundled files directly from:

PLAN_EXEC_ROOT/references/prompts/task.md
PLAN_EXEC_ROOT/references/prompts/review.md
PLAN_EXEC_ROOT/references/prompts/fixer.md
PLAN_EXEC_ROOT/references/prompts/finalizer.md
PLAN_EXEC_ROOT/references/prompts/stats.md
PLAN_EXEC_ROOT/references/agents/*.txt
PLAN_EXEC_ROOT/scripts/*.sh

Read the full file on GitHub · 323 lines

Files

What ships with it

18 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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.

2d ago First seen · 323 lines · 29 tokens per session scan A ea47fc8aa14e

Subscribe to this mod's changes

plan-exec is a skill published in the GitHub repository r13v/pi-feature-dev (2 stars, last pushed 14d ago), licensed MIT. It adds 29 tokens to every session and 2,428 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-31.

Code review Planning Productivity

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

obra/superpowers · 37 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

agent-host-chat-contributions

Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.

microsoft/vscode · 56 tokens

auto-perf-optimize

Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.

microsoft/vscode · 62 tokens