What is executing-plans?

A workflow for carrying out a written software implementation plan in batches, with review points between batches.

Use it to load and check a plan, complete several tasks at a time, run the requested checks, and report progress for review.

It keeps planned work organized and gives a reviewer chances to catch problems before all tasks are finished.

executing-plans — Skill for Claude Code and Codex by coctostan

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.

Any agent

npx skills add coctostan/pi-superpowers-plus --skill executing-plans

Clone the repo

git clone --depth 1 https://github.com/coctostan/pi-superpowers-plus

Made for: Claude Code, Codex.

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/coctostan/pi-superpowers-plus/executing-plans/github.svg)](https://agentmods.dev/skills/coctostan/pi-superpowers-plus/executing-plans)

Your own site

<a href="https://agentmods.dev/skills/coctostan/pi-superpowers-plus/executing-plans"><img src="https://agentmods.dev/badge/skills/coctostan/pi-superpowers-plus/executing-plans/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/coctostan/pi-superpowers-plus/executing-plans"><img src="https://agentmods.dev/badge/skills/coctostan/pi-superpowers-plus/executing-plans.svg" alt="Reviewed on agentmods" width="80" 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 786 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

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.1	$0.00022	$0.00786
Opus 5.5	$0.00009	$0.00314
Sonnet 5.5	$0.00004	$0.00157
Haiku 4.5	$0.00002	$0.00079

Measured 1mo ago against content hash b24021318269, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, 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 1mo 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 · 103 lines

How it starts

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

Related skills: Need an isolated workspace? /skill:using-git-worktrees. Verify each task with /skill:verification-before-completion. Done? /skill:finishing-a-development-branch.

Executing Plans

Overview

Load plan, review critically, execute tasks in batches, report for review between batches.

Core principle: Batch execution with checkpoints for architect review.

Announce at start: "I'm using the executing-plans skill to implement this plan."

If a tool result contains a ⚠️ workflow warning, stop immediately and address it before continuing.

Prerequisites

Active branch (not main) or user-confirmed intent to work on main
Approved plan or clear task scope

The Process

Step 1: Load and Review Plan

Read plan file
Review critically - identify any questions or concerns about the plan
If concerns: Raise them with your human partner before starting
If no concerns: Initialize the plan_tracker tool and proceed

Step 2: Execute Batch

Default: First 3 tasks

For each task:

Update task status via plan_tracker tool
Follow each step exactly (plan has bite-sized steps)
Run verifications as specified
Update task status via plan_tracker tool

Step 3: Report

When batch complete:

Show what was implemented
Show verification output
Say: "Ready for feedback."

Step 4: Continue

Based on feedback:

Apply changes if needed
Execute next batch
Repeat until complete

Step 5: 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 /skill: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 mid-batch (missing dependency, test fails, instruction unclear)
Plan has critical gaps preventing starting
You don't understand an instruction
Verification fails repeatedly

Read the full file on GitHub · 103 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.

1mo ago First seen · 103 lines · 22 tokens per session scan A b24021318269

Subscribe to this mod's changes

executing-plans is a skill published in the GitHub repository coctostan/pi-superpowers-plus (106 stars, last pushed 8mo ago), licensed MIT. It adds 22 tokens to every session and 786 once invoked, about $0.0001 per session on Opus 5.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.

Planning ai-tools pi pi-extension

surf

Control Chrome browser via CLI for testing, automation, and debugging. Use when the user needs browser automation, screenshots, form filling, page inspection, network/CPU emulation, DevTools streaming, or AI queries via ChatGPT/Gemini/Perplexity/Grok/AI Studio.

w-winter/dot314 · 60 tokens

portfolio-manager

Plan this week's budget split between projects from the portfolio snapshot and priorities.md, then report it to the operator.

edgehero/pi-dispatch · 25 tokens

prose-review

Review prose written for others (e.g., user-facing documentation, prompts for other LLMs, reports, plans, inline comments, docstrings) for local jargon leakage, orphaned references, missing grounding, and audience or genre mismatch. Always run on prose you produce or materially edit, except for routine conversational…

w-winter/dot314 · 84 tokens

text-search

Search indexed text corpora with qmd. For indexed content, prefer qmd over grep.

w-winter/dot314 · 22 tokens

repoprompt-tool-guidance-refresh

Refresh RepoPrompt tool guidance when the CLI/MCP surface changes. Tracks RepoPrompt CE (rpce-cli, the maintained target) across versions, and can diff the frozen Classic CLI (rp-cli) against CE. Uses /.pi/agent/skills/repoprompt-tool-guidance-refresh/scripts/track-rp-version.sh to capture/diff --help and -l (tool…

w-winter/dot314 · 115 tokens

portfolio-fixture

The zero-judgement test of the portfolio flow. Copies a fixed plan to the outbox and reports it.

edgehero/pi-dispatch · 27 tokens