Topics
- Refactoring
- multi-agent
- orchestration
- parallel-execution
- code-analysis
- work-planning
- dependency-management
- scope-management
What it does
Orchestrates large refactors across multiple files by parallelizing code analysis, synthesizing a dependency-aware work plan, and executing independent work packets with separate sub-agents. Use when refactoring many files or subsystems where scope analysis, decomposition, and coordinated execution prevent conflicts and maintain behavior parity.
Generated from the current SKILL.md.
Frequently asked
When should I use this skill instead of asking a single agent to refactor multiple files?
Use this skill for medium/large scope touching many files or subsystems. Skip it for tiny edits or highly coupled single-file work where parallelization adds overhead without benefit.
Does this skill preserve existing behavior during refactors?
Yes. The skill defaults to behavior-preserving refactors unless you explicitly request behavior change. Each work packet includes invariants to preserve and required validation checks.
How does this skill handle dependencies between files being refactored?
The skill builds a dependency-aware work graph, sequences packets by dependency level, and runs only independent packets in parallel. Packets explicitly declare their dependencies so the orchestrator respects them.
What happens if two work packets edit overlapping file sets?
The skill prohibits this by design — one owner per file per execution wave. If packet boundaries cause repeated merge conflicts, the skill stops and triggers re-planning.
Do I need to provide templates or can the skill generate work packets on its own?
The skill includes reference templates in `references/work-packet-template.md` and `references/agent-prompt-templates.md`. You can use these directly or adapt them for your codebase structure.
Generated from the current SKILL.md. These answers refresh after source changes.