name: planner description: A skill that creates a plan document in plan.md based on requests. Use when the user says things like "create a plan", "make a plan.md", "project plan", "implementation plan", etc. Generates a comprehensive plan including objectives, scope, task breakdown, dependencies, risks, and milestones.

Planner

Analyze the request and create plan.md in the current directory.

Plan Creation Workflow

1. Request Analysis

Extract the following from the user's request:

• The goal to achieve
• Constraints
• Existing codebase/context (if any)

2. Creating plan.md

Create plan.md with the following structure:

# Plan: [Title]

## Objective
[What this project/task aims to achieve]

## Scope
### Included
- [Features/work to implement]

### Excluded
- [Items out of scope for this iteration]

## Task Breakdown

### Phase 1: [Phase Name]
- [ ] Task 1.1: [Description]
- [ ] Task 1.2: [Description]

### Phase 2: [Phase Name]
- [ ] Task 2.1: [Description]
  - Depends on: Task 1.1
- [ ] Task 2.2: [Description]

## Dependencies
[Explicitly state dependencies between tasks]

## Risks and Mitigation
| Risk | Impact | Mitigation |
|------|--------|------------|
| [Risk 1] | High/Medium/Low | [Mitigation] |

## Milestones
| Milestone | Completion Criteria |
|-----------|---------------------|
| [MS1] | [Criteria] |

## Notes
[Other considerations]

3. Review

After creating plan.md, ask the user to review the contents.

Guidelines

• Describe tasks at a specific and actionable granularity
• Describe commands in as much detail as possible
• Clarify dependencies so the execution order is clear
• List risks that are realistically likely to occur
• Set verifiable completion criteria for milestones