Planning Review Fixes

Hard Limits (MANDATORY)

15 issues? CHOOSE THE 5 THAT MATTER.

Finding Categories

Classify each finding BEFORE planning:

Waste Pattern Detection:

• "Add validation for..." → Delete the code path
• "Add error handling for..." → Simplify so errors can't happen
• "Add tests for edge cases..." → Remove the edge cases
• "Refactor for readability..." → Delete the abstraction

3-Phase Process

Phase 1: Parse and Filter

For EACH finding:

1. "Would deleting the code be better than fixing it?"
2. "Is this pointing at a waste pattern?"
3. "What real bug slips through if we ignore this?"

Classify as DELETE / SIMPLIFY / FIX / SKIP.

Phase 2: Group and Size

Split if >2hr. Combine if <30min.

Phase 3: Task Specification

### Task: {Title}
**Type:** DELETE | SIMPLIFY | FIX
**Files:** file:line, file:line
**What:** One sentence
**Why:** Bug prevented OR waste removed
**Criteria (max 3):**
- [ ] Criterion 1
- [ ] Criterion 2
- [ ] Tests pass

Output Format

After generating task specifications, output in spec YAML format for ft epic decompose:

# Review Fix Plan: {epic}

## Summary
- Total findings: N
- DELETE: X | SIMPLIFY: Y | FIX: Z | SKIP: W

## Tasks (max 5)

### 1. {Title} [DELETE|SIMPLIFY|FIX]
**Files:** file:line
**What:** One sentence
**Why:** Bug prevented OR waste removed
**Criteria:**
- [ ] ...

Find the Stupid

Converted and distributed by TomeVault — claim your Tome and manage your conversions.