MCP Server Builder
anthropics/skills
Guides the design and implementation of Model Context Protocol servers in TypeScript or Python, from tool naming and error messages to evaluation.
Create structured plans for multi-task projects that can be used by the task-orchestrator skill.
Install Planner
$ npx skills add jdrhyne/agent-skills --skill planner -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install jdrhyne/agent-skills planner --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/jdrhyne/agent-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/planner .claude/skills/planner && 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 "planner" agent skill from https://github.com/jdrhyne/agent-skills/tree/main/skills/planner into .claude/skills/planner/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "planner", 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/jdrhyne/agent-skills/tree/main/skills/plannerType 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 jdrhyne/agent-skills --skill planner -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install jdrhyne/agent-skills planner --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jdrhyne/agent-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/planner .agents/skills/planner && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "planner" agent skill from https://github.com/jdrhyne/agent-skills/tree/main/skills/planner into .agents/skills/planner/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "planner", 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 jdrhyne/agent-skills --skill planner -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install jdrhyne/agent-skills planner --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jdrhyne/agent-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/planner .cursor/skills/planner && 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 "planner" agent skill from https://github.com/jdrhyne/agent-skills/tree/main/skills/planner into .cursor/skills/planner/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "planner", 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/jdrhyne/agent-skills.git --path skills/planner--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 jdrhyne/agent-skills --skill planner -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install jdrhyne/agent-skills planner --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jdrhyne/agent-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/planner .gemini/skills/planner && 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 "planner" agent skill from https://github.com/jdrhyne/agent-skills/tree/main/skills/planner into .gemini/skills/planner/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "planner", 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 jdrhyne/agent-skills plannerInstalls 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 jdrhyne/agent-skills --skill planner -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/jdrhyne/agent-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/planner .github/skills/planner && 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 "planner" agent skill from https://github.com/jdrhyne/agent-skills/tree/main/skills/planner into .github/skills/planner/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "planner", 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 jdrhyne/agent-skills --skill planner -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install jdrhyne/agent-skills planner --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jdrhyne/agent-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/planner .opencode/skills/planner && 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 "planner" agent skill from https://github.com/jdrhyne/agent-skills/tree/main/skills/planner into .opencode/skills/planner/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "planner", 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
planner- GitHub stars
- 240
- Token cost
- ~956 tokens
- SKILL.md length
- 301 words
- Files
- 1
- Skills in repo
- 20
- Repo updated
- First seen
- Licence
- MIT
At a glance
Create structured plans for multi-task projects that can be used by the task-orchestrator skill.
- Works in 5 steps: Phase 0: Clarify requirements (ask up to… → Phase 1: Research & understand the… → Phase 2: Create detailed plan with… → …
- Breaking down complex work into parallel and sequential tasks with dependencies
- SKILL.md covers Quick Start, Key Principles, Plan Template and Hand-off, plus 2 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Planner is an agent skill from jdrhyne/agent-skills. Create structured plans for multi-task projects that can be used by the task-orchestrator skill. Use when breaking down complex work into parallel and sequential tasks with dependencies.
Its SKILL.md is about 960 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. The repository describes itself as: A collection of AI agent skills for Clawdbot, Claude Code, Codex. The licence is MIT.
When your agent uses it
- Breaking down complex work into parallel and sequential tasks with dependencies
Example prompts
- “/planner”
Workflow steps
5 steps, taken from the first numbered list in SKILL.md.
- Phase 0: Clarify requirements (ask up to 5 targeted questions)
- Phase 1: Research & understand the codebase
- Phase 2: Create detailed plan with sprints, tasks, acceptance criteria
- Phase 3: Subagent review of the plan
- Phase 4: Return the plan in markdown and save a file only if the user asked for a persisted artifact
What it can do on your machine
Read from SKILL.md and the folder at commit 439cd3a. 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
Planner loads about 956 tokens when it runs. Until then it costs about 49 tokens; SKILL.md has 301 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 jdrhyne/agent-skills at commit 439cd3a, republished under its MIT licence (© jdrhyne). 301 words, ~956 tokens.
Download SKILL.mdSave it as
.claude/skills/planner/SKILL.md (or your agent's skills folder).- name
- planner
- description
- Create structured plans for multi-task projects that can be used by the task-orchestrator skill. Use when breaking down complex work into parallel and sequential tasks with dependencies.
Planner
Create structured, orchestrator-ready plans for multi-task projects.
Source: Adapted from am-will's codex-skills workflow patterns Pairs with: task-orchestrator skill for follow-on implementation
Quick Start
Follow this process:
- Phase 0: Clarify requirements (ask up to 5 targeted questions)
- Phase 1: Research & understand the codebase
- Phase 2: Create detailed plan with sprints, tasks, acceptance criteria
- Phase 3: Subagent review of the plan
- Phase 4: Return the plan in markdown and save a file only if the user asked for a persisted artifact
Key Principles
Task Atomicity
Each task must be:
- Atomic and committable — small, independent pieces of work
- Specific and actionable — not vague
- Testable — include tests or validation method
- Located — include file paths and code locations
Bad vs Good Task Breakdown
❌ Bad: "Implement third-party sign-in"
✓ Good:
- "Add sign-in config to environment variables"
- "Install and configure the required authentication package"
- "Create sign-in callback route handler in src/routes/auth.ts"
- "Add the sign-in button to the login UI"
Sprint Structure
Each sprint must:
- Result in a demoable, runnable, testable increment
- Build on prior sprint work
- Include clear demo/verification checklist
Plan Template
# Plan: [Task Name]
**Generated**: [Date]
**Estimated Complexity**: [Low/Medium/High]
## Overview
[Brief summary of what needs to be done and the general approach]
## Prerequisites
- [Dependencies or requirements that must be met first]
- [Tools, libraries, or access needed]
- [Tooling limitations, e.g., browser relay/CDP restrictions]
## Sprint 1: [Sprint Name]
**Goal**: [What this sprint accomplishes]
**Demo/Validation**:
- [How to run/demo this sprint's output]
- [What to verify]
### Task 1.1: [Task Name]
- **Location**: [File paths or components involved]
- **Description**: [What needs to be done]
- **Perceived Complexity**: [1-10]
- **Dependencies**: [Any previous tasks this depends on]
- **Acceptance Criteria**:
- [Specific, testable criteria]
- **Validation**:
- [Test(s) or alternate validation steps]
### Task 1.2: [Task Name]
[...]
## Sprint 2: [Sprint Name]
[...]
## Testing Strategy
- [How to test the implementation]
- [What to verify at each sprint]
## Potential Risks
- [Things that could go wrong]
- [Mitigation strategies]
## Rollback Plan
- [How to undo changes if needed]Hand-off
Once plan is ready, hand off to the parallel-task worker:
Please run parallel-task.md against my-plan.mdOr invoke directly:
"Run all unblocked tasks in plan.md using parallel subagents. Keep looping until all tasks are complete."
Safety Boundaries
- Do not save a plan file unless the user asked for one or the surrounding workflow explicitly needs a persisted artifact.
- Do not assign overlapping write scopes to parallel tasks without calling out the conflict.
- Do not invent dependencies, validation steps, or completion status that the repo context does not support.
- Do not turn a planning request into implementation work unless the user explicitly asks to move from planning to implementation.
Related
parallel-task— Parallel task worker that executes the plan this skill produces
Adapted from am-will's codex-skills planner/parallel-task prompts.
© jdrhyne, 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/planner of jdrhyne/agent-skills.
Open the folder on GitHubat commit 439cd3a
Compare with similar skills
Planner 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 |
|---|---|---|---|---|---|---|
| Planner this skilljdrhyne/agent-skills | 240 | — | ~956 | Automated safety check: Pass | MIT | |
| MCP Server Builderanthropics/skills | 180k | 63 repos | ~2.3k | Automated safety check: Pass | Apache-2.0 | |
| Hook Development for Claude Code Pluginsanthropics/claude-plugins-official | 38k | 10 repos | ~4.1k | Automated safety check: Notes | Apache-2.0 | |
| Using Superpowersfarm-fe/farm | 5.6k | 35 repos | ~1.4k | Automated safety check: Pass | MIT | |
| Executing Plans Inlineobra/superpowers | 297k | 2 repos | ~5.1k | Automated safety check: Pass | MIT | |
| Skill CreatorAzure/azqr | 795 | 89 repos | ~8.2k | Automated safety check: Pass | Apache-2.0 |
Similar skills
- Official
- Official
Hook Development for Claude Code Plugins
anthropics/claude-plugins-official
Explains how to write Claude Code plugin hooks, both prompt-based checks and bash commands, for events such as PreToolUse, Stop and SessionStart.
Using Superpowers
farm-fe/farm
A skill your agent uses when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions
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.
- Official
Skill Creator
Azure/azqr
Create new skills, modify and improve existing skills, and measure skill performance.
- Official
Claude Code Agent Development
anthropics/claude-plugins-official
Explains how to write agents for Claude Code plugins: the markdown file with YAML frontmatter, trigger descriptions, model and color settings, and system prompt design.
More from jdrhyne/agent-skills
All 20 skills in this repoGong
jdrhyne/agent-skills
Gong API for searching calls, transcripts, and conversation intelligence.
Elegant Reports
jdrhyne/agent-skills
Generate beautifully designed PDF reports with a Nordic/Scandinavian aesthetic.
Ga4
jdrhyne/agent-skills
Read Google Analytics 4 reporting data through the GA4 Data API.
Gallery Scraper
jdrhyne/agent-skills
Bulk download images from login-protected gallery websites using an attached browser session.
Gsc
jdrhyne/agent-skills
Read Google Search Console properties, Search Analytics, URL Inspection, and sitemaps.
Nudocs
jdrhyne/agent-skills
Upload, edit, and export documents via Nudocs.ai. An agent skill from jdrhyne/agent-skills.
Related
Categories
Questions about Planner
What does Planner do?
Create structured plans for multi-task projects that can be used by the task-orchestrator skill. Planner is an agent skill from jdrhyne/agent-skills. Create structured plans for multi-task projects that can be used by the task-orchestrator skill.
When should I use Planner?
Planner fits situations like: breaking down complex work into parallel and sequential tasks with dependencies.
How do I install Planner in Claude Code?
Run `npx skills add jdrhyne/agent-skills --skill planner -a claude-code`. Or copy the skill folder (skills/planner in jdrhyne/agent-skills) into .claude/skills/planner in your project. Claude Code loads it when a task matches its description.
How do I install Planner in Codex?
Run `npx skills add jdrhyne/agent-skills --skill planner -a codex`. Or copy the skill folder (skills/planner in jdrhyne/agent-skills) into .agents/skills/planner in your project. Codex loads it when a task matches its description.
Can I use Planner 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 jdrhyne/agent-skills --skill planner -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/planner, .gemini/skills/planner, .github/skills/planner and .opencode/skills/planner in your project.
What does Planner need to run?
SKILL.md names no scripts, command-line tools or credentials: Planner is instructions for the agent only.
Does Planner 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 Planner 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 Planner use?
Planner 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 Planner use?
About 956 tokens (SKILL.md is roughly 3.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 Planner?
Skills that share tags, products or a category with Planner: MCP Server Builder (anthropics/skills, 180k stars), Hook Development for Claude Code Plugins (anthropics/claude-plugins-official, 38k stars), Using Superpowers (farm-fe/farm, 5.6k stars) and Executing Plans Inline (obra/superpowers, 297k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Planner?
jdrhyne (a GitHub user) maintains it in jdrhyne/agent-skills, which has 240 GitHub stars. The repository holds 20 skills in this directory. The repository was last updated on August 30, 2026.
Source: jdrhyne/agent-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.