amq-speclisted
Install: claude install-skill avivsinai/skills-marketplace
# /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.
## 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
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/<topic>`
## First Action: Send problem to partner IMMEDIATELY
The entire point of the spec workflow is parallel research — both agents
exploring the problem independently, then comparing notes. Every second you
spend researching before sending is a second your partner sits idle waiting
for the problem statement. That's why the send comes first, even though your
instinct might be to "research first to give better context."
```bash
amq send --to <partner> --kind question \
--labels workflow:spec,phase:request \
--thread spec/<topic> --subject "Spec: <topic>" --body "<problem>"
```
Send the user's problem description verbatim — your own analysis goes in the
research