Deep Plan
piercelamb/deep-plan
Creates detailed, sectionized, TDD-oriented implementation plans through research, stakeholder interviews, and multi-LLM review.
Methodically execute implementation plans with a TDD approach, incremental commits, and continuous validation
Install Executing Plans
$ npx skills add dev-toolings/superpowers-symfony --skill executing-plans -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install dev-toolings/superpowers-symfony executing-plans --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/dev-toolings/superpowers-symfony.git skills-src && mkdir -p .claude/skills && cp -r skills-src/content/skills/executing-plans .claude/skills/executing-plans && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "executing-plans" agent skill from https://github.com/dev-toolings/superpowers-symfony/tree/main/content/skills/executing-plans into .claude/skills/executing-plans/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "executing-plans", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/dev-toolings/superpowers-symfony/tree/main/content/skills/executing-plansType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add dev-toolings/superpowers-symfony --skill executing-plans -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install dev-toolings/superpowers-symfony executing-plans --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/dev-toolings/superpowers-symfony.git skills-src && mkdir -p .agents/skills && cp -r skills-src/content/skills/executing-plans .agents/skills/executing-plans && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "executing-plans" agent skill from https://github.com/dev-toolings/superpowers-symfony/tree/main/content/skills/executing-plans into .agents/skills/executing-plans/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "executing-plans", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add dev-toolings/superpowers-symfony --skill executing-plans -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install dev-toolings/superpowers-symfony executing-plans --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/dev-toolings/superpowers-symfony.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/content/skills/executing-plans .cursor/skills/executing-plans && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "executing-plans" agent skill from https://github.com/dev-toolings/superpowers-symfony/tree/main/content/skills/executing-plans into .cursor/skills/executing-plans/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "executing-plans", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/dev-toolings/superpowers-symfony.git --path content/skills/executing-plans--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add dev-toolings/superpowers-symfony --skill executing-plans -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install dev-toolings/superpowers-symfony executing-plans --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/dev-toolings/superpowers-symfony.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/content/skills/executing-plans .gemini/skills/executing-plans && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "executing-plans" agent skill from https://github.com/dev-toolings/superpowers-symfony/tree/main/content/skills/executing-plans into .gemini/skills/executing-plans/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "executing-plans", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install dev-toolings/superpowers-symfony executing-plansInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add dev-toolings/superpowers-symfony --skill executing-plans -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/dev-toolings/superpowers-symfony.git skills-src && mkdir -p .github/skills && cp -r skills-src/content/skills/executing-plans .github/skills/executing-plans && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "executing-plans" agent skill from https://github.com/dev-toolings/superpowers-symfony/tree/main/content/skills/executing-plans into .github/skills/executing-plans/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "executing-plans", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add dev-toolings/superpowers-symfony --skill executing-plans -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install dev-toolings/superpowers-symfony executing-plans --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/dev-toolings/superpowers-symfony.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/content/skills/executing-plans .opencode/skills/executing-plans && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "executing-plans" agent skill from https://github.com/dev-toolings/superpowers-symfony/tree/main/content/skills/executing-plans into .opencode/skills/executing-plans/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "executing-plans", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
executing-plans- GitHub stars
- 222
- Token cost
- ~405 tokens
- SKILL.md length
- 204 words
- Files
- 2
- Skills in repo
- 44
- Repo updated
- First seen
- Licence
- MIT
At a glance
Methodically execute implementation plans with a TDD approach, incremental commits, and continuous validation
- Works in 5 steps: Read the whole plan, confirm the… → For each step, write the test, watch it… → Commit after each completed step, with a… → …
- Tasks that involve Planning
- SKILL.md covers Use when, Default workflow, Guardrails and Progressive disclosure, plus 2 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Executing Plans is an agent skill from dev-toolings/superpowers-symfony. Methodically execute implementation plans with a TDD approach, incremental commits, and continuous validation
Its SKILL.md is about 410 tokens, which your agent loads only when the skill is triggered. The skill folder holds 1 other file (for example `reference.md`).
It sits in Agent Workflows, covering Planning and Test-driven development. The repository describes itself as: Claude Code plugin for Symfony 7.4 LTS & 8.x — 44 skills, 7 AI subagents & 13 commands for API Platform v4, Doctrine ORM 3, TDD (Pest/PHPUnit), Messenger, security & DDD. The licence is MIT.
When your agent uses it
- Tasks that involve Planning
- Tasks that involve Test-driven development
Example prompts
- “/executing-plans”
Requirements
- Pre-approved tools (allowed-tools): Read, Glob, Grep, Write, Edit, Bash
Workflow steps
5 steps, taken from the first numbered list in SKILL.md.
- Read the whole plan, confirm the baseline tests pass, and work on a branch.
- For each step, write the test, watch it fail, implement, watch it pass, then refactor.
- Commit after each completed step, with a message that names it.
- Run the quality gates (style, static analysis, full suite) at the end of each phase.
- Track each step's status in the plan, and stop to report when reality contradicts it.
What it can do on your machine
Read from SKILL.md and the folder at commit 459bcd0. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves these tools, so the agent can use them without asking each time:
ReadGlobGrepWriteEditBash
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Executing Plans loads about 405 tokens when it runs. Until then it costs about 31 tokens; SKILL.md has 204 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check: notes
The automated check noted patterns worth knowing about, such as sudo or a known installer.
- NotePre-approves every shell command (allowed-tools: Bash)SKILL.md
allowed-tools: Read, Glob, Grep, Write, Edit, Bash
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from dev-toolings/superpowers-symfony at commit 459bcd0, republished under its MIT licence (© dev-toolings). 204 words, ~405 tokens.
Download SKILL.mdSave it as
.claude/skills/executing-plans/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- executing-plans
- description
- Methodically execute implementation plans with a TDD approach, incremental commits, and continuous validation
- allowed-tools
- Read, Glob, Grep, Write, Edit, Bash
- capabilities
- read, search, edit, shell
- tags
- workflow
Executing Plans (Symfony)
Use when
- An approved implementation plan exists and must be carried out.
- The work spans several steps that must each land green.
- Resuming a plan after an interruption or a blocker.
Default workflow
- Read the whole plan, confirm the baseline tests pass, and work on a branch.
- For each step, write the test, watch it fail, implement, watch it pass, then refactor.
- Commit after each completed step, with a message that names it.
- Run the quality gates (style, static analysis, full suite) at the end of each phase.
- Track each step's status in the plan, and stop to report when reality contradicts it.
Guardrails
- Never skip watching the test fail: a test that never failed proves nothing.
- One step per commit; do not batch steps.
- Do not change the plan silently: report the deviation and the reason.
- On a blocker (failing migration, autowiring error), fix the cause, not the test.
Progressive disclosure
- Use this file for execution posture and risk controls.
- Open references when deep implementation details are needed.
Output contract
- One commit per step, tests included.
- The plan with the status of every step.
- Final validation results and any deviation from the plan.
References
reference.md
© dev-toolings, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 1 other file in content/skills/executing-plans of dev-toolings/superpowers-symfony.
- SKILL.md
- reference.md
Open the folder on GitHubat commit 459bcd0
Compare with similar skills
Executing Plans next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Executing Plans this skilldev-toolings/superpowers-symfony | 222 | — | ~405 | Automated safety check: Notes | MIT | |
| Deep Planpiercelamb/deep-plan | 101 | — | ~4.8k | Automated safety check: Pass | MIT | |
| Plan Py4vaspvasp-dev/py4vasp | 100 | — | ~2.3k | Automated safety check: Pass | Apache-2.0 | |
| Test-First Implementation Plangittower/git-flow-next | 458 | — | ~1.3k | Automated safety check: Notes | Custom licence | |
| Writing PlansProgrammerAnthony/Expert-Coding-Harness | 235 | — | ~876 | Automated safety check: Pass | MIT | |
| Solo BuildLeoYeAI/openclaw-master-skills | 2.2k | — | ~4.6k | Automated safety check: Notes | MIT |
Similar skills
Plan Py4vasp
vasp-dev/py4vasp
Plan a py4vasp change as an ordered list of test-first chunks — that chunk list is the plan.
Test-First Implementation Plan
gittower/git-flow-next
Builds a two-phase implementation plan from a spec issue, analysis or concept, writing a detailed test plan first and the implementation outline second.
Writing Plans
ProgrammerAnthony/Expert-Coding-Harness
A skill your agent uses when 已有经批准的设计/规格说明、多步骤实施任务，在动代码之前需要可执行任务清单时。触发场景：写实施计划、拆解开发任务、implementation plan、执行计划文档、任务拆分、按 TDD 步骤写计划。
Solo Build
LeoYeAI/openclaw-master-skills
Execute implementation plan tasks with TDD workflow, auto-commit, and phase gates.
Executing Plans Inline
obra/superpowers
Has the agent carry out an implementation plan itself, task by task in the current session, keeping a ledger, proving each step with a test and ending with one whole-branch review.
More from dev-toolings/superpowers-symfony
All 44 skills in this repoSymfony Scheduler
dev-toolings/superpowers-symfony
Schedule recurring tasks with the Symfony Scheduler component (native since 7.x); define schedules, triggers, and integrate with Messenger
API Platform Dto Resources
dev-toolings/superpowers-symfony
Map entities to API DTOs in API Platform (v5, 4.4, 4.3) with the Symfony Object Mapper ([Map], stateOptions) for decoupled input/output contracts
API Platform Filters
dev-toolings/superpowers-symfony
Implement API Platform filters - Parameters API (QueryParameter, v5/4.4/4.3) and the [ApiFilter] attribute deprecated since 4.4 - for search, date, range, boolean, and custom filtering
API Platform Resources
dev-toolings/superpowers-symfony
Configure API Platform resources (v5, 4.4, 4.3) with explicit operations, pagination, and typed OpenAPI for clean, versioned REST/GraphQL APIs
API Platform Security
dev-toolings/superpowers-symfony
Secure API Platform resources with security expressions, voters, securityPostValidation, and operation-level access control
API Platform Serialization
dev-toolings/superpowers-symfony
Control API Platform serialization with groups, [Context], IRI links (readableLink/writableLink), and custom context builders
Related
Categories
Questions about Executing Plans
What does Executing Plans do?
Methodically execute implementation plans with a TDD approach, incremental commits, and continuous validation. Executing Plans is an agent skill from dev-toolings/superpowers-symfony.
When should I use Executing Plans?
Executing Plans fits situations like: tasks that involve Planning; tasks that involve Test-driven development.
How do I install Executing Plans in Claude Code?
Run `npx skills add dev-toolings/superpowers-symfony --skill executing-plans -a claude-code`. Or copy the skill folder (content/skills/executing-plans in dev-toolings/superpowers-symfony) into .claude/skills/executing-plans in your project. Claude Code loads it when a task matches its description.
How do I install Executing Plans in Codex?
Run `npx skills add dev-toolings/superpowers-symfony --skill executing-plans -a codex`. Or copy the skill folder (content/skills/executing-plans in dev-toolings/superpowers-symfony) into .agents/skills/executing-plans in your project. Codex loads it when a task matches its description.
Can I use Executing Plans in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add dev-toolings/superpowers-symfony --skill executing-plans -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/executing-plans, .gemini/skills/executing-plans, .github/skills/executing-plans and .opencode/skills/executing-plans in your project.
What does Executing Plans need to run?
SKILL.md names no scripts, command-line tools or credentials: Executing Plans is instructions for the agent only. Its frontmatter pre-approves these tools: Read, Glob, Grep, Write, Edit, Bash.
Does Executing Plans access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Executing Plans safe to install?
Our automated static check of SKILL.md found notes only (pre-approves every shell command (allowed-tools: bash)), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.
What licence does Executing Plans use?
Executing Plans is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Executing Plans use?
About 405 tokens (SKILL.md is roughly 1.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Executing Plans?
Skills that share tags, products or a category with Executing Plans: Deep Plan (piercelamb/deep-plan, 101 stars), Plan Py4vasp (vasp-dev/py4vasp, 100 stars), Test-First Implementation Plan (gittower/git-flow-next, 458 stars) and Writing Plans (ProgrammerAnthony/Expert-Coding-Harness, 235 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Executing Plans?
dev-toolings (a GitHub organization) maintains it in dev-toolings/superpowers-symfony, which has 222 GitHub stars. The repository holds 44 skills in this directory. The repository was last updated on October 5, 2026.
Source: dev-toolings/superpowers-symfony on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.