Implement Refactor

Restructure code without changing user-facing behavior.

When to Use

• Code cleanup
• Reducing tech debt
• Improving maintainability
• Extracting shared patterns

Artifacts

• task.md updated via task_boundary

Approach

Phase 1: Scope Definition

1. Refactoring Goal: Specific code smell or tech debt
2. Behavior Invariants: List behaviors that MUST NOT change
3. Scope Boundaries: In-scope vs out-of-scope files