plan
Installation
SKILL.md
Create Implementation Plan
Create an implementation plan for $ARGUMENTS.
Planning Process
1. Requirements Analysis
First clarify:
- Purpose: What to achieve
- Scope: What to include, what to exclude
- Constraints: Technical, time, dependencies
2. Current State Investigation
Investigate the codebase:
- Related existing code
- Files affected
- Libraries/patterns to use
- Existing tests
3. Break Down Implementation Steps
Break into small steps:
- Each step is independently testable
- Consider dependency order
- High-risk steps first
4. Output Format
## Implementation Plan: {Title}
### Purpose
{1-2 sentences}
### Scope
- New files: {list}
- Modified files: {list}
- Dependencies: {list}
### Implementation Steps
#### Step 1: {Title}
- [ ] {Specific task}
- [ ] {Specific task}
**Verification**: {Completion criteria for this step}
#### Step 2: {Title}
...
### Risks & Considerations
- {Potential issues and mitigations}
### Open Questions
- {Items to clarify before implementation}
Notes
- Plans should be at actionable granularity
- Include verification method for each step
- Ask questions at planning stage for unclear points
- Don't over-detail (adjust during implementation)
Related skills
More from del-taiseiozaki/claude-code-orchestra
update-design
Explicitly update DESIGN.md with decisions from the current conversation. Use when you want to force a design document update.
15context-loader
ALWAYS activate this skill at the start of every task. Load project context from .claude/ directory including coding rules, design decisions, and documentation before executing any task.
15simplify
Simplify and refactor code while preserving functionality and library constraints.
13codex-system
|
13init
Analyze project structure and update AGENTS.md with detected tech stack, commands, and configurations.
12update-lib-docs
Update library documentation in .claude/docs/libraries/ with latest information from web search.
12