planner
Create comprehensive, phased implementation plans with sprints and atomic tasks. Use when user says: "make a plan", "create a plan", "plan this out", "plan the implementation", "help me plan", "design a plan", "draft a plan", "write a plan", "outline the steps", "break this down into tasks", "what's the plan for", or any similar planning request. Also triggers on explicit "/planner" or "/plan" commands.
- License 许可
- MIT
- 最近更新
- 2026-04-11
- Stars
- ★ 3
- Forks
- 0
01 前言 Front Matter
- name
- planner
- description
- Create comprehensive, phased implementation plans with sprints and atomic tasks. Use when user says: "make a plan", "create a plan", "plan this out", "plan the implementation", "help me plan", "design a plan", "draft a plan", "write a plan", "outline the steps", "break this down into tasks", "what's the plan for", or any similar planning request. Also triggers on explicit "/planner" or "/plan" commands.
03 SKILL.md 正文
Planner Agent
Create detailed, phased implementation plans for bugs, features, or tasks.
Process
Phase 0: Research
-
Investigate the codebase:
- Architecture and patterns
- Similar existing implementations
- Dependencies and frameworks
- Related components
-
Analyze the request:
- Core requirements
- Challenges & edge cases
- Security/performance/UX considerations
Phase 1: Clarify Requirements
Before doing ANY documentation search: clarify requirements with user. This will narrow and aid you in finding the right docs.
Think of 5-10 questions that will help you generate the best plan possible.
Here are suggested example categories, but not a strict or exhaustive list. You may ask anything helpful. Use best judgement & prioritize ambiguity and risk reduction:
- Goals & success criteria
- Scope & non‑goals
- Users & core workflows
- Platforms & environments
- Tech constraints
- Data & integrations
- Auth & permissions
- Performance & reliability
- Testing & validation
- Ask any helpful question
Phase 2: Retrieve Documentation
When the plan involves any external library, API, framework, or service, use the Context7 skill to fetch the latest official docs before drafting tasks. This ensures version‑accurate steps, correct parameters, and current best practices. If no external dependencies apply, skip this phase.
Phase 3: Create Plan
Structure
- Overview: Brief summary and approach
- Sprints: Logical phases that build on each other
- Tasks: Specific, actionable items within sprints
Sprint Requirements
Each sprint must:
- Result in demoable, runnable, testable increment
- Build on prior sprint work
- Include demo/verification checklist
Task Requirements
Each task must be:
- Atomic and committable (small, independent)
- Specific with clear inputs/outputs
- Independently testable
- Include file paths when relevant
- Include dependencies for parallel execution
- Include tests or validation method
Bad: "Implement Google OAuth" Good:
- "Add Google OAuth config to env variables"
- "Install passport-google-oauth20 package"
- "Create OAuth callback route in src/routes/auth.ts"
- "Add Google sign-in button to login UI"
Phase 3: Save
Save the file
Generate filename from request:
- Extract keywords
- Convert to kebab-case
- Add
-plan.mdsuffix
Examples:
- "fix xyz bug" →
xyz-bug-plan.md
Phase 4: Gotchas
AFTER it is saved. Identify potential issues & edge cases in plan. Address proactively. Where could smth go wrong? What about the plan is ambiguous? Missing step, dependency, or pitfall?
If any gotchas found, stop & ask up to 3 more questions. (either w/ request_user_input or directly)
Refine the plan if any additional useful info is provided.
Plan Template
# Plan: [Task Name]
**Generated**: [Date]
**Estimated Complexity**: [Low/Medium/High]
## Overview
[Summary of task and approach]
## Prerequisites
- [Dependencies or requirements]
- [Tools, libraries, access needed]
## Sprint 1: [Name]
**Goal**: [What this accomplishes]
**Demo/Validation**:
- [How to run/demo]
- [What to verify]
### Task 1.1: [Name]
- **Location**: [File paths]
- **Description**: [What to do]
- **Dependencies**: [Previous tasks]
- **Acceptance Criteria**:
- [Specific criteria]
- **Validation**:
- [Tests or verification]
### Task 1.2: [Name]
[...]
## Sprint 2: [Name]
[...]
## Testing Strategy
- [How to test]
- [What to verify per sprint]
## Potential Risks & Gotchas
- [What could go wrong]
- [Mitigation strategies]
## Rollback Plan
- [How to undo if needed]
Important
- Think about full lifecycle: implementation, testing, deployment
- Consider non-functional requirements
- Show user summary and file path when done
- Do NOT implement - only create the plan
04 同仓库更多 Skills
vercel-react-best-practices
React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.
swarm-planner
[EXPLICIT INVOCATION ONLY] Creates dependency-aware implementation plans optimized for parallel multi-agent execution.
super-swarm-spark
Only to be triggered by explicit super-swarm-spark commands.
role-creator
Create and install Codex custom agent roles in ~/.codex/config.toml, generate role config files, enforce supported keys, and guide users through required role inputs (model, reasoning effort, developer_instructions).
read-github
Read and search GitHub repository documentation via gitmcp.io MCP service. **WHEN TO USE:** - User provides a GitHub URL - User mentions a specific repo in owner/repo format - User asks "what does this repo do?", "read the docs for X repo", or similar - User wants to search code or docs within a repo
planner
Create comprehensive, phased implementation plans with sprints and atomic tasks. Use when user says: "make a plan", "create a plan", "plan this out", "plan the implementation", "help me plan", "design a plan", "draft a plan", "write a plan", "outline the steps", "break this down into tasks", "what's the plan for", or any similar planning request. Also triggers on explicit "/planner" or "/plan" commands.