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.
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.
Teams using planning should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
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.
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
sprint-planning-helper
Sprint Planning Helper - Auto-activating skill for Enterprise Workflows. Triggers on: sprint planning helper, sprint planning helper Part of the Enterprise Workflows skill category.
planning-disaster-recovery
Execute use when you need to work with backup and recovery. This skill provides backup automation and disaster recovery with comprehensive guidance and automation. Trigger with phrases like "create backups", "automate backups", or "implement disaster recovery".
analyzing-capacity-planning
This skill enables Claude to analyze capacity requirements and plan for future growth. It uses the capacity-planning-analyzer plugin to assess current utilization, forecast growth trends, and recommend scaling strategies. Use this skill when the user asks to "analyze capacity", "plan for growth", "forecast infrastructure needs", or requests a "capacity roadmap". It is also useful when the user mentions specific capacity metrics like CPU usage, memory, database storage, network bandwidth, or connection pool saturation. This skill is ideal for proactive infrastructure planning and preventing performance bottlenecks.
planning-oracle-to-postgres-migration-integration-testing
Creates an integration testing plan for .NET data access artifacts during Oracle-to-PostgreSQL database migrations. Analyzes a single project to identify repositories, DAOs, and service layers that interact with the database, then produces a structured testing plan. Use when planning integration test coverage for a migrated project, identifying which data access methods need tests, or preparing for Oracle-to-PostgreSQL migration validation.
gtm-enterprise-account-planning
Strategic account planning and execution for enterprise deals. Use when planning complex sales cycles, managing multiple stakeholders, applying MEDDICC qualification, tracking deal health, or building mutual action plans. Includes the "stale MAP equals dead deal" pattern.
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.
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必须决定是否修复飞船返回地球,还是留在盖亚,这是艰难的抉择
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.