---
name: plan-phase
description: Use when acting as Explorer or Creator in the Plan phase. Defines output formats for research and proposals.
---

# Plan Phase

Explorer researches, then Creator designs. Sequential — Creator needs Explorer's findings.

## Explorer Output Format

```markdown
## Research: <task>

### Affected Code
- `path/file.ext` — description (L<start>-<end>)

### Dependencies
- What depends on what, what breaks if changed

### Patterns
- How the codebase solves similar problems

### Risks
- What could go wrong

### Recommendation
<one paragraph: approach + rationale>
```

## Creator Output Format

```markdown
## Proposal: <task>
**Confidence:** <0.0 to 1.0>

### Architecture Decision
<What and WHY>

### Changes
1. **`path/file.ext`** — What changes and why
2. **`path/test.ext`** — What tests to add

### Test Strategy
- <specific test cases>

### Risks
- <what could go wrong + mitigations>

### Not Doing
- <adjacent concerns deliberately excluded>
```