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 design is complete and you need detailed implementation tasks for engineers with zero codebase context - creates comprehensive implementation plans with exact file…
Install Writing Plans
$ npx skills add geeksblabla/stateofdev.ma --skill writing-plans -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install geeksblabla/stateofdev.ma writing-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/geeksblabla/stateofdev.ma.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/writing-plans .claude/skills/writing-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 "writing-plans" agent skill from https://github.com/geeksblabla/stateofdev.ma/tree/master/.claude/skills/writing-plans into .claude/skills/writing-plans/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "writing-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/geeksblabla/stateofdev.ma/tree/master/.claude/skills/writing-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 geeksblabla/stateofdev.ma --skill writing-plans -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install geeksblabla/stateofdev.ma writing-plans --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/geeksblabla/stateofdev.ma.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/writing-plans .agents/skills/writing-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 "writing-plans" agent skill from https://github.com/geeksblabla/stateofdev.ma/tree/master/.claude/skills/writing-plans into .agents/skills/writing-plans/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "writing-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 geeksblabla/stateofdev.ma --skill writing-plans -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install geeksblabla/stateofdev.ma writing-plans --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/geeksblabla/stateofdev.ma.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/writing-plans .cursor/skills/writing-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 "writing-plans" agent skill from https://github.com/geeksblabla/stateofdev.ma/tree/master/.claude/skills/writing-plans into .cursor/skills/writing-plans/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "writing-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/geeksblabla/stateofdev.ma.git --path .claude/skills/writing-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 geeksblabla/stateofdev.ma --skill writing-plans -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install geeksblabla/stateofdev.ma writing-plans --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/geeksblabla/stateofdev.ma.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/writing-plans .gemini/skills/writing-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 "writing-plans" agent skill from https://github.com/geeksblabla/stateofdev.ma/tree/master/.claude/skills/writing-plans into .gemini/skills/writing-plans/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "writing-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 geeksblabla/stateofdev.ma writing-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 geeksblabla/stateofdev.ma --skill writing-plans -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/geeksblabla/stateofdev.ma.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/writing-plans .github/skills/writing-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 "writing-plans" agent skill from https://github.com/geeksblabla/stateofdev.ma/tree/master/.claude/skills/writing-plans into .github/skills/writing-plans/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "writing-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 geeksblabla/stateofdev.ma --skill writing-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 geeksblabla/stateofdev.ma writing-plans --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/geeksblabla/stateofdev.ma.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/writing-plans .opencode/skills/writing-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 "writing-plans" agent skill from https://github.com/geeksblabla/stateofdev.ma/tree/master/.claude/skills/writing-plans into .opencode/skills/writing-plans/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "writing-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
writing-plans- GitHub stars
- 163
- Used in
- 57 other repos
- Token cost
- ~661 tokens
- SKILL.md length
- 216 words
- Files
- 1
- Skills in repo
- 2
- Repo updated
- First seen
- Licence
- None found
At a glance
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…
- Complete code examples
- SKILL.md covers Overview, Bite-Sized Task Granularity, Plan Document Header and Task Structure, plus 2 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Verification steps assuming engineer has minimal domain knowledge
What it does
Writing Plans is an agent skill from geeksblabla/stateofdev.ma. Use when design is complete and you need detailed implementation tasks for engineers with zero codebase context - creates comprehensive implementation plans with exact file paths, complete code examples, and verification steps assuming engineer has minimal domain knowledge
Its SKILL.md is about 660 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: stateofdev.ma source code.
When your agent uses it
- Complete code examples
- Verification steps assuming engineer has minimal domain knowledge
Example prompts
- “/writing-plans”
What it can do on your machine
Read from SKILL.md and the folder at commit b21fd7f. 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
No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown).
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
Writing Plans loads about 661 tokens when it runs. Until then it costs about 72 tokens; SKILL.md has 216 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 216 words (~661 tokens).
“Write comprehensive implementation plans assuming the engineer has zero context for our codebase and questionable taste. Document everything they need to know: which files to touch for each task, code, docs they might need to check. Give them the whole…”
- name
- writing-plans
Files
Just SKILL.md in .claude/skills/writing-plans of geeksblabla/stateofdev.ma.
Open the folder on GitHubat commit b21fd7f
Used in at least 35 other repositories
We found 91 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 57 other GitHub owners. This page covers the copy in geeksblabla/stateofdev.ma, which our catalogue first saw on October 7, 2026.
- Asvarox/allkaraoke.agents/skills/write-plan
- farm-fe/farm.agents/skills/writing-plans.claude/skills/writing-plans
- brevdev/workshop-build-an-agentcode/4-agent-customization/skills/superpowers/writing-plans
- obra/superpowersskills/writing-plans
- julianromli/opencode-templateskill/writing-plans
- SuFxGIT/scoutarr.agents/skills/writing-plans
- jamditis/claude-skills-journalismsuperjawn/skills/writing-plans
- tctinh/agent-hive.github/skills/writing-planspackages/opencode-hive/skills/writing-plans+1 more
- guanyang/open-agent-hubskills/writing-plans
- jd-opensource/JoySafeterskills/writing-plans
- ed3dai/ed3d-pluginsplugins/ed3d-plan-and-execute/skills/writing-implementation-plans
- aaddrick/claude-pipeline.claude/skills/writing-plans
- spacering-net/codegsrc-tauri/experts/skills/writing-plans
- coctostan/pi-superpowers-plusskills/writing-plans
- involvex/youtube-music-cli.agents/skills/writing-plans.claude/skills/writing-plans
- Ibrahim-3d/orchestrator-supaconductorskills/writing-plans
- haojing8312/WorkClaw.claude/skills/writing-plans
- 6BNBN/FlowPilot兼容codex@cursor一键安装技能/codex一键安装技能/纯手动安装/skills/writing-plans兼容codex@cursor一键安装技能/codex一键安装技能/.codex-home-claude-parity/skills/writing-plans
- NoobyGains/godmodeskills/task-planning
- AgentTeam-TaichuAI/ScienceClawSkills/writing-plans
- Houseofmvps/ultrashipskills/writing-plans
- AlphaLab-USTC/OhMyCode.agents/skills/superpowers/writing-plans.claude/skills/superpowers/writing-plans
- rpamis/cometeval/local/skills/benchmarks/dependency/superpowers/writing-plans
- getcrew44/crew44daemon/internal/presets/defaultcrew/skills/coding/writing-plans
- totvs/engpro-advpl-tlpp-skillsskills/superpowers/writing-plans
- NeuroAIHub/BrainPilotpackages/backend-core/plugins/superpowers/6.2.0/skills/writing-planspackages/backend-core/plugins/superpowers/6.2.1-bp.1/skills/writing-plans
- LayneChai/superpowers-dshskills/writing-plans
- Xu123-Bob/Baizeagent/skills/superpowers/5.1.0/skills/writing-plans
- VelaPayments/vela-payments.agents/skills/writing-plans.claude/skills/writing-plans
- VelaPayments/vela-server.agents/skills/writing-plans.claude/skills/writing-plans
- davila7/claude-code-templatescli-tool/components/skills/development/writing-planscli-tool/components/skills/productivity/writing-plans
- theexperiencecompany/gaia.agents/skills/writing-plans.claude/skills/writing-plans
- Microck/ordinary-claude-skillsskills_all/writing-plansskills_categorized/education/writing-plans+2 more
- CraftOS-dev/CraftBotskills/writing-plans
- aiskillstore/marketplaceskills/obra/writing-plansskills/davila7/writing-plans
…and 41 more copies not listed here.
Compare with similar skills
Writing 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 |
|---|---|---|---|---|---|---|
| Writing Plans this skillgeeksblabla/stateofdev.ma | 163 | 57 repos | ~661 | Automated safety check: Pass | None | |
| Executing Plans Inlineobra/superpowers | 297k | 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 | |
| Subagent Driven DevelopmentAsvarox/allkaraoke | 261 | 37 repos | ~1.2k | Automated safety check: Pass | None | |
| Planning With Filesjd-opensource/JoySafeter | 313 | 19 repos | ~1.8k | Automated safety check: Notes | Apache-2.0 |
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.
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.
Paseo Committee
getpaseo/paseo
Forms a two-agent committee with contrasting profiles to analyze a stuck problem in parallel, reconcile their views and return a consensus plan without editing files.
More from geeksblabla/stateofdev.ma
Executing Plans
geeksblabla/stateofdev.ma
A skill your agent uses when partner provides a complete implementation plan to execute in controlled batches with review checkpoints - loads plan, reviews critically, executes tasks in batches…
Related
Categories
Questions about Writing Plans
What does Writing Plans do?
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…. ma.
When should I use Writing Plans?
Writing Plans fits situations like: complete code examples; verification steps assuming engineer has minimal domain knowledge.
How do I install Writing Plans in Claude Code?
Run `npx skills add geeksblabla/stateofdev.ma --skill writing-plans -a claude-code`. Or copy the skill folder (.claude/skills/writing-plans in geeksblabla/stateofdev.ma) into .claude/skills/writing-plans in your project. Claude Code loads it when a task matches its description.
How do I install Writing Plans in Codex?
Run `npx skills add geeksblabla/stateofdev.ma --skill writing-plans -a codex`. Or copy the skill folder (.claude/skills/writing-plans in geeksblabla/stateofdev.ma) into .agents/skills/writing-plans in your project. Codex loads it when a task matches its description.
Can I use Writing 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 geeksblabla/stateofdev.ma --skill writing-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/writing-plans, .gemini/skills/writing-plans, .github/skills/writing-plans and .opencode/skills/writing-plans in your project.
What does Writing Plans need to run?
SKILL.md names no scripts, command-line tools or credentials: Writing Plans is instructions for the agent only.
Does Writing 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 Writing Plans 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 Writing Plans use?
No licence was found for Writing Plans or its repository. Without one, default copyright applies: ask the author before reusing or redistributing it.
How many tokens does Writing Plans use?
About 661 tokens (SKILL.md is roughly 2.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 Writing Plans?
Skills that share tags, products or a category with Writing Plans: Executing Plans Inline (obra/superpowers, 297k stars), Interview Me (addyosmani/agent-skills, 103k stars), OpenSpec Guided Onboarding (Fission-AI/OpenSpec, 71k stars) and Subagent Driven Development (Asvarox/allkaraoke, 261 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Writing Plans?
geeksblabla (a GitHub organization) maintains it in geeksblabla/stateofdev.ma, which has 163 GitHub stars. The repository holds 2 skills in this directory. The repository was last updated on March 1, 2026.
Source: geeksblabla/stateofdev.ma on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.