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.
A skill your agent uses when beginning implementation from a design plan - orchestrates branch creation, detailed planning, and hands off to execution with all necessary context
Install Starting An Implementation Plan
$ npx skills add ed3dai/ed3d-plugins --skill starting-an-implementation-plan -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install ed3dai/ed3d-plugins starting-an-implementation-plan --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/ed3dai/ed3d-plugins.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/ed3d-plan-and-execute/skills/starting-an-implementation-plan .claude/skills/starting-an-implementation-plan && 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 "starting-an-implementation-plan" agent skill from https://github.com/ed3dai/ed3d-plugins/tree/main/plugins/ed3d-plan-and-execute/skills/starting-an-implementation-plan into .claude/skills/starting-an-implementation-plan/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "starting-an-implementation-plan", 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/ed3dai/ed3d-plugins/tree/main/plugins/ed3d-plan-and-execute/skills/starting-an-implementation-planType 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 ed3dai/ed3d-plugins --skill starting-an-implementation-plan -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install ed3dai/ed3d-plugins starting-an-implementation-plan --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ed3dai/ed3d-plugins.git skills-src && mkdir -p .agents/skills && cp -r skills-src/plugins/ed3d-plan-and-execute/skills/starting-an-implementation-plan .agents/skills/starting-an-implementation-plan && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "starting-an-implementation-plan" agent skill from https://github.com/ed3dai/ed3d-plugins/tree/main/plugins/ed3d-plan-and-execute/skills/starting-an-implementation-plan into .agents/skills/starting-an-implementation-plan/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "starting-an-implementation-plan", 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 ed3dai/ed3d-plugins --skill starting-an-implementation-plan -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install ed3dai/ed3d-plugins starting-an-implementation-plan --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ed3dai/ed3d-plugins.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/plugins/ed3d-plan-and-execute/skills/starting-an-implementation-plan .cursor/skills/starting-an-implementation-plan && 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 "starting-an-implementation-plan" agent skill from https://github.com/ed3dai/ed3d-plugins/tree/main/plugins/ed3d-plan-and-execute/skills/starting-an-implementation-plan into .cursor/skills/starting-an-implementation-plan/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "starting-an-implementation-plan", 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/ed3dai/ed3d-plugins.git --path plugins/ed3d-plan-and-execute/skills/starting-an-implementation-plan--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 ed3dai/ed3d-plugins --skill starting-an-implementation-plan -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install ed3dai/ed3d-plugins starting-an-implementation-plan --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ed3dai/ed3d-plugins.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/plugins/ed3d-plan-and-execute/skills/starting-an-implementation-plan .gemini/skills/starting-an-implementation-plan && 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 "starting-an-implementation-plan" agent skill from https://github.com/ed3dai/ed3d-plugins/tree/main/plugins/ed3d-plan-and-execute/skills/starting-an-implementation-plan into .gemini/skills/starting-an-implementation-plan/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "starting-an-implementation-plan", 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 ed3dai/ed3d-plugins starting-an-implementation-planInstalls 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 ed3dai/ed3d-plugins --skill starting-an-implementation-plan -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/ed3dai/ed3d-plugins.git skills-src && mkdir -p .github/skills && cp -r skills-src/plugins/ed3d-plan-and-execute/skills/starting-an-implementation-plan .github/skills/starting-an-implementation-plan && 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 "starting-an-implementation-plan" agent skill from https://github.com/ed3dai/ed3d-plugins/tree/main/plugins/ed3d-plan-and-execute/skills/starting-an-implementation-plan into .github/skills/starting-an-implementation-plan/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "starting-an-implementation-plan", 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 ed3dai/ed3d-plugins --skill starting-an-implementation-plan -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install ed3dai/ed3d-plugins starting-an-implementation-plan --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ed3dai/ed3d-plugins.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/plugins/ed3d-plan-and-execute/skills/starting-an-implementation-plan .opencode/skills/starting-an-implementation-plan && 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 "starting-an-implementation-plan" agent skill from https://github.com/ed3dai/ed3d-plugins/tree/main/plugins/ed3d-plan-and-execute/skills/starting-an-implementation-plan into .opencode/skills/starting-an-implementation-plan/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "starting-an-implementation-plan", 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
starting-an-implementation-plan- GitHub stars
- 250
- Token cost
- ~3.4k tokens
- SKILL.md length
- 1,150 words
- Files
- 1
- Skills in repo
- 34
- Repo updated
- First seen
- Licence
- None found
At a glance
A skill your agent uses when beginning implementation from a design plan - orchestrates branch creation, detailed planning, and hands off to execution with all necessary context
- Works in 3 steps: Branch Setup: Select and create branch… → Planning: Create detailed implementation… → Execution Handoff: Direct user to…
- Beginning implementation from a design plan - orchestrates branch creation
- SKILL.md covers Overview, REQUIRED: Design Plan Path, The Process and Common Mistakes, plus 1 more section
- Calls git
What it does
Starting An Implementation Plan is an agent skill from ed3dai/ed3d-plugins. Use when beginning implementation from a design plan - orchestrates branch creation, detailed planning, and hands off to execution with all necessary context
Its SKILL.md is about 3.4k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Agent Workflows, covering Planning. The repository describes itself as: Ed's repo of Claude Code plugins, centered around a research-plan-implement workflow. Only a tiny bit cursed. If you're lucky.
When your agent uses it
- Beginning implementation from a design plan - orchestrates branch creation
- Detailed planning
- Hands off to execution with all necessary context
Example prompts
- “/starting-an-implementation-plan”
Workflow steps
3 steps, taken from the first numbered list in SKILL.md.
- Branch Setup: Select and create branch for implementation
- Planning: Create detailed implementation plan
- Execution Handoff: Direct user to execute the plan
What it can do on your machine
Read from SKILL.md and the folder at commit 0c90f4b. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
git
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.
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
Starting An Implementation Plan loads about 3.4k tokens when it runs. Until then it costs about 47 tokens; SKILL.md has 1,150 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 passed
The automated check found no risky patterns in SKILL.md.
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
Without a licence we can't republish the file, so here is its outline and opening line. It has 1,150 words (~3,358 tokens).
“Orchestrate the transition from design document to executable implementation through planning and execution handoff.”
- name
- starting-an-implementation-plan
- user-invocable
- false
Files
Just SKILL.md in plugins/ed3d-plan-and-execute/skills/starting-an-implementation-plan of ed3dai/ed3d-plugins.
Open the folder on GitHubat commit 0c90f4b
Compare with similar skills
Starting An Implementation Plan 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 |
|---|---|---|---|---|---|---|
| Starting An Implementation Plan this skilled3dai/ed3d-plugins | 250 | — | ~3.4k | Automated safety check: Pass | None | |
| Executing Plans Inlineobra/superpowers | 296k | 2 repos | ~5.1k | Automated safety check: Pass | MIT | |
| Interview Meaddyosmani/agent-skills | 103k | 6 repos | ~3.8k | Automated safety check: Pass | MIT | |
| OpenSpec Guided OnboardingFission-AI/OpenSpec | 71k | 1 repos | ~4.5k | Automated safety check: Pass | MIT | |
| Writing Plansgeeksblabla/stateofdev.ma | 163 | 57 repos | ~661 | Automated safety check: Pass | None | |
| Subagent Driven DevelopmentAsvarox/allkaraoke | 261 | 38 repos | ~1.2k | Automated safety check: Pass | None |
Similar skills
Interview Me
addyosmani/agent-skills
Asks one question at a time, each with a best guess attached, until the agent is about 95 percent sure what you really want, before any plan, spec or code.
OpenSpec Guided Onboarding
Fission-AI/OpenSpec
Walks you through a complete OpenSpec workflow cycle with narration while doing real work in your codebase.
Writing Plans
geeksblabla/stateofdev.ma
A skill your agent uses when design is complete and you need detailed implementation tasks for engineers with zero codebase context - creates comprehensive implementation plans with exact file…
Subagent Driven Development
Asvarox/allkaraoke
A skill your agent uses when executing implementation plans with independent tasks in the current session
Planning With Files
jd-opensource/JoySafeter
Implements Manus-style file-based planning for complex tasks.
More from ed3dai/ed3d-plugins
All 34 skills in this repoSystematic Debugging
ed3dai/ed3d-plugins
A skill your agent uses when encountering any bug, test failure, or unexpected behavior, before proposing fixes - four-phase framework (root cause investigation, pattern analysis, hypothesis…
Testing Skills With Subagents
ed3dai/ed3d-plugins
A skill your agent uses when creating or editing skills, before deployment, to verify they work under pressure and resist rationalization - applies RED-GREEN-REFACTOR cycle to process documentation…
Brainstorming
ed3dai/ed3d-plugins
A skill your agent uses when creating or developing anything, before writing code or implementation plans - refines rough ideas into fully-formed designs through structured Socratic questioning…
Writing Good Tests
ed3dai/ed3d-plugins
A skill your agent uses when writing or reviewing tests - covers test philosophy, condition-based waiting, mocking strategy, and test isolation
Writing Skills
ed3dai/ed3d-plugins
A skill your agent uses when creating new skills, editing existing skills, or verifying skills work before deployment - applies TDD to process documentation by testing with subagents before writing…
Coding Effectively
ed3dai/ed3d-plugins
ALWAYS use this skill when writing or refactoring code. An agent skill from ed3dai/ed3d-plugins.
Related
Categories
Questions about Starting An Implementation Plan
What does Starting An Implementation Plan do?
A skill your agent uses when beginning implementation from a design plan - orchestrates branch creation, detailed planning, and hands off to execution with all necessary context. Starting An Implementation Plan is an agent skill from ed3dai/ed3d-plugins.
When should I use Starting An Implementation Plan?
Starting An Implementation Plan fits situations like: beginning implementation from a design plan - orchestrates branch creation; detailed planning; hands off to execution with all necessary context.
How do I install Starting An Implementation Plan in Claude Code?
Run `npx skills add ed3dai/ed3d-plugins --skill starting-an-implementation-plan -a claude-code`. Or copy the skill folder (plugins/ed3d-plan-and-execute/skills/starting-an-implementation-plan in ed3dai/ed3d-plugins) into .claude/skills/starting-an-implementation-plan in your project. Claude Code loads it when a task matches its description.
How do I install Starting An Implementation Plan in Codex?
Run `npx skills add ed3dai/ed3d-plugins --skill starting-an-implementation-plan -a codex`. Or copy the skill folder (plugins/ed3d-plan-and-execute/skills/starting-an-implementation-plan in ed3dai/ed3d-plugins) into .agents/skills/starting-an-implementation-plan in your project. Codex loads it when a task matches its description.
Can I use Starting An Implementation Plan 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 ed3dai/ed3d-plugins --skill starting-an-implementation-plan -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/starting-an-implementation-plan, .gemini/skills/starting-an-implementation-plan, .github/skills/starting-an-implementation-plan and .opencode/skills/starting-an-implementation-plan in your project.
What does Starting An Implementation Plan need to run?
Going by SKILL.md and its folder, Starting An Implementation Plan needs the command-line tools its instructions call (git).
Does Starting An Implementation Plan access the network?
SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Starting An Implementation Plan safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Starting An Implementation Plan use?
No licence was found for Starting An Implementation Plan or its repository. Without one, default copyright applies: ask the author before reusing or redistributing it.
How many tokens does Starting An Implementation Plan use?
About 3.4k tokens (SKILL.md is roughly 13k 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 Starting An Implementation Plan?
Skills that share tags, products or a category with Starting An Implementation Plan: Executing Plans Inline (obra/superpowers, 296k stars), Interview Me (addyosmani/agent-skills, 103k stars), OpenSpec Guided Onboarding (Fission-AI/OpenSpec, 71k stars) and Writing Plans (geeksblabla/stateofdev.ma, 163 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Starting An Implementation Plan?
ed3dai (a GitHub organization) maintains it in ed3dai/ed3d-plugins, which has 250 GitHub stars. The repository holds 34 skills in this directory. The repository was last updated on September 6, 2026.
Source: ed3dai/ed3d-plugins on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.