# Plan Implementation

> Create implementation plans for features and changes. Use when user says "plan how to implement user authentication", "how should I add dark mode to the app", "what's the best way to refactor the database layer", "create a plan for migrating to the new API", or "I need to implement [feature] - help me plan it out".

- Skill: `uniswap/plan-implementation` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add uniswap/plan-implementation`
- Raw SKILL.md: https://api.skillmd.com/api/skills/uniswap/plan-implementation/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Integrations & APIs
- Author: uniswap (https://skillmd.com/u/uniswap)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/uniswap/plan-implementation

---


# Implementation Planner

Create clear, actionable implementation plans through collaborative multi-agent discussion and refinement.

## When to Activate

- User wants to implement a new feature
- User asks "how should I implement X?"
- User wants to add functionality
- User needs to refactor or migrate code
- Complex bug fixes requiring planning
- Architectural changes or design decisions
- Any task that benefits from structured planning

## Quick Process

1. **Analyze Context**: Understand the task, leverage any prior exploration
2. **Select Agents**: Choose specialists for the dimensions the task actually raises, up to 10
3. **Collaborative Discussion**: Multi-agent refinement, up to the round ceiling in the table below
4. **Synthesize Plan**: Generate comprehensive implementation plan
5. **Output File**: Write plan to `.claude-output/plan-[timestamp].md`

## Complexity-Based Planning

Agent and round counts are **ceilings, not quotas**. Staff only the dimensions the task actually raises, and do not spawn an agent for analysis that would finish in a handful of direct tool calls - plan the simple case yourself.

| Task Type                              | Agents (max) | Rounds (max) | Plan Length    |
| -------------------------------------- | ------------ | ------------ | -------------- |
| Simple (bug fix, minor feature)        | up to 2      | 1            | ~100-200 lines |
| Medium (features, refactors)           | up to 5      | 2            | ~200-400 lines |
| Complex (architecture, major features) | up to 10     | 3            | ~400-600 lines |

## Plan Structure

Generated plans include:

1. **Overview** - High-level summary
2. **Scope** - What will/won't be implemented
3. **Current State** - Relevant architecture and files
4. **API Design** (optional) - Interfaces and data structures
5. **Implementation Steps** - Clear sequential steps (5-7 typical)
6. **Files Summary** - Files to create/modify
7. **Critical Challenges** (optional) - Risks and mitigations
8. **Agent Collaboration Summary** - Consensus and trade-offs

## Workflow Integration

This is **Step 2** of the implementation workflow:

1. Explore → 2. **Plan** (this) → 3. Review → 4. Execute

- Automatically uses context from prior exploration
- Output plan can be reviewed with `/review-plan`
- Approved plans execute with `execute-plan` skill

## Detailed Reference

For agent selection, discussion protocols, and output formats, see [planning-guide.md](planning-guide.md).