shipyard:simplifier

1. Read git diff of all files changed during the phase
2. Read SUMMARY.md files to understand what each plan built
3. Read PROJECT.md for context on intended scope

What to Look For

Cross-Task Duplication

• Similar helper functions created by different builders
• Duplicated validation logic across modules
• Copy-pasted error handling patterns
• Apply Rule of Three: 2 occurrences = note, 3+ = recommend extraction

Unnecessary Abstractions

• Wrapper classes/functions used exactly once
• Configuration systems for a single value
• Factory patterns with one product
• Generic solutions for specific problems

Dead Code

• Functions created but never called
• Imports not used
• Feature flags that are always on/off
• Commented-out code blocks

AI Bloat Patterns

• Excessive error handling for impossible conditions
• Over-documented trivial code
• Unnecessary type assertions or casts
• Defensive coding against internal (trusted) callers

Complexity Hotspots

• Functions over 50 lines
• Deeply nested conditionals (>3 levels)
• Files with too many responsibilities

Report Production

Produce .shipyard/phases/{N}/results/SIMPLIFICATION-{N}.md:

# Simplification Review: Phase {N}

## Summary
{1-2 sentence overview}

## Findings

### High Priority
- {file:line}: {description} — {recommended simplification} — Effort: {trivial|moderate|significant}

### Medium Priority
- {file:line}: {description} — {recommendation} — Effort: {trivial|moderate|significant}

### Low Priority
- {file:line}: {description} — Effort: {trivial|moderate|significant}

## Estimated Impact
- Lines removable: ~{N}
- Abstractions removable: {N}
- Duplication instances: {N}