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 for complex multi-step tasks. An agent skill from peintune/runjam.
Install Writing Plans
$ npx skills add peintune/runjam --skill writing-plans -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install peintune/runjam 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/peintune/runjam.git skills-src && mkdir -p .claude/skills && cp -r skills-src/src-tauri/builtin-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/peintune/runjam/tree/main/src-tauri/builtin-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/peintune/runjam/tree/main/src-tauri/builtin-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 peintune/runjam --skill writing-plans -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install peintune/runjam writing-plans --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/peintune/runjam.git skills-src && mkdir -p .agents/skills && cp -r skills-src/src-tauri/builtin-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/peintune/runjam/tree/main/src-tauri/builtin-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 peintune/runjam --skill writing-plans -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install peintune/runjam writing-plans --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/peintune/runjam.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/src-tauri/builtin-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/peintune/runjam/tree/main/src-tauri/builtin-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/peintune/runjam.git --path src-tauri/builtin-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 peintune/runjam --skill writing-plans -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install peintune/runjam writing-plans --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/peintune/runjam.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/src-tauri/builtin-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/peintune/runjam/tree/main/src-tauri/builtin-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 peintune/runjam 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 peintune/runjam --skill writing-plans -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/peintune/runjam.git skills-src && mkdir -p .github/skills && cp -r skills-src/src-tauri/builtin-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/peintune/runjam/tree/main/src-tauri/builtin-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 peintune/runjam --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 peintune/runjam writing-plans --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/peintune/runjam.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/src-tauri/builtin-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/peintune/runjam/tree/main/src-tauri/builtin-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
- 228
- Token cost
- ~213 tokens
- SKILL.md length
- 85 words
- Files
- 1
- Skills in repo
- 7
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses for complex multi-step tasks. An agent skill from peintune/runjam.
- Works in 5 steps: Goal: What are we trying to achieve? → Approach: High-level strategy → Steps: Ordered, actionable items → …
- Complex multi-step tasks
- SKILL.md covers Plan Structure, When to Plan and Anti-Patterns
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Writing Plans is an agent skill from peintune/runjam. Use for complex multi-step tasks. Create a structured plan before writing code. Use when the user asks for a plan, spec, or when the task is too large to implement in one step.
Its SKILL.md is about 210 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: One desktop for all your AI coding Agent — Claude Code, Codex CLI & Gemini CLI. Auto-detect, one-click install, unified chat, file explorer, terminal & editor. Local-first. Built… The licence is MIT.
When your agent uses it
- Complex multi-step tasks
- The user asks for a plan
- The task is too large to implement in one step
Example prompts
- “/writing-plans”
Workflow steps
5 steps, taken from the first numbered list in SKILL.md.
- Goal: What are we trying to achieve?
- Approach: High-level strategy
- Steps: Ordered, actionable items
- Risks: What could go wrong?
- Alternatives: What else was considered?
What it can do on your machine
Read from SKILL.md and the folder at commit b186c61. 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.
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 213 tokens when it runs. Until then it costs about 48 tokens; SKILL.md has 85 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
The full file from peintune/runjam at commit b186c61, republished under its MIT licence (© peintune). 85 words, ~213 tokens.
Download SKILL.mdSave it as
.claude/skills/writing-plans/SKILL.md (or your agent's skills folder).- name
- writing-plans
- description
- Use for complex multi-step tasks. Create a structured plan before writing code. Use when the user asks for a plan, spec, or when the task is too large to implement in one step.
Writing Plans
For complex tasks, always plan before implementing.
Plan Structure
- Goal: What are we trying to achieve?
- Approach: High-level strategy
- Steps: Ordered, actionable items
- Risks: What could go wrong?
- Alternatives: What else was considered?
When to Plan
- Task spans multiple files or modules
- User explicitly asks for a plan
- Architecture decisions are needed
- Breaking changes to existing APIs
Anti-Patterns
- Planning for trivial tasks (single-file, single-function)
- Over-planning: more time planning than coding
- Plan has no action items — just abstract theory
© peintune, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in src-tauri/builtin-skills/writing-plans of peintune/runjam.
Open the folder on GitHubat commit b186c61
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 skillpeintune/runjam | 228 | — | ~213 | Automated safety check: Pass | MIT | |
| 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 | |
| Writing Plansgeeksblabla/stateofdev.ma | 163 | 57 repos | ~661 | Automated safety check: Pass | None | |
| Subagent Driven DevelopmentAsvarox/allkaraoke | 261 | 37 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 peintune/runjam
Mermaid
peintune/runjam
Render Mermaid diagrams as SVG or ASCII art using beautiful-mermaid.
Finishing A Development Branch
peintune/runjam
A skill your agent uses when development work is complete and you need to prepare for merge.
Ppt Generation
peintune/runjam
A skill your agent uses when the user requests to generate, create, or make presentations (PPT/PPTX).
Runjam Defaults
peintune/runjam
Default constraints for every RunJam session. An agent skill from peintune/runjam.
Code Review
peintune/runjam
A skill your agent uses when reviewing code for bugs, security issues, performance problems, or adherence to best practices.
Test Driven Development
peintune/runjam
A skill your agent uses when implementing any feature or bugfix, before writing implementation code.
Related
Categories
Questions about Writing Plans
What does Writing Plans do?
A skill your agent uses for complex multi-step tasks. An agent skill from peintune/runjam. Writing Plans is an agent skill from peintune/runjam. Use for complex multi-step tasks.
When should I use Writing Plans?
Writing Plans fits situations like: complex multi-step tasks; the user asks for a plan; the task is too large to implement in one step.
How do I install Writing Plans in Claude Code?
Run `npx skills add peintune/runjam --skill writing-plans -a claude-code`. Or copy the skill folder (src-tauri/builtin-skills/writing-plans in peintune/runjam) 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 peintune/runjam --skill writing-plans -a codex`. Or copy the skill folder (src-tauri/builtin-skills/writing-plans in peintune/runjam) 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 peintune/runjam --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?
Writing 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 Writing Plans use?
About 213 tokens (SKILL.md is roughly 852 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 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 Writing Plans?
peintune (a GitHub user) maintains it in peintune/runjam, which has 228 GitHub stars. The repository holds 7 skills in this directory. The repository was last updated on October 5, 2026.
Source: peintune/runjam on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.