amq-squad
Compatibility intent router for the amq-squad plugin. Routes goal preparation to wizard, direct operations to cli, and live lead work to orchestrator.
- License 许可
- MIT
- 最近更新
- 2026-11-11
- Stars
- ★ 8
- Forks
- 1
01 前言 Front Matter
- name
- amq-squad
- description
- Compatibility intent router for the amq-squad plugin. Routes goal preparation to wizard, direct operations to cli, and live lead work to orchestrator.
02 资源文件 1
- 参考文档references/team-rules-template.md7.2 KB
03 SKILL.md 正文
amq-squad compatibility router
This legacy skill name remains for compatibility. Route the request to one authoritative namespaced skill and follow that skill completely:
- Goal intake, roster and custom roles, the squad.yaml digest flow
(
team propose,team apply), the brief, or the launch:amq-squad:wizard. - Status, doctor, task, evidence, guard, gate status, AMQ context, or merge and
release verification:
amq-squad:cli. - The lead seat of a launched squad planning tasks, dispatching, widening, running
the merge train, raising gates or preparing a release:
amq-squad:orchestrator.
Do not run setup, direct operations, and the live lead loop from this router. Existing invocations keep working only as compatibility routing; authoritative behavior and future changes live in the three namespaced skills.
amq-squad 3.0 removed the v2 lifecycle verbs (start, resume, down, send,
init, wizard). A request phrased in those terms routes by intent: "start the
team" is a launch (amq-squad:wizard), "who is up" is status (amq-squad:cli).
Disposable review worktrees follow the canonical workspace rules: create them at an
explicit temporary path with git worktree add --detach, and clean up that exact path
with git worktree remove --force. This does not authorize raw recursive deletion.
04 同仓库更多 Skills
wizard
Goal-first squad setup and launch for amq-squad 3.0 through the squad.yaml digest flow. Use when creating a squad for a repository, writing the workstream brief, previewing the files a squad needs, approving that exact digest, or launching the seats. Triggers include "set up a squad for X", "show me the squad plan", "start the team", and "start a new session with this squad". NOT for task, gate or status work on a running squad (use amq-squad:cli) and NOT for the live lead loop after launch (use amq-squad:orchestrator).
orchestrator
Live amq-squad 3.0 lead protocol after the squad is launched. Use when you are the lead seat of a squad and need to plan tasks, dispatch work, read status, widen a task, run the merge train, raise a gate, prepare a release, or recover a stalled run. Triggers include "watch the squad", "what should I do next", "dispatch this task", "the run is stuck", "who is blocked". NOT for preparing or launching a squad (use amq-squad:wizard) or for one-off status and inspection commands (use amq-squad:cli).
cli
Direct amq-squad 3.0 operations and diagnostics against an existing squad. Use when you need to inspect state, claim or complete a task, read the evidence ledger, check a guard verdict, read the AMQ context, raise or check a gate, check the host, or verify merge and release evidence. Triggers include "what is the status", "claim this task", "show my evidence", "is this tool call allowed", "where does this route", "is this safe to merge". NOT for preparing or launching a squad (use amq-squad:wizard) and NOT for the live lead loop (use amq-squad:orchestrator).
amq-team-setup
Deprecated redirect for the former setup wizard skill. Use amq-squad:wizard.
amq-squad-role-creator
Deprecated redirect for the former custom role authoring skill. Use amq-squad:wizard.
amq-squad-orchestrator
Deprecated compatibility redirect for the live lead skill. Use amq-squad:orchestrator.