Christian Nennemann
f7f3c84b41
- check-phase: 831 → 204 words (remove protocol duplication with agents) - plan-phase: 521 → 143 words (keep output formats, drop behavioral text) - do-phase: 408 → 113 words (keep output format + critical commit rule) - Total plugin: 9830 → 8269 words (~2000 tokens saved)
993 B
993 B
name, description
| name | description |
|---|---|
| plan-phase | 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
## 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
## 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>