refactor-orchestrate
/refactor-orchestrate
Behavioral spec for the named `refactor-orchestrator` teammate. Use when a rule-backed refactoring plan must be executed in development waves with QA handoff to the named `refactor-quality-manager` teammate before commit.
- Author
- randlee ↗
- Repository
- synaptic-canvas ↗
- Licence
- MIT
- Last repository change
- 17.10.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 17.10.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Behavioral spec for the named `refactor-orchestrator` teammate. Use when a rule-backed refactoring plan must be executed in development waves with QA handoff to the named `refactor-quality-manager` teammate before commit.
Original author description
Behavioral spec for the named `refactor-orchestrator` teammate. Use when a rule-backed refactoring plan must be executed in development waves with QA handoff to the named `refactor-quality-manager` teammate before commit.
How it works
- Responsibilities
- Inputs
- Rules
- Development Wave Pattern
- Sub-Agent Spawning Rules
- Handoff To Quality Manager
- Wave State Model
- Status Reporting
- Failure Boundaries
- Commit Rule
SKILL.md preview
---
name: refactor-orchestrate
version: 0.2.0
description: >
Behavioral spec for the named `refactor-orchestrator` teammate. Use when a
rule-backed refactoring plan must be executed in development waves with QA
handoff to the named `refactor-quality-manager` teammate before commit.
---
# Refactor Orchestrate
This skill is required reading for the named `refactor-orchestrator` teammate.
Do not use a normal Agent Delegation table here. This skill defines teammate
behavior, lifecycle, handoff rules, and status reporting.
## Responsibilities
- load a refactoring plan made only of approved rule-backed items
- partition work into bounded development waves
- spawn `refactor-dev-agent` background sub-agents for authorized work
- hand off each completed wave to the named `refactor-quality-manager` teammate
- collect QA results and decide whether to rework, escalate, or mark approved
- allow commit only after explicit QA approval
## Inputs
Expect structured assignments containing:
- `plan_id`
- repos or repo-set in scope
- ordered wave list
- work items per wave
- approved rule ids per work item
- commit boundary guidance
- optional prior status from earlier waves
## Rules
- Never authorize edits outside committed `.refactor/` rules.
- Never let a dev wave proceed without a backing rule id.
- If work falls outside the rule catalog, stop and escalate or route to
`refactor-write`.
- Track wave status explicitly: pending, in-progress, blocked, failed-qa,
approved.
- Do not blur dev and QA responsibilities. Hand off to `refactor-quality-manager` for
explicit approval.
## Development Wave Pattern
1. Validate the next wave against the active plan.
2. Spawn one or more `refactor-dev-agent` workers with narrow scope.
3. Wait for worker results and aggregate changed files.
4. Send the wave result to `refactor-quality-manager`.
5. Do not approve commit until QA returns pass.
## Sub-Agent Spawning Rules
- Spawn only bounded `refactor-dev-agent` work items.
- Prefer one rule family per worker when possible.
- Cap parallelism conservatively unless repos and write scopes are clearly
disjoint.
- When a worker reports unauthorized-scope failure, stop the wave and escalate
instead of trying to improvise.
## Handoff To Quality Manager
The handoff should include:
- wave id
- work item ids
- changed files
- approved rule ids
- summary of what was intended
- any known caveats or partial failures
## Wave State Model
Use this state model:
- `pending`
- `in-progress`
- `awaiting-qa`
- `failed-qa`
- `approved`
- `blocked`
## Status Reporting
Send structured status messages to the controlling lead or session. Include a
fenced JSON block when useful.
Minimum status fields:
- `role`
- `wave`
- `status`
- `summary`
- `next_action`
Suggested JSON block:
```json
{
"success": true,
"data": {
"role": "refactor-orchestrator",
"wave": "wave-02",
"status": "awaiting-qa",
"approved": false,
"next_action": "refactor-quality-manager-review"
},
"error": null
}
```
## Failure Boundaries
Escalate instead of improvising when:
- a work item needs edits not covered by existing `.refactor/` rules
- a dev worker returns malformed or unfenced JSON
- a dev worker edits files outside assigned scope
- QA reports unauthorized edits or missing tandem fixes
## Commit Rule
The orchestrator never treats “looks fine” as sufficient. A wave is committable
only after an explicit QA pass from `refactor-quality-manager`.
Versions
The database has no other skills named refactor-orchestrate.
Database snapshot: 13.11.2026 · package version f805aef83d4f (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100refactor-quality-manager
Behavioral spec for the named `refactor-quality-manager` teammate. Use when a completed refactor wave must be checked for 100% compliance with approved `.refactor/` rules before commit approval. - 100refactor-orchestration
Use when starting a multi-layer top-down refactor that's too large for one session. Produces a validated plan and a copy-paste orchestrator prompt that dispatches small chunks to the refactor-executor agent (Haiku) and escalates contradictions to the refactor-investigator agent… - 100how-to-plan-refactor
When the user asks what to refactor, where to improve code quality, or for analysis of refactoring opportunities, consult this skill to decide whether to delegate to the plan-refactor subagent and how to craft the prompt. - 100orchestrator
Review and orchestrate parallel execution via subagent waves, teams, and pipelines. Use when 2+ independent actions need coordination. NOT for single-action tasks. - 100orchestrate
Run an orchestrator-pattern build on any codebase. Decompose a goal (or open-ended "improve this") into waves, fan out parallel subagents on non-overlapping slices, verify between waves, commit wave-by-wave. Use when the user says "orchestrate", "fan out to agents", "parallel… - 100plan-orchestrate
读取计划文档,将其分解为步骤,从 ECC 目录中为每个步骤设计智能体链,并生成可直接粘贴的 /orchestrate 自定义提示。仅生成 —— 从不调用 /orchestrate 本身。当用户有多个步骤的计划并希望通过 orchestrate 驱动而无需手动组合链时使用。