amq-spec

The amq-spec skill implements a structured, parallel-research-then-converge workflow designed for multi-agent development teams. By leveraging the Agent Message Queue (AMQ), it allows two agents—such as Claude Code and the Codex CLI—to tackle complex design problems independently before aligning on a unified proposal. This approach effectively mitigates groupthink, prevents duplicative effort, and ensures that architectural decisions are rigorously vetted before any code is implemented. The workflow is designed for developers who need robust, collaborative planning for technical features, system design, or complex logic implementation. It enforces a disciplined phase-based protocol that mandates independent research as the first action, followed by discussion, drafting, and collaborative review, ensuring that neither agent biases the other during the initial problem-solving stage.

• Coordinates multi-agent collaboration using the AMQ interoperability bus for local file-based communication.

• Enforces a canonical six-phase spec workflow: Research, Discuss, Draft, Review, Present, and Execute.

• Promotes intellectual independence by requiring agents to submit research findings before reading the partner's analysis.

• Simplifies thread management with automatic spec/<topic> labeling for all related messages.

• Supports standard protocol kinds including question, brainstorm, review_request, review_response, and decision for clear state transitions.

• Provides a safe, crash-resilient mechanism using Atomic Maildir delivery principles for reliable agent handoffs.

• Use this skill when initiating collaborative design tasks such as 'spec X with codex' or 'design X together'.

• Always extract the topic (kebab-case), partner agent handle, and the problem statement from user input for accurate routing.

• Strictly adhere to the order of operations: Send problem to partner immediately before performing your own analysis to prevent bias.

• The initiator acts as the primary interface with the user, presenting the final, agreed-upon plan only after the spec workflow concludes.

• Note that this tool is not intended for simple messaging, file reviews, or project bootstrapping; use /amq-cli for those scenarios. Ensure the AMQ root is properly initialized before running the spec command.