amq-spec

Parallel-research-then-converge design workflow between two agents. Use this skill when the user wants two agents to independently think through a design problem before aligning on a solution — "spec X with codex", "design X together", "both agents think through X", "brainstorm architecture together", "parallel research then joint proposal", "think through separately then align", "careful thought from both sides before coding", or any variation where the user wants collaborative design rather than just splitting implementation work. Also use this when you receive a message labeled workflow:spec and need to know the correct receiver-side protocol. Not for sending simple messages or reviews (use /amq-cli), implementing completed designs, or creating document templates.

Jump to install

Repository: hashgraph-online/awesome-codex-plugins
Last source activity: August 5, 2026 at 15:58
Detected SKILL.md language: English
Stars: 771
Forks: 236

Install options

The review-first prompt is selected by default. You can switch to a direct command or download a local copy.

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

A direct command skips the review prompt. Inspect the source before running it.

npx skills add https://github.com/hashgraph-online/awesome-codex-plugins --skill amq-spec

The command stays on one line. Scroll horizontally to inspect it before copying.

Prefer a local copy? Download the files currently available to SkillsMP.

Review the source files

Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.

File Explorer

2 files

SKILL.md

Source instructions · Read-only preview

Back to search Back to installation

name	amq-spec
version	0.52.3
description	Parallel-research-then-converge design workflow between two agents. Use this skill when the user wants two agents to independently think through a design problem before aligning on a solution — "spec X with codex", "design X together", "both agents think through X", "brainstorm architecture together", "parallel research then joint proposal", "think through separately then align", "careful thought from both sides before coding", or any variation where the user wants collaborative design rather than just splitting implementation work. Also use this when you receive a message labeled workflow:spec and need to know the correct receiver-side protocol. Not for sending simple messages or reviews (use /amq-cli), implementing completed designs, or creating document templates.
argument-hint	<description of what to design> [with <partner>]
metadata	{"short-description":"Multi-agent collaborative spec workflow","compatibility":"claude-code, codex-cli"}

/amq-spec — Collaborative Specification Workflow

This skill defines a structured two-agent specification flow.

Use canonical phases in order: Research -> Discuss -> Draft -> Review -> Present -> Execute

Detailed step-by-step protocol lives in references/spec-workflow.md. This file is the concise operational entrypoint.

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`

Label	Your action
`phase:request`	Read the problem statement, do your own independent research first, then submit findings as `brainstorm` + `phase:research`
`phase:research`	Before reading: check if you've already submitted your own research on this thread. If not, do your own research and submit it first. This preserves research independence — reading the partner's findings before forming your own view contaminates your perspective. Once your research is submitted, read the thread and start discussion as `brainstorm` + `phase:discuss`.
`phase:discuss`	Reply with your analysis, continue discussion until aligned
`phase:draft`	Review the plan and send feedback as `review_response` + `phase:review`. Your job here is review, not implementation — the plan needs to survive scrutiny before anyone builds it.
`phase:review`	Revise plan if needed, or confirm alignment
`phase:decision`	Stop. A `phase:decision` message is agent-to-agent alignment, not user approval, so do not implement from a spec decision alone. Only the human authorizes implementation, recorded as a structural gate to the initialized human handle (conventionally `user`; see the Operator Gates section in /amq-cli). Wait until the initiator confirms the human approved on the gate thread and assigns you work.

amq-spec

Install options

Review the source files

/amq-spec — Collaborative Specification Workflow

/amq-spec — Collaborative Specification Workflow

Parse Input

Pre-flight

First Action: Send problem to partner IMMEDIATELY

Label Convention

Quick Command Skeleton

When You RECEIVE a Spec Message

Protocol Discipline

Reference

amq-spec

Source facts

Install options

Review the source files

More from this repository

More from this repository

/amq-spec — Collaborative Specification Workflow

/amq-spec — Collaborative Specification Workflow

Parse Input

Pre-flight

First Action: Send problem to partner IMMEDIATELY

Label Convention

Quick Command Skeleton

When You RECEIVE a Spec Message

Protocol Discipline

Reference