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.
Create concise, architectural implementation plans using the RFC-Lite format.
Install Planning Mastery
$ npx skills add xenitV1/claude-code-maestro --skill planning-mastery -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install xenitV1/claude-code-maestro planning-mastery --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/xenitV1/claude-code-maestro.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/planning-mastery .claude/skills/planning-mastery && 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 "planning-mastery" agent skill from https://github.com/xenitV1/claude-code-maestro/tree/main/skills/planning-mastery into .claude/skills/planning-mastery/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "planning-mastery", 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/xenitV1/claude-code-maestro/tree/main/skills/planning-masteryType 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 xenitV1/claude-code-maestro --skill planning-mastery -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install xenitV1/claude-code-maestro planning-mastery --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/xenitV1/claude-code-maestro.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/planning-mastery .agents/skills/planning-mastery && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "planning-mastery" agent skill from https://github.com/xenitV1/claude-code-maestro/tree/main/skills/planning-mastery into .agents/skills/planning-mastery/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "planning-mastery", 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 xenitV1/claude-code-maestro --skill planning-mastery -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install xenitV1/claude-code-maestro planning-mastery --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/xenitV1/claude-code-maestro.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/planning-mastery .cursor/skills/planning-mastery && 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 "planning-mastery" agent skill from https://github.com/xenitV1/claude-code-maestro/tree/main/skills/planning-mastery into .cursor/skills/planning-mastery/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "planning-mastery", 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/xenitV1/claude-code-maestro.git --path skills/planning-mastery--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 xenitV1/claude-code-maestro --skill planning-mastery -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install xenitV1/claude-code-maestro planning-mastery --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/xenitV1/claude-code-maestro.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/planning-mastery .gemini/skills/planning-mastery && 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 "planning-mastery" agent skill from https://github.com/xenitV1/claude-code-maestro/tree/main/skills/planning-mastery into .gemini/skills/planning-mastery/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "planning-mastery", 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 xenitV1/claude-code-maestro planning-masteryInstalls 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 xenitV1/claude-code-maestro --skill planning-mastery -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/xenitV1/claude-code-maestro.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/planning-mastery .github/skills/planning-mastery && 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 "planning-mastery" agent skill from https://github.com/xenitV1/claude-code-maestro/tree/main/skills/planning-mastery into .github/skills/planning-mastery/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "planning-mastery", 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 xenitV1/claude-code-maestro --skill planning-mastery -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install xenitV1/claude-code-maestro planning-mastery --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/xenitV1/claude-code-maestro.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/planning-mastery .opencode/skills/planning-mastery && 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 "planning-mastery" agent skill from https://github.com/xenitV1/claude-code-maestro/tree/main/skills/planning-mastery into .opencode/skills/planning-mastery/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "planning-mastery", 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
planning-mastery- GitHub stars
- 229
- Token cost
- ~699 tokens
- SKILL.md length
- 213 words
- Files
- 1
- Skills in repo
- 13
- Repo updated
- First seen
- Licence
- MIT
At a glance
Create concise, architectural implementation plans using the RFC-Lite format.
- Works in 4 steps: NO CODE BLOCKS: Do not write function… → NO EXPLANATIONS: Do not teach the user… → NO CONVERSATION: Do not talk to the user… → …
- Tasks that involve Planning
- SKILL.md covers 🎯 CORE PHILOSOPHY, 📝 MANDATORY TEMPLATE (Copy &…, ⛔ ZERO TOLERANCE RULES and 📂 COGNITIVE AUDIT CYCLE
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Planning Mastery is an agent skill from xenitV1/claude-code-maestro. Create concise, architectural implementation plans using the RFC-Lite format. STRICTLY LIMITED VERBOSITY.
Its SKILL.md is about 700 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 licence is MIT.
When your agent uses it
- Tasks that involve Planning
Example prompts
- “/planning-mastery”
Requirements
- Pre-approved tools (allowed-tools): Read, Write, Edit, Glob, Grep, Bash
Workflow steps
4 steps, taken from the first numbered list in SKILL.md.
- NO CODE BLOCKS: Do not write function bodies in the plan.
- NO EXPLANATIONS: Do not teach the user why React is good.
- NO CONVERSATION: Do not talk to the user in the plan.
- STAY HIGH LEVEL: "Implement Auth" is better than "Write function login() { ... }".
What it can do on your machine
Read from SKILL.md and the folder at commit 924315b. 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:
ReadWriteEditGlobGrepBash
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
Planning Mastery loads about 699 tokens when it runs. Until then it costs about 31 tokens; SKILL.md has 213 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, Write, Edit, Glob, Grep, 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 xenitV1/claude-code-maestro at commit 924315b, republished under its MIT licence (© xenitV1). 213 words, ~699 tokens.
Download SKILL.mdSave it as
.claude/skills/planning-mastery/SKILL.md (or your agent's skills folder).- name
- planning-mastery
- description
- Create concise, architectural implementation plans using the RFC-Lite format. STRICTLY LIMITED VERBOSITY.
- allowed-tools
- Read, Write, Edit, Glob, Grep, Bash
<domain_overview>
📋 RFC-Lite Planning Protocol
The 300-Line Limit: If your plan exceeds 300 lines, YOU HAVE FAILED. Rule: Code belongs in files, not plans. Do not write pseudo-code. Do not paste entire file contents. Focus: Define What (Files), How (Logic Strategy), and Success (Verification).
DEPENDENCY FORECASTING MANDATE (CRITICAL): Never propose a change without mapping its "Blast Radius". AI-generated plans frequently fail by ignoring downstream effects on coupled modules. Before defining file changes, you MUST explicitly identify which existing features or tests might break. If a change requires "Shotgun Surgery" (modifying more than 5 files for one feature), you MUST pause and propose an architectural abstraction instead.
</domain_overview>
<philosophy>
🎯 CORE PHILOSOPHY
Understanding comes before implementation. A well-designed solution is half-implemented. Never code without a clear design.
</philosophy>
<template_enforcement>
📝 MANDATORY TEMPLATE (Copy & Fill)
# [Task/Feature Name] - Implementation Plan
## 1. 🎯 Objective
[1-2 sentences strictly defining the goal.]
## 2. 🏗️ Tech Strategy
- **Pattern:** [e.g. Composition vs Inheritance]
- **State:** [e.g. Global Store vs Local Hook]
- **Constraints:** [e.g. "Must use LCH colors", "No external libs"]
## 3. 📂 File Changes
| Action | File Path | Brief Purpose |
|:-------|:----------|:--------------|
| [NEW] | `src/components/MyComp.tsx` | Visual shell |
| [MOD] | `src/App.tsx` | Routing integration |
## 4. 👣 Execution Sequence
1. **Scaffold:** Create component files with types (No logic yet).
2. **Logic:** Implement `useLogic.ts` hook with TDD.
3. **Visuals:** Apply LCH gradients & Glassmorphism.
4. **Connect:** Wire up to parent component.
## 5. ✅ Verification Standards
- [ ] **Visual:** Check against `frontend_reference.md` (no flat colors).
- [ ] **Interaction:** Verify `scale(0.97)` tap effect.
- [ ] **Console:** Zero errors during flow.</template_enforcement> <strict_rules>
⛔ ZERO TOLERANCE RULES
- NO CODE BLOCKS: Do not write function bodies in the plan.
- NO EXPLANATIONS: Do not teach the user why React is good.
- NO CONVERSATION: Do not talk to the user in the plan.
- STAY HIGH LEVEL: "Implement Auth" is better than "Write function login() { ... }". </strict_rules> <audit_and_reference>
📂 COGNITIVE AUDIT CYCLE
- Does the plan exceed 300 lines?
- Are all breaking changes identified?
- Is it RFC-Lite compliant?
- Are verification steps actionable commands? </audit_and_reference>
© xenitV1, 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 skills/planning-mastery of xenitV1/claude-code-maestro.
Open the folder on GitHubat commit 924315b
Compare with similar skills
Planning Mastery 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 |
|---|---|---|---|---|---|---|
| Planning Mastery this skillxenitV1/claude-code-maestro | 229 | — | ~699 | Automated safety check: Notes | 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 xenitV1/claude-code-maestro
All 13 skills in this repoClean Code
xenitV1/claude-code-maestro
The Foundation Skill. An agent skill from xenitV1/claude-code-maestro.
Ralph Wiggum
xenitV1/claude-code-maestro
Surgical Debugger & Code Optimizer. An agent skill from xenitV1/claude-code-maestro.
Backend Design
xenitV1/claude-code-maestro
Elite Tier Backend standards, including Vertical Slice Architecture, Zero Trust Security, and High-Performance API protocols.
Brainstorming
xenitV1/claude-code-maestro
Design-first methodology. An agent skill from xenitV1/claude-code-maestro.
Browser Extension
xenitV1/claude-code-maestro
Master specialized skill for building 2025/2026-grade browser extensions.
Debug Mastery
xenitV1/claude-code-maestro
Systematic debugging methodology with 4-phase process, root cause tracing, and elite observability standards.
Related
Categories
Questions about Planning Mastery
What does Planning Mastery do?
Create concise, architectural implementation plans using the RFC-Lite format. Planning Mastery is an agent skill from xenitV1/claude-code-maestro. Create concise, architectural implementation plans using the RFC-Lite format.
When should I use Planning Mastery?
Planning Mastery fits situations like: tasks that involve Planning.
How do I install Planning Mastery in Claude Code?
Run `npx skills add xenitV1/claude-code-maestro --skill planning-mastery -a claude-code`. Or copy the skill folder (skills/planning-mastery in xenitV1/claude-code-maestro) into .claude/skills/planning-mastery in your project. Claude Code loads it when a task matches its description.
How do I install Planning Mastery in Codex?
Run `npx skills add xenitV1/claude-code-maestro --skill planning-mastery -a codex`. Or copy the skill folder (skills/planning-mastery in xenitV1/claude-code-maestro) into .agents/skills/planning-mastery in your project. Codex loads it when a task matches its description.
Can I use Planning Mastery 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 xenitV1/claude-code-maestro --skill planning-mastery -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/planning-mastery, .gemini/skills/planning-mastery, .github/skills/planning-mastery and .opencode/skills/planning-mastery in your project.
What does Planning Mastery need to run?
SKILL.md names no scripts, command-line tools or credentials: Planning Mastery is instructions for the agent only. Its frontmatter pre-approves these tools: Read, Write, Edit, Glob, Grep, Bash.
Does Planning Mastery 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 Planning Mastery 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 Planning Mastery use?
Planning Mastery 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 Planning Mastery use?
About 699 tokens (SKILL.md is roughly 2.8k 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 Planning Mastery?
Skills that share tags, products or a category with Planning Mastery: 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 Planning Mastery?
xenitV1 (a GitHub user) maintains it in xenitV1/claude-code-maestro, which has 229 GitHub stars. The repository holds 13 skills in this directory. The repository was last updated on January 24, 2026.
Source: xenitV1/claude-code-maestro on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.