planning
Transform ideas into actionable implementation plans. Combines Socratic questioning for requirements discovery with detailed task breakdown for zero-context engineers. Use before any feature development.
Best use case
planning is best used when you need a repeatable AI agent workflow instead of a one-off prompt. It is especially useful for teams working in multi. Transform ideas into actionable implementation plans. Combines Socratic questioning for requirements discovery with detailed task breakdown for zero-context engineers. Use before any feature development.
Transform ideas into actionable implementation plans. Combines Socratic questioning for requirements discovery with detailed task breakdown for zero-context engineers. Use before any feature development.
Users should expect a more consistent workflow output, faster repeated execution, and less time spent rewriting prompts from scratch.
Practical example
Example input
Use the "planning" skill to help with this workflow task. Context: Transform ideas into actionable implementation plans. Combines Socratic questioning for requirements discovery with detailed task breakdown for zero-context engineers. Use before any feature development.
Example output
A structured workflow result with clearer steps, more consistent formatting, and an output that is easier to reuse in the next run.
When to use this skill
- Use this skill when you want a reusable workflow rather than writing the same prompt again and again.
When not to use this skill
- Do not use this when you only need a one-off answer and do not need a reusable workflow.
- Do not use it if you cannot install or maintain the related files, repository context, or supporting tools.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/planning/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How planning Compares
| Feature / Agent | planning | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Transform ideas into actionable implementation plans. Combines Socratic questioning for requirements discovery with detailed task breakdown for zero-context engineers. Use before any feature development.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
Related Guides
AI Agent for Product Research
Browse AI agent skills for product research, competitive analysis, customer discovery, and structured product decision support.
Top AI Agents for Productivity
See the top AI agent skills for productivity, workflow automation, operational systems, documentation, and everyday task execution.
SKILL.md Source
# Planning
아이디어를 구체적인 구현 계획으로 발전시키는 통합 스킬입니다.
## Phase 1: Discovery (Brainstorming)
### Socratic Process
```
1. 핵심 목표 파악
- "이것이 해결하려는 문제가 무엇인가요?"
- "성공을 어떻게 측정할 수 있나요?"
2. 제약 조건 탐색
- "반드시 지켜야 할 제약이 있나요?"
- "기술적/비즈니스적 한계는?"
3. 대안 탐색
- 최소 3가지 접근법 도출
- 각 접근법의 장단점 분석
```
### Output: Discovery Summary
```markdown
## Discovery Summary
### 핵심 요구사항
- [필수 요구사항 목록]
### 기술적 결정사항
- [합의된 접근법]
### 열린 질문
- [추가 탐색 필요 항목]
```
---
## Phase 2: Plan Writing
### Core Principle
> **"가정: 엔지니어가 코드베이스 컨텍스트가 전혀 없음"**
### Plan Structure
```markdown
# [Feature Name] Implementation Plan
## Goal
[한 문장 목표]
## Tech Stack
- Framework: [프레임워크]
- Dependencies: [의존성]
## File Structure
[영향받는 파일 목록]
```
### Bite-sized Tasks (각 2-5분)
```markdown
## Task 1: [태스크명]
### Files
- `src/feature/file.ts` (신규/수정)
### Test First
[테스트 코드]
### Implementation
[구현 코드]
### Commit
```bash
git commit -m "feat(scope): description"
```
```
---
## Workflow
```
Discovery → Plan → Execute
┌────────────────┐
│ Brainstorm │ ← 요구사항 도출
└───────┬────────┘
▼
┌────────────────┐
│ Write Plan │ ← 태스크 분해
└───────┬────────┘
▼
┌────────────────┐
│ Execute │ ← TDD 사이클
└────────────────┘
```
## Plan Storage
```
docs/plans/YYYY-MM-DD-<feature-name>.md
```
## Checklist
### Discovery 완료
- [ ] 핵심 목표 명확
- [ ] 제약 조건 파악
- [ ] 접근법 결정
### Plan 완료
- [ ] 모든 파일 경로 정확
- [ ] 각 태스크 2-5분 분량
- [ ] 테스트 코드 포함
- [ ] 커밋 메시지 작성됨Related Skills
task-planning
Plan and organize software development tasks effectively. Use when breaking down features, creating user stories, or planning sprints. Handles task breakdown, user stories, acceptance criteria, and backlog management.
concise-planning
Use when a user asks for a plan for a coding task, to generate a clear, actionable, and atomic checklist.
agile-planning
Generate agile release plans with sprints and roadmaps using unique sprint codes. Use when creating sprint schedules, product roadmaps, release planning, or when user mentions agile planning, sprints, roadmap, or release plans.
research-driven-planning
Loop 1 of the Three-Loop Integrated Development System. Research-driven requirements analysis with iterative risk mitigation through 5x pre-mortem cycles using multi-agent consensus. Feeds validated, risk-mitigated plans to parallel-swarm-implementation. Use when starting new features or projects requiring comprehensive planning with <3% failure confidence and evidence-based technology selection.
planning-workflow
Jeffrey Emanuel's comprehensive markdown planning methodology for software projects. The 85%+ time-on-planning approach that makes agentic coding work at scale. Includes exact prompts used.
planning-the-escape
逃离计划 - 最终章,Stella必须决定是否修复飞船返回地球,还是留在盖亚,这是艰难的抉择
planning-sprints
Automatically activated when user mentions sprint planning, backlog refinement, iteration planning, sprint goals, capacity planning, velocity tracking, or asks to plan/start/close a sprint. Provides comprehensive sprint planning expertise using agile best practices.
project-planning
Generate initial project planning documents (PVS, ADR, Tech Spec, Roadmap) from a project concept description. Use when starting a new project, when docs/planning/ contains placeholder files, or when user requests project planning document generation.
planning-with-trello
Use when planning features, organizing sprints, or syncing work with Trello boards.
planning-action
Use when the user asks for a roadmap, timeline, phased plan, or execution sequence.
roadmap-planning-expert
When the user asks about roadmap planning, sprint planning, milestone estimation, or capacity planning
planning-with-files
Transforms workflow to use Manus-style persistent markdown files for planning, progress tracking, and knowledge storage. Use when starting complex tasks, multi-step projects, research tasks, or when the user mentions planning, organizing work, tracking progress, or wants structured output.