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.
OpenTeams-only workflow skill. An agent skill from openteams-lab/openteams.
Install Writing Plans
$ npx skills add openteams-lab/openteams --skill writing-plans -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install openteams-lab/openteams 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/openteams-lab/openteams.git skills-src && mkdir -p .claude/skills && cp -r skills-src/assets/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/openteams-lab/openteams/tree/main/assets/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/openteams-lab/openteams/tree/main/assets/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 openteams-lab/openteams --skill writing-plans -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install openteams-lab/openteams writing-plans --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/openteams-lab/openteams.git skills-src && mkdir -p .agents/skills && cp -r skills-src/assets/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/openteams-lab/openteams/tree/main/assets/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 openteams-lab/openteams --skill writing-plans -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install openteams-lab/openteams writing-plans --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/openteams-lab/openteams.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/assets/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/openteams-lab/openteams/tree/main/assets/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/openteams-lab/openteams.git --path assets/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 openteams-lab/openteams --skill writing-plans -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install openteams-lab/openteams writing-plans --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/openteams-lab/openteams.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/assets/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/openteams-lab/openteams/tree/main/assets/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 openteams-lab/openteams 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 openteams-lab/openteams --skill writing-plans -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/openteams-lab/openteams.git skills-src && mkdir -p .github/skills && cp -r skills-src/assets/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/openteams-lab/openteams/tree/main/assets/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 openteams-lab/openteams --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 openteams-lab/openteams writing-plans --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/openteams-lab/openteams.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/assets/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/openteams-lab/openteams/tree/main/assets/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
- 628
- Token cost
- ~1.3k tokens
- SKILL.md length
- 642 words
- Files
- 1
- Skills in repo
- 7
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
OpenTeams-only workflow skill. An agent skill from openteams-lab/openteams.
- You have a spec
- SKILL.md covers OpenTeams-only availability, Overview, Scope Check and File Structure, plus 6 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Requirements for a multi-step task
What it does
Writing Plans is an agent skill from openteams-lab/openteams. OpenTeams-only workflow skill. Use when you have a spec or requirements for a multi-step task, before touching code
Its SKILL.md is about 1.3k 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: Plan, Build, and Ship — with a team of AI agents instead of one. The licence is Apache-2.0.
When your agent uses it
- You have a spec
- Requirements for a multi-step task
- Before touching code
Example prompts
- “/writing-plans”
Requirements
- Python 3
What it can do on your machine
Read from SKILL.md and the folder at commit 5450234. 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 1.3k tokens when it runs. Until then it costs about 32 tokens; SKILL.md has 642 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 openteams-lab/openteams at commit 5450234, republished under its Apache-2.0 licence (© openteams-lab). 642 words, ~1,348 tokens.
Download SKILL.mdSave it as
.claude/skills/writing-plans/SKILL.md (or your agent's skills folder).- name
- writing-plans
- description
- OpenTeams-only workflow skill. Use when you have a spec or requirements for a multi-step task, before touching code
Writing Plans
OpenTeams-only availability
This skill is part of the OpenTeams workflow and is only available when the current input prompt starts with:
[OPENTEAMS_SOURCE=openteams]If this marker is absent, do not use this skill. Tell the caller that writing-plans is only available through OpenTeams.
Overview
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, testing, docs they might need to check, how to test it. Give them the whole plan as bite-sized tasks. DRY. YAGNI. TDD. Frequent commits.
Assume they are a skilled developer, but know almost nothing about our toolset or problem domain. Assume they don't know good test design very well.
Announce at start: "I'm using the writing-plans skill to create the implementation plan."
Context: If working in an isolated worktree, it should have been created via the using-git-worktrees skill at execution time.
Save plans to: .openteams/plans/YYYY-MM-DD-<feature-name>.md
- (User preferences for plan location override this default)
Scope Check
If the spec covers multiple independent subsystems, it should have been broken into sub-project specs during brainstorming. If it wasn't, suggest breaking this into separate plans — one per subsystem. Each plan should produce working, testable software on its own.
File Structure
Before defining tasks, map out which files will be created or modified and what each one is responsible for. This is where decomposition decisions get locked in.
- Design units with clear boundaries and well-defined interfaces. Each file should have one clear responsibility.
- You reason best about code you can hold in context at once, and your edits are more reliable when files are focused. Prefer smaller, focused files over large ones that do too much.
- Files that change together should live together. Split by responsibility, not by technical layer.
- In existing codebases, follow established patterns. If the codebase uses large files, don't unilaterally restructure - but if a file you're modifying has grown unwieldy, including a split in the plan is reasonable.
This structure informs the task decomposition. Each task should produce self-contained changes that make sense independently.
Bite-Sized Task Granularity
Each step is one action (2-5 minutes):
- "Write the failing test" - step
- "Run it to make sure it fails" - step
- "Implement the minimal code to make the test pass" - step
- "Run the tests and make sure they pass" - step
- "Commit" - step
Show full SKILL.md (251 more words)Show less
Plan Document Header
Every plan MUST start with this header:
# [Feature Name] Implementation Plan
**Goal:** [One sentence describing what this builds]
**Architecture:** [2-3 sentences about approach]
**Tech Stack:** [Key technologies/libraries]
---Task Example
### Task N: [Component Name]
**Files:**
- Create: `exact/path/to/file.py`
- Modify: `exact/path/to/existing.py:123-145`
- Test: `tests/exact/path/to/test.py`
- **Step 1: Write the failing test**
```python
def test_specific_behavior():
result = function(input)
assert result == expected
```
- **Step 2: Run test to verify it fails**
Run: `pytest tests/path/test.py::test_name -v`
Expected: FAIL with "function not defined"
- **Step 3: Write minimal implementation**
```python
def function(input):
return expected
```
- **Step 4: Run test to verify it passes**
Run: `pytest tests/path/test.py::test_name -v`
Expected: PASS
- **Step 5: Commit**
```bash
git add tests/path/test.py src/path/file.py
git commit -m "feat: add specific feature"
```No Placeholders
Every step must contain the actual content an engineer needs. These are plan failures — never write them:
- "TBD", "TODO", "implement later", "fill in details"
- "Add appropriate error handling" / "add validation" / "handle edge cases"
- "Write tests for the above" (without actual test code)
- "Similar to Task N" (repeat the code — the engineer may be reading tasks out of order)
- Steps that describe what to do without showing how (code blocks required for code steps)
- References to types, functions, or methods not defined in any task
Remember
- Exact file paths always
- Exact commands with expected output
- DRY, YAGNI, TDD, frequent commits
Self-Review
After writing the complete plan, look at the spec with fresh eyes and check the plan against it. This is a checklist you run yourself — not a subagent dispatch.
1. Spec coverage: Skim each section/requirement in the spec. Can you point to a task that implements it? List any gaps.
2. Placeholder scan: Search your plan for red flags — any of the patterns from the "No Placeholders" section above. Fix them.
3. Type consistency: Do the types, method signatures, and property names you used in later tasks match what you defined in earlier tasks? A function called clearLayers() in Task 3 but clearFullLayers() in Task 7 is a bug.
If you find issues, fix them inline. No need to re-review — just fix and move on. If you find a spec requirement with no task, add the task.
© openteams-lab, Apache-2.0. 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 assets/skills/writing-plans of openteams-lab/openteams.
Open the folder on GitHubat commit 5450234
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 skillopenteams-lab/openteams | 628 | — | ~1.3k | Automated safety check: Pass | Apache-2.0 | |
| Executing Plans Inlineobra/superpowers | 297k | 2 repos | ~5.1k | Automated safety check: Pass | MIT | |
| Interview Meaddyosmani/agent-skills | 105k | 6 repos | ~3.8k | Automated safety check: Pass | MIT | |
| OpenSpec Guided OnboardingFission-AI/OpenSpec | 72k | 1 repos | ~4.5k | Automated safety check: Pass | MIT | |
| Writing Plansgeeksblabla/stateofdev.ma | 163 | 58 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 openteams-lab/openteams
Brainstorming
openteams-lab/openteams
OpenTeams-only workflow skill. An agent skill from openteams-lab/openteams.
Code Guidelines
openteams-lab/openteams
OpenTeams-only workflow skill. An agent skill from openteams-lab/openteams.
GitHub Actions Run And Fix
openteams-lab/openteams
OpenTeams skill for manually starting a GitHub Actions workflow, watching its execution, diagnosing failures, rerunning transient failed jobs, repairing code or configuration errors, and dispatching…
GitHub PR Actions Fix
openteams-lab/openteams
OpenTeams skill for watching GitHub Actions checks after a pull request is submitted or updated, inspecting failures, making the smallest safe code fix, validating locally, pushing to the PR branch…
Planning Mode
openteams-lab/openteams
A skill your agent uses when the user asks to break down a goal into a clear, executable, reviewable task plan using WBS, dependencies, milestones, RACI, risk register, and plan review.
Using Git Worktrees
openteams-lab/openteams
A skill your agent uses when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools, git…
Related
Categories
Questions about Writing Plans
What does Writing Plans do?
OpenTeams-only workflow skill. An agent skill from openteams-lab/openteams. Writing Plans is an agent skill from openteams-lab/openteams. OpenTeams-only workflow skill.
When should I use Writing Plans?
Writing Plans fits situations like: you have a spec; requirements for a multi-step task; before touching code.
How do I install Writing Plans in Claude Code?
Run `npx skills add openteams-lab/openteams --skill writing-plans -a claude-code`. Or copy the skill folder (assets/skills/writing-plans in openteams-lab/openteams) 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 openteams-lab/openteams --skill writing-plans -a codex`. Or copy the skill folder (assets/skills/writing-plans in openteams-lab/openteams) 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 openteams-lab/openteams --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. Our summary lists: Python 3.
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 Apache-2.0 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 1.3k tokens (SKILL.md is roughly 5.4k 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, 105k stars), OpenSpec Guided Onboarding (Fission-AI/OpenSpec, 72k 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?
openteams-lab (a GitHub organization) maintains it in openteams-lab/openteams, which has 628 GitHub stars. The repository holds 7 skills in this directory. The repository was last updated on October 11, 2026.
Source: openteams-lab/openteams on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.