amq-spec
Use two agents to research a design independently and converge on one specification through AMQ. Trigger for collaborative design or messages labeled workflow:spec; use amq-cli for ordinary coordination.
- License 许可
- Apache-2.0
- 最近更新
- 2026-11-14
- Stars
- ★ 1.6k
- Forks
- 491
01 前言 Front Matter
- name
- amq-spec
- version
- 0.143.0
- metadata
- { "compatibility": "claude-code, codex-cli", "short-description": "Multi-agent collaborative spec workflow" }
- description
- Use two agents to research a design independently and converge on one specification through AMQ. Trigger for collaborative design or messages labeled workflow:spec; use amq-cli for ordinary coordination.
- argument-hint
- <description of what to design> [with <partner>]
02 资源文件 1
- 参考文档references/spec-workflow.md5.8 KB
03 SKILL.md 正文
AMQ collaborative specification
Two agents research a design problem independently, discuss it, and converge on one plan. The user approves the plan before anyone implements it.
Phases run in order:
Research -> Discuss -> Draft -> Review -> Present -> Execute
Per-phase commands and the research and plan templates are in the spec workflow.
Parse input
From the user prompt, extract:
- topic: short kebab-case spec name (e.g.,
auth-token-rotation) - partner: partner agent handle (default:
codex) - problem: the full design problem statement
If topic/problem are unclear, ask for clarification.
Pre-flight
- Verify AMQ is available:
which amq - Verify the AMQ root is discoverable (
.amqrc, AMQ env vars, or the default.agent-maillayout); otherwise run:amq coop init - Use thread name:
spec/<topic>
Kickoff
Send the problem to the partner first, then start your own research. Both agents then research in parallel. Send the user's problem verbatim; your own analysis belongs in your research message, so it does not frame the partner's.
amq send --to "<partner>" --kind question \
--labels workflow:spec,phase:request \
--thread "spec/<topic>" --subject "Spec: <topic>" --body "<problem>"
Labels
Every spec message uses an ordinary AMQ kind plus these labels on the
spec/<topic> thread:
| Phase | Kind | Labels |
|---|---|---|
| Problem statement | question |
workflow:spec,phase:request |
| Research findings | brainstorm |
workflow:spec,phase:research |
| Discussion | brainstorm |
workflow:spec,phase:discuss |
| Plan draft | review_request |
workflow:spec,phase:draft |
| Plan feedback | review_response |
workflow:spec,phase:review |
| Final decision | decision |
workflow:spec,phase:decision |
| Progress/ETA | status |
workflow:spec |
When you receive a spec message
| Label | Your action |
|---|---|
phase:request |
Do your own research first, then send findings as brainstorm + phase:research. |
phase:research |
If you have not sent your own research on this thread, research and send it before you read the partner's. Then read the thread and start discussion as brainstorm + phase:discuss. |
phase:discuss |
Reply with your analysis; continue until aligned. |
phase:draft |
Review the plan and send feedback as review_response + phase:review. Do not implement. |
phase:review |
Revise the plan if needed, or confirm alignment. |
phase:decision |
Stop. Do not implement; see the approval gate below. |
Approval gate
A phase:decision message records agreement between agents; it is not user
approval. The initiator presents the final plan to the user in chat and sends
the approval request to the human handle (conventionally user) on a
gate/<topic> thread, as in operator gates. Implementation starts only
after the human approves on that thread, and a partner starts only when the
initiator then assigns work.
Rules
- Wait on the existing wake. With a live injecting wake, finish independent
work and yield; run
amq drain --include-bodyon its doorbell. Do not startamq watch,amq monitor, or a polling loop. Checkamq wake check --me <handle> --jsonwhen the capability is unknown. A boundedwatchis a fallback only without an injecting wake. - Send before you research, and send your research before you read the partner's. Independent research is what the second agent adds.
- Do not skip phases. Discussion is where misunderstandings surface.
- Keep the
spec/<topic>thread and the labels. The receiver table above depends on them. - Keep tool access during research. Do not enter a plan mode that blocks tools.
04 同仓库更多 Skills
worktable-review-with-annotations
Create, inspect, reply to, update, or resolve situated Worktable annotations. Use when feedback belongs to a Doc section, block, text range, or HTML Doc, or when the user asks to address existing review feedback and coordinate a requested artifact edit.
worktable-find-and-synthesize-context
Find, assess, and synthesize context from Worktable Docs and Records. Use when the user asks what a workspace contains, wants workspace-backed research, needs current facts reconciled across artifacts, or requests a cited synthesis without changing workspace state.
worktable-create-or-update-docs
Create, edit, rename, or maintain narrative Worktable Docs. Use for plans, decisions, briefs, notes, research syntheses, and other durable prose when the user requests a new artifact or a safe update to an existing one.
worktable-create-or-manage-records
Organize repeated structured information as durable Worktable Records. Use for research datasets, inventories, directories, pipelines, trackers, and other collections whose items need identity, fields, filtering, links, validation, or individual updates.
worktable-create-or-manage-interactive-html
Create or improve durable visual and interactive artifacts in Worktable. Use for dashboards, trackers, calculators, mini apps, slide presentations, and other requests that benefit from a polished HTML Doc.
worktable-collaborate-threads
Read, answer, and hand off messages through durable Worktable threads with users or other authenticated participants. Use when the user asks to check addressed messages, reply to a participant, continue a thread, request another agent's help, wait briefly for a response, or watch for comments and messages sent to the agent.