amq-spec

Coordinate two agents through phased AMQ spec workflows with thread naming conventions.

81|9|Updated Dec 25, 2025
One-click install
npx skills add https://github.com/avivsinai/agent-message-queue --skill amq-spec
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: amq-spec
Source: https://github.com/avivsinai/agent-message-queue/tree/main/skills/amq-spec
Command: npx skills add https://github.com/avivsinai/agent-message-queue --skill amq-spec

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Two agents can independently research a design problem and converge on a shared specification, avoiding bias from premature conclusions.

Core Features & Use Cases

  • Enforces independent exploration and phased collaboration for multi-agent design tasks.
  • Provides a canonical thread naming convention (spec/<topic>) and a standardized labeling scheme (workflow:spec, phase:...).
  • Supports a complete protocol with problem statement, research, discussion, drafting, review, and decision phases across agents and users.

Quick Start

Initiate a two-agent spec by framing a problem and sending it to your partner using the standard spec protocol.

Frequently Asked Questions about amq-spec

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I enable two agents to independently research a design problem and converge on a shared specification?

This multi-agent spec workflow solves the problem of premature bias by enforcing independent exploration before phased alignment. Agents research separately, then converge on a shared specification through structured communication.

What is the AMQ protocol for phase-ordered communication in multi-agent design tasks?

The AMQ protocol structures multi-agent design communication using standard primitives: question, brainstorm, draft, review, and decision. It enforces phase-ordered progression from problem statement through research to final specification.

How do I structure thread naming conventions for parallel agent exploration?

Structure thread naming for parallel agent exploration using the canonical spec/<topic> convention. Apply standardized labels like workflow:spec and phase:... to track progression across independent research and alignment stages.

Can I use this multi-agent spec workflow for both code architecture and process design?

You can apply this multi-agent spec workflow to code, architecture, or process design. It supports canonical spec workflows requiring parallel exploration and phased alignment across diverse technical design domains.

Does multi-agent spec collaboration require external dependencies to manage design phases?

Multi-agent spec collaboration requires no external dependencies to manage design phases. The protocol operates independently using standard AMQ primitives and thread naming conventions to coordinate two agents without additional packages.