amq-spec

Topics in the source

• AMQ collaborative specification
• Parse input
• Pre-flight
• Kickoff
• Labels
• When you receive a spec message
• Approval gate
• Rules

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. 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. 1. Verify AMQ is available: which amq 2. Verify the AMQ root is discoverable (.amqrc, AMQ env vars, or the default .agent-mail layout); otherwise run: amq coop init 3. Use thread name: spec/ 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. Every spec message uses an ordinary AMQ kind plus these labels on the spec/ thread: | Phase | Kind | Labels | |---|---|---| | Problem statement | question | workflow:spec,phase:request | | Research findings | brainstorm | workflow:spe

This is an excerpt. Refer to the complete source and its current requirements.