with one click
refactoring-team
// Iterative code refactoring through progressive lenses via a worker-reviewer agent team.
// Iterative code refactoring through progressive lenses via a worker-reviewer agent team.
Presents a proposed approach in progressive confirmable chunks with recommended decisions and alternatives. Use when aligning on a design, plan, or technical approach before implementation.
Launches agent teams with structured roles and task decomposition. Use when asked to create a team, spawn teammates, or coordinate multiple agents in parallel.
Drive feature development using Outside-In TDD with Hexagonal Architecture. Design emerges through inline code, in-memory fakes, interface extraction, and deferred I/O. Use when building features, writing tests, or structuring backend services. Triggers on: TDD, outside-in, hexagonal, ports and adapters, emergent design, acceptance test, component test, walking skeleton, in-memory fakes, component, contract test, adapter, fast tests, sub-second feedback. Language-agnostic (Go, Rust, Python, TypeScript, Java, C#).
Writes Claude Code status line scripts. Use when creating, customizing, or debugging statusline configurations.
Creates process files - text as code instructions for reliable AI workflows. Use when creating new process files.
Designs systems using Event Modeling.
| name | refactoring-team |
| description | Iterative code refactoring through progressive lenses via a worker-reviewer agent team. |
| disable-model-invocation | true |
| argument-hint | [target-path] |
| hooks | {"TeammateIdle":[{"hooks":[{"type":"command","command":"${CLAUDE_SKILL_DIR}/references/guard-idle-worker.sh"}]}]} |
STARTER_CHARACTER = 💎
Agent teams must be enabled in settings:
{
"env": {
"CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS": "1"
}
}
If not set, offer to add it before proceeding.
If $ARGUMENTS provided, use as target path. Otherwise ask for:
Verify the target path exists and tests pass before proceeding.
Generate a short random ID: head -c 3 /dev/urandom | xxd -p | head -c 3
Use it to name the teammates:
worker-ID (e.g. worker-a3f)reviewer-ID (e.g. reviewer-a3f)Read the spawn prompts:
Before spawning, replace these placeholders in both prompts:
TARGET_PATH → actual target pathTEST_COMMAND → actual test commandLENSES_DIR → ${CLAUDE_SKILL_DIR}/references/lensesGUIDES_DIR → ${CLAUDE_SKILL_DIR}/references/reviewer-guidesWORKER_NAME → the worker's name (e.g. worker-a3f)REVIEWER_NAME → the reviewer's name (e.g. reviewer-a3f)Tell the user:
teammateMode: "tmux" in settingsWhen a worker goes idle, read .refactoring-state to check the lens number. If it skipped a value, message the reviewer to go back and complete the skipped lens first.