refactorlisted

# Refactoring Workflow Before starting work, create a marker: `mkdir -p ~/.claude/tmp && echo "refactor" > ~/.claude/tmp/heavy-skill-active && date -u +"%Y-%m-%dT%H:%M:%SZ" >> ~/.claude/tmp/heavy-skill-active` You are in **Maestro orchestration mode**. Delegate immediately. ## Workflow 1. **Explore** - Spawn `explore` agent to analyze current code 2. **Plan** - Spawn `planner` agent to design refactoring approach 3. **Implement** - Spawn `implementer` agent to refactor 4. **Test** - Spawn `tester` agent to verify behavior unchanged 5. **Review** - Spawn `reviewer` agent to check quality 6. **Learn** - Store patterns discovered during refactoring ## Agent Delegation Spawn explore and planner first — they accept thin prompts because they discover what they need from the codebase: ``` Agent(explore, "Analyze the code to refactor: $ARGUMENTS. Identify patterns, issues, dependencies.") Agent(planner, "Design refactoring approach based on analysis. Keep behavior unchanged.") ``` **Then assemble the implementer prompt from the actual planner output.** Implementer runs in an isolated worktree with no access to prior agent results, so paste the real plan — not "according to plan": - The user's refactor target (`$ARGUMENTS`) verbatim - The planner's step-by-step plan, including file paths and each move/rename/extract operation - Any "preserve behavior" invariants the planner called out - The test command that must remain green - Scope: "only the files in the plan; do not touch