orchestrate-batch-refactor
Plan and execute large refactor efforts with parallel multi-agent analysis. Use when: refactoring many files, splitting workstreams, or coordinating sub-agents for batch code changes.
What this skill does
# Orchestrate Batch Refactor ## Overview Use this skill to run high-throughput refactors safely. Analyze scope in parallel, synthesize a single plan, then execute independent work packets with sub-agents. ## Inputs - Repo path and target scope (paths, modules, or feature area) - Goal type: refactor, rewrite, or hybrid - Constraints: behavior parity, API stability, deadlines, test requirements ## When to Use Parallelization - Use this skill for medium/large scope touching many files or subsystems. - Skip multi-agent execution for tiny edits or highly coupled single-file work. ## Core Workflow 1. Define scope and success criteria. - List target paths/modules and non-goals. - State behavior constraints (for example: preserve external behavior). 2. Run parallel analysis first. - Split target scope into analysis lanes. - Spawn `explorer` sub-agents in parallel to analyze each lane. - Ask each agent for: intent map, coupling risks, candidate work packets, required validations. 3. Build one dependency-aware plan. - Merge explorer output into a single work graph. - Create work packets with clear file ownership and validation commands. - Sequence packets by dependency level; run only independent packets in parallel. 4. Execute with worker agents. - Spawn one `worker` per independent packet. - Assign explicit ownership (files/responsibility). - Instruct every worker that they are not alone in the codebase and must ignore unrelated edits. 5. Integrate and verify. - Review packet outputs, resolve overlaps, and run validation gates. - Run targeted tests per packet, then broader suite for integrated scope. 6. Report and close. - Summarize packet outcomes, key refactors, conflicts resolved, and residual risks. ## Work Packet Rules - One owner per file per execution wave. - No parallel edits on overlapping file sets. - Keep packet goals narrow and measurable. - Include explicit done criteria and required checks. - Prefer behavior-preserving refactors unless user explicitly requests behavior change. ## Planning Contract Every packet must include: 1. Packet ID and objective. 2. Owned files. 3. Dependencies (none or packet IDs). 4. Risks and invariants to preserve. 5. Required checks. 6. Integration notes for main thread. Use [`references/work-packet-template.md`](references/work-packet-template.md) for the exact shape. ## Agent Prompting Contract - Use the prompt templates in [`references/agent-prompt-templates.md`](references/agent-prompt-templates.md). - Explorer prompts focus on analysis and decomposition. - Worker prompts focus on implementation and validation with strict ownership boundaries. ## Safety Guardrails - Do not start worker execution before plan synthesis is complete. - Do not parallelize across unresolved dependencies. - Do not claim completion if any required packet check fails. - Stop and re-plan when packet boundaries cause repeated merge conflicts. ## Validation Strategy Run in this order: 1. Packet-level checks (fast and scoped). 2. Cross-packet integration checks. 3. Full project safety checks when scope is broad. Prefer fast feedback loops, but never skip required behavior checks.
Related in AI Agents
skill-development
IncludedComprehensive meta-skill for creating, managing, validating, auditing, and distributing Claude Code skills and slash commands (unified in v2.1.3+). Provides skill templates, creation workflows, validation patterns, audit checklists, naming conventions, YAML frontmatter guidance, progressive disclosure examples, and best practices lookup. Use when creating new skills, validating existing skills, auditing skill quality, understanding skill architecture, needing skill templates, learning about YAML frontmatter requirements, progressive disclosure patterns, tool restrictions (allowed-tools), skill composition, skill naming conventions, troubleshooting skill activation issues, creating custom slash commands, configuring command frontmatter, using command arguments ($ARGUMENTS, $1, $2), bash execution in commands, file references in commands, command namespacing, plugin commands, MCP slash commands, Skill tool configuration, or deciding between skills vs slash commands. Delegates to docs-management skill for official documentation.
reprompter
IncludedTransform messy prompts into well-structured, effective prompts — single or multi-agent. Use when: "reprompt", "reprompt this", "clean up this prompt", "structure my prompt", rough text needing XML tags and best practices, "reprompter teams", "repromptception", "run with quality", "smart run", "smart agents", multi-agent tasks, audits, parallel work, anything going to agent teams. Don't use when: simple Q&A, pure chat, immediate execution-only tasks. See "Don't Use When" section for details. Outputs: Structured XML/Markdown prompt, quality score (before/after), optional team brief + per-agent sub-prompts, agent team output files. Success criteria: Single mode quality score ≥ 7/10; Repromptception per-agent prompt quality score 8+/10; all required sections present, actionable and specific.
adaptive-compaction
IncludedAdaptive add-on policy and recovery layer that decides WHEN to compact, prune, snapshot, or fork -- replacing fixed-percent auto-compaction across Claude Code, Codex, and MCP-capable hosts. Trigger on auto-compact timing or damage: "when should I compact", "is it safe to compact now or start a fresh session", "auto-compact fires too early/mid-task", "switching to an unrelated task but the window still has space", "context rot", "answers get worse the longer the session runs", "the agent forgot the plan or my decisions after it summarized", "add a layer on top that manages context without changing the agent", raising autoCompactWindow to give the policy room, or installing/tuning a cross-tool compaction policy or PreCompact hook -- even when "compaction" is never said but the problem is context-window pressure or post-summarization memory loss. Do NOT use to summarize a conversation, build RAG, write a summarization prompt (decides WHEN not HOW), or answer max-context-length trivia.
agent-skill-creator
IncludedCreate cross-platform agent skills from workflow descriptions. Activates when users ask to create an agent, automate a repetitive workflow, create a custom skill, or need advanced agent creation. Triggers on phrases like create agent for, automate workflow, create skill for, every day I have to, daily I need to, turn process into agent, need to automate, create a cross-platform skill, validate this skill, export this skill, migrate this skill. Supports single skills, multi-agent suites, transcript processing, template-based creation, interactive configuration, cross-platform export, and spec validation.
llm-wiki
IncludedUse when building or maintaining a persistent personal knowledge base (second brain) in Obsidian where an LLM incrementally ingests sources, updates entity/concept pages, maintains cross-references, and keeps a synthesis current. Triggers include "second brain", "Obsidian wiki", "personal knowledge management", "ingest this paper/article/book", "build a research wiki", "compound knowledge", "Memex", or whenever the user wants knowledge to accumulate across sessions instead of being re-derived by RAG on every query.
skill-master
IncludedAgent Skills authoring, evaluation, and optimization. Create, edit, validate, benchmark, and improve skills following the agentskills.io specification. Use when designing SKILL.md files, structuring skill folders (references, scripts, assets), ingesting external documentation into skills, running trigger evals, benchmarking skill quality, optimizing descriptions, or performing blind A/B comparisons. Keywords: agentskills.io, SKILL.md, skill authoring, eval, benchmark, trigger optimization.