[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6MEFKEDASDV6T8RX3Z0C092":3,"skill-same:01M6MEFKEDASDV6T8RX3Z0C092":92},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":31,"publishedAt":52,"linkOnly":53,"markdownContent":54,"markdownBody":55,"frontMatter":56,"refName":62,"commitSha":63,"skillDirectory":64,"forksCount":65,"repositoryHtmlUrl":66,"repositoryHomepageUrl":67,"ownerHtmlUrl":68,"ownerBlogUrl":69,"ownerDescription":70,"updatedAt":71,"install":72,"resources":85},"01M6MEFKEDASDV6T8RX3Z0C092","amq-spec",null,"Use two agents to research a design independently and converge on one specification through AMQ. Trigger for collaborative design or messages labeled workflow:spec; use amq-cli for ordinary coordination.","hashgraph-online\u002Fawesome-codex-plugins","hashgraph-online","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F160371962?v=4","01M6CNB6NRJVNNGN14TR01Q6D3","HOL (Hashgraph Online)","01M6JT1HSKKG9V68KQAQGBA7XP",1575,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Favivsinai\u002Fagent-message-queue\u002Fskills\u002Famq-spec\u002FSKILL.md",[18,23,26],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000015","视觉设计","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":27,"categoryName":28,"taxonomyType":29,"taxonomyTypeDesc":30},"01JBSEEDCAT000000000000032","设计师","PROFESSION","适用职业",[32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48,49,50,51],"spec","amq spec","multi-agent","spec workflow","cli","codex","research","multi","with","codex-cli","coordination","specification","code","workflow","use","design","messages","trigger","for","converge","2026-11-10 10:12:30",false,"---\nname: amq-spec\nversion: 0.143.0 # x-release-please-version\ndescription: Use two agents to research a design independently and converge on one specification through AMQ. Trigger for collaborative design or messages labeled workflow:spec; use amq-cli for ordinary coordination.\nargument-hint: \"\u003Cdescription of what to design> [with \u003Cpartner>]\"\nmetadata:\n  short-description: Multi-agent collaborative spec workflow\n  compatibility: claude-code, codex-cli\n---\n\n# AMQ collaborative specification\n\nTwo agents research a design problem independently, discuss it, and converge\non one plan. The user approves the plan before anyone implements it.\n\nPhases run in order:\n`Research -> Discuss -> Draft -> Review -> Present -> Execute`\n\nPer-phase commands and the research and plan templates are in\n[the spec workflow](references\u002Fspec-workflow.md).\n\n## Parse input\n\nFrom the user prompt, extract:\n- **topic**: short kebab-case spec name (e.g., `auth-token-rotation`)\n- **partner**: partner agent handle (default: `codex`)\n- **problem**: the full design problem statement\n\nIf topic\u002Fproblem are unclear, ask for clarification.\n\n## Pre-flight\n\n1. Verify AMQ is available: `which amq`\n2. Verify the AMQ root is discoverable (`.amqrc`, AMQ env vars, or the default `.agent-mail` layout); otherwise run: `amq coop init`\n3. Use thread name: `spec\u002F\u003Ctopic>`\n\n## Kickoff\n\nSend the problem to the partner first, then start your own research. Both\nagents then research in parallel. Send the user's problem verbatim; your own\nanalysis belongs in your research message, so it does not frame the partner's.\n\n```bash\namq send --to \"\u003Cpartner>\" --kind question \\\n  --labels workflow:spec,phase:request \\\n  --thread \"spec\u002F\u003Ctopic>\" --subject \"Spec: \u003Ctopic>\" --body \"\u003Cproblem>\"\n```\n\n## Labels\n\nEvery spec message uses an ordinary AMQ kind plus these labels on the\n`spec\u002F\u003Ctopic>` thread:\n\n| Phase | Kind | Labels |\n|---|---|---|\n| Problem statement | `question` | `workflow:spec,phase:request` |\n| Research findings | `brainstorm` | `workflow:spec,phase:research` |\n| Discussion | `brainstorm` | `workflow:spec,phase:discuss` |\n| Plan draft | `review_request` | `workflow:spec,phase:draft` |\n| Plan feedback | `review_response` | `workflow:spec,phase:review` |\n| Final decision | `decision` | `workflow:spec,phase:decision` |\n| Progress\u002FETA | `status` | `workflow:spec` |\n\n## When you receive a spec message\n\n| Label | Your action |\n|---|---|\n| `phase:request` | Do your own research first, then send findings as `brainstorm` + `phase:research`. |\n| `phase:research` | If you have not sent your own research on this thread, research and send it before you read the partner's. Then read the thread and start discussion as `brainstorm` + `phase:discuss`. |\n| `phase:discuss` | Reply with your analysis; continue until aligned. |\n| `phase:draft` | Review the plan and send feedback as `review_response` + `phase:review`. Do not implement. |\n| `phase:review` | Revise the plan if needed, or confirm alignment. |\n| `phase:decision` | Stop. Do not implement; see the approval gate below. |\n\n## Approval gate\n\nA `phase:decision` message records agreement between agents; it is not user\napproval. The initiator presents the final plan to the user in chat and sends\nthe approval request to the human handle (conventionally `user`) on a\n`gate\u002F\u003Ctopic>` thread, as in [operator gates](https:\u002F\u002Fgithub.com\u002Favivsinai\u002Fagent-message-queue\u002Fblob\u002Fmain\u002Fskills\u002Famq-cli\u002Freferences\u002Foperations.md#operator-gates). Implementation starts only\nafter the human approves on that thread, and a partner starts only when the\ninitiator then assigns work.\n\n## Rules\n\n- **Wait on the existing wake.** With a live injecting wake, finish independent\n  work and yield; run `amq drain --include-body` on its doorbell. Do not start\n  `amq watch`, `amq monitor`, or a polling loop. Check\n  `amq wake check --me \u003Chandle> --json` when the capability is unknown. A\n  bounded `watch` is a fallback only without an injecting wake.\n- **Send before you research, and send your research before you read the\n  partner's.** Independent research is what the second agent adds.\n- **Do not skip phases.** Discussion is where misunderstandings surface.\n- **Keep the `spec\u002F\u003Ctopic>` thread and the labels.** The receiver table above\n  depends on them.\n- **Keep tool access during research.** Do not enter a plan mode that blocks\n  tools.\n","# AMQ collaborative specification\n\nTwo agents research a design problem independently, discuss it, and converge\non one plan. The user approves the plan before anyone implements it.\n\nPhases run in order:\n`Research -> Discuss -> Draft -> Review -> Present -> Execute`\n\nPer-phase commands and the research and plan templates are in\n[the spec workflow](references\u002Fspec-workflow.md).\n\n## Parse input\n\nFrom the user prompt, extract:\n- **topic**: short kebab-case spec name (e.g., `auth-token-rotation`)\n- **partner**: partner agent handle (default: `codex`)\n- **problem**: the full design problem statement\n\nIf topic\u002Fproblem are unclear, ask for clarification.\n\n## Pre-flight\n\n1. Verify AMQ is available: `which amq`\n2. Verify the AMQ root is discoverable (`.amqrc`, AMQ env vars, or the default `.agent-mail` layout); otherwise run: `amq coop init`\n3. Use thread name: `spec\u002F\u003Ctopic>`\n\n## Kickoff\n\nSend the problem to the partner first, then start your own research. Both\nagents then research in parallel. Send the user's problem verbatim; your own\nanalysis belongs in your research message, so it does not frame the partner's.\n\n```bash\namq send --to \"\u003Cpartner>\" --kind question \\\n  --labels workflow:spec,phase:request \\\n  --thread \"spec\u002F\u003Ctopic>\" --subject \"Spec: \u003Ctopic>\" --body \"\u003Cproblem>\"\n```\n\n## Labels\n\nEvery spec message uses an ordinary AMQ kind plus these labels on the\n`spec\u002F\u003Ctopic>` thread:\n\n| Phase | Kind | Labels |\n|---|---|---|\n| Problem statement | `question` | `workflow:spec,phase:request` |\n| Research findings | `brainstorm` | `workflow:spec,phase:research` |\n| Discussion | `brainstorm` | `workflow:spec,phase:discuss` |\n| Plan draft | `review_request` | `workflow:spec,phase:draft` |\n| Plan feedback | `review_response` | `workflow:spec,phase:review` |\n| Final decision | `decision` | `workflow:spec,phase:decision` |\n| Progress\u002FETA | `status` | `workflow:spec` |\n\n## When you receive a spec message\n\n| Label | Your action |\n|---|---|\n| `phase:request` | Do your own research first, then send findings as `brainstorm` + `phase:research`. |\n| `phase:research` | If you have not sent your own research on this thread, research and send it before you read the partner's. Then read the thread and start discussion as `brainstorm` + `phase:discuss`. |\n| `phase:discuss` | Reply with your analysis; continue until aligned. |\n| `phase:draft` | Review the plan and send feedback as `review_response` + `phase:review`. Do not implement. |\n| `phase:review` | Revise the plan if needed, or confirm alignment. |\n| `phase:decision` | Stop. Do not implement; see the approval gate below. |\n\n## Approval gate\n\nA `phase:decision` message records agreement between agents; it is not user\napproval. The initiator presents the final plan to the user in chat and sends\nthe approval request to the human handle (conventionally `user`) on a\n`gate\u002F\u003Ctopic>` thread, as in [operator gates](https:\u002F\u002Fgithub.com\u002Favivsinai\u002Fagent-message-queue\u002Fblob\u002Fmain\u002Fskills\u002Famq-cli\u002Freferences\u002Foperations.md#operator-gates). Implementation starts only\nafter the human approves on that thread, and a partner starts only when the\ninitiator then assigns work.\n\n## Rules\n\n- **Wait on the existing wake.** With a live injecting wake, finish independent\n  work and yield; run `amq drain --include-body` on its doorbell. Do not start\n  `amq watch`, `amq monitor`, or a polling loop. Check\n  `amq wake check --me \u003Chandle> --json` when the capability is unknown. A\n  bounded `watch` is a fallback only without an injecting wake.\n- **Send before you research, and send your research before you read the\n  partner's.** Independent research is what the second agent adds.\n- **Do not skip phases.** Discussion is where misunderstandings surface.\n- **Keep the `spec\u002F\u003Ctopic>` thread and the labels.** The receiver table above\n  depends on them.\n- **Keep tool access during research.** Do not enter a plan mode that blocks\n  tools.\n",{"name":5,"version":57,"metadata":58,"description":7,"argument-hint":61},"0.143.0",{"compatibility":59,"short-description":60},"claude-code, codex-cli","Multi-agent collaborative spec workflow","\u003Cdescription of what to design> [with \u003Cpartner>]","main","cebc3dce495d7eb80d3b1d5841f877a4a92e162d","plugins\u002Favivsinai\u002Fagent-message-queue\u002Fskills\u002Famq-spec",491,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins","https:\u002F\u002Fhol.org\u002Fplugins\u002Fbest-codex-plugins","https:\u002F\u002Fgithub.com\u002Fhashgraph-online","https:\u002F\u002Fhol.org","Open-source standards and developer tools for interoperable AI agents: discovery, identity, communication, payments, privacy and security.","2026-11-14 14:06:13",{"source":8,"skillName":5,"commands":73,"prompt":83,"zipAvailable":84},[74,77,80],{"tool":75,"command":76},"npx","npx skills add hashgraph-online\u002Fawesome-codex-plugins --skill amq-spec",{"tool":78,"command":79},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill amq-spec",{"tool":81,"command":82},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill amq-spec","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Favivsinai\u002Fagent-message-queue\u002Fskills\u002Famq-spec\u002FSKILL.md",true,[86],{"path":87,"resourceType":88,"resourceTypeDesc":89,"sizeBytes":90,"sourceHtmlUrl":91},"references\u002Fspec-workflow.md","REFERENCE","参考文档",5898,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Favivsinai\u002Fagent-message-queue\u002Fskills\u002Famq-spec\u002Freferences\u002Fspec-workflow.md",[93,103,111,119,127,135],{"skillNo":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":97,"licenseFileUrl":98,"sourceHtmlUrl":99,"categories":100,"keywords":101,"publishedAt":102},"01M7DV332YQMGD8WTRJ9DZQXTB","worktable-review-with-annotations","Create, inspect, reply to, update, or resolve situated Worktable annotations. Use when feedback belongs to a Doc section, block, text range, or HTML Doc, or when the user asks to address existing review feedback and coordinate a requested artifact edit.","MIT","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-review-with-annotations\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-review-with-annotations\u002FSKILL.md",[],[],"2026-11-15 14:19:17",{"skillNo":104,"name":105,"nameZh":6,"description":106,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":97,"licenseFileUrl":107,"sourceHtmlUrl":108,"categories":109,"keywords":110,"publishedAt":102},"01M7DV2YGHCZVBEB1AHYB6CGHE","worktable-find-and-synthesize-context","Find, assess, and synthesize context from Worktable Docs and Records. Use when the user asks what a workspace contains, wants workspace-backed research, needs current facts reconciled across artifacts, or requests a cited synthesis without changing workspace state.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-find-and-synthesize-context\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-find-and-synthesize-context\u002FSKILL.md",[],[],{"skillNo":112,"name":113,"nameZh":6,"description":114,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":97,"licenseFileUrl":115,"sourceHtmlUrl":116,"categories":117,"keywords":118,"publishedAt":102},"01M7DV2TQN1H11ME2SAF9MXN7V","worktable-create-or-update-docs","Create, edit, rename, or maintain narrative Worktable Docs. Use for plans, decisions, briefs, notes, research syntheses, and other durable prose when the user requests a new artifact or a safe update to an existing one.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-update-docs\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-update-docs\u002FSKILL.md",[],[],{"skillNo":120,"name":121,"nameZh":6,"description":122,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":97,"licenseFileUrl":123,"sourceHtmlUrl":124,"categories":125,"keywords":126,"publishedAt":102},"01M7DV2NE452NEA8TXATKSNAJH","worktable-create-or-manage-records","Organize repeated structured information as durable Worktable Records. Use for research datasets, inventories, directories, pipelines, trackers, and other collections whose items need identity, fields, filtering, links, validation, or individual updates.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-records\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-records\u002FSKILL.md",[],[],{"skillNo":128,"name":129,"nameZh":6,"description":130,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":97,"licenseFileUrl":131,"sourceHtmlUrl":132,"categories":133,"keywords":134,"publishedAt":102},"01M7DV2HENRBR2KSCVM064WH0Y","worktable-create-or-manage-interactive-html","Create or improve durable visual and interactive artifacts in Worktable. Use for dashboards, trackers, calculators, mini apps, slide presentations, and other requests that benefit from a polished HTML Doc.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-interactive-html\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-interactive-html\u002FSKILL.md",[],[],{"skillNo":136,"name":137,"nameZh":6,"description":138,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":97,"licenseFileUrl":139,"sourceHtmlUrl":140,"categories":141,"keywords":142,"publishedAt":102},"01M7DV2CADR5R7RQFFYPNAGR9Y","worktable-collaborate-threads","Read, answer, and hand off messages through durable Worktable threads with users or other authenticated participants. Use when the user asks to check addressed messages, reply to a participant, continue a thread, request another agent's help, wait briefly for a response, or watch for comments and messages sent to the agent.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-collaborate-threads\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-collaborate-threads\u002FSKILL.md",[],[]]