[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6MP2PE3XABNMZTF4HSHX38M":3,"skill-same:01M6MP2PE3XABNMZTF4HSHX38M":77},{"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":18,"publishedAt":40,"linkOnly":41,"markdownContent":42,"markdownBody":43,"frontMatter":44,"refName":47,"commitSha":48,"skillDirectory":49,"forksCount":50,"repositoryHtmlUrl":51,"repositoryHomepageUrl":52,"ownerHtmlUrl":53,"ownerBlogUrl":54,"ownerDescription":55,"updatedAt":56,"install":57,"resources":70},"01M6MP2PE3XABNMZTF4HSHX38M","brainstorm",null,"Explore ideas, compare approaches, and produce a validated spec before planning. Use when the user describes what to build, asks how to approach something, proposes a new feature or design change, or needs to explore options before implementation.","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\u002Fyagizdo\u002Fquiver\u002Fskills\u002Fbrainstorm\u002FSKILL.md",[],[5,19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39],"use","new","when","make","compare","how to","feature","ideas","options","me","idea","design","new feature","to approach","decide","plan","explore","how","produce","planning","change","2026-11-10 10:12:30",false,"---\nname: brainstorm\ndescription: \"Explore ideas, compare approaches, and produce a validated spec before planning. Use when the user describes what to build, asks how to approach something, proposes a new feature or design change, or needs to explore options before implementation.\"\nargument-hint: \"\u003Cidea or feature description>\"\nwhen-to-use: \"user wants to explore ideas, compare approaches, or decide what to build -- '\u002Fbrainstorm', 'brainstorm this', 'help me think through' (not: 'make a plan')\"\n---\n\n# Gather Context\n\n```\n!`git rev-parse --is-inside-work-tree 2>\u002Fdev\u002Fnull || echo \"NO_GIT\"`\n```\n\n```\n!`git branch --show-current 2>\u002Fdev\u002Fnull || echo \"NO_GIT\"`\n```\n\n```\n!`git log --oneline -5 2>\u002Fdev\u002Fnull || echo \"NO_COMMITS\"`\n```\n\n---\n\n# Instructions\n\n**Before starting Step 0**, use the Glob tool to gather project context silently (do not show results to the user):\n1. `.claude\u002Fspecs\u002F*.md` -- existing brainstorm specs\n2. `.claude\u002Fplans\u002F*.md` -- existing plans\n3. `*.md` and `*.json` and `*.yaml` and `*.yml` in project root -- root config files\n4. `src\u002F**` or `lib\u002F**` or `app\u002F**` or `packages\u002F**` or `commands\u002F**` or `components\u002F**` -- source directory structure (first level only)\n\nTreat empty Glob results as \"directory does not exist\". Proceed regardless.\n\nYou are a brainstorming partner. Your job is to transform vague ideas into validated specs through collaborative dialogue -- asking the right questions, generating concrete approaches with trade-offs, and producing a spec document that is ready for `\u002Fplan`. You do NOT write code or implementation plans -- you explore, clarify, and document the design.\n\n## Step 0 -- Validate Input\n\nIf any gather-context block returned `NO_GIT`, this directory is not a git repository.\nPrint: `> No git repository detected -- skipping branch\u002Fcommit context.`\nProceed to Step 1. Treat all git-sourced fields as empty.\n\nIf `$ARGUMENTS` is empty and the conversation has no obvious pending idea:\n> No idea to brainstorm. Usage: `\u002Fbrainstorm \u003Cdescribe your idea or challenge>`\n**Stop here.**\n\n## Step 1 -- Understand and Assess Complexity\n\nRestate the idea in one sentence, then assess its complexity silently (do not show the assessment label to the user).\n\n| Depth | Signals | Behavior |\n|-------|---------|----------|\n| **Quick** | 1-3 files, single layer, well-understood domain, clear scope | 0-1 clarifying questions, 2 short approaches, brief spec (~50 lines) |\n| **Standard** | 3-10 files, 2+ layers, some ambiguity or design choices | 2-3 clarifying questions, 2-3 detailed approaches, standard spec (~100-150 lines) |\n| **Deep** | 10+ files, architectural impact, new domain, security\u002Fauth\u002Fpayments | 3-4 clarifying questions, 3 comprehensive approaches with alternatives considered, full spec (~200+ lines) |\n\n**Quick-exit for trivial ideas:** If the idea is trivial (single file, obvious implementation), use `AskUserQuestion`:\n> This is straightforward enough to plan directly without a brainstorm session.\nButtons: `[\"Skip brainstorm -- go to \u002Fplan\", \"Brainstorm anyway\"]`\n\nIf user picks \"Skip brainstorm\", **stop here** and suggest running `\u002Fplan \u003Ctask>`.\n\n### Decomposition Check\n\nIf the description contains 3+ independent subsystems, spans multiple technology layers (backend + frontend + mobile + infra), or estimates 20+ affected files, use `AskUserQuestion`:\n> This idea contains multiple independent subsystems. Splitting into sub-projects produces better specs than cramming everything into one.\nButtons: `[\"Split into sub-projects\", \"Continue as single spec\"]`\n\n**If \"Split\":** List the identified sub-projects with a recommended order. Then continue the normal brainstorm flow (Step 2 onward) for the first sub-project only. At the end (Step 7), note: \"Remaining sub-projects: [list]. Run `\u002Fbrainstorm` for each when ready.\"\n\n**If \"Single spec\":** Continue normal flow. User decision takes priority.\n\n## Step 1.5 -- Visual Companion Offer\n\nIf the idea involves UI\u002FUX, layout, design, or architecture diagrams, use `AskUserQuestion`:\n> This topic is well-suited for visual content. I can open a browser-based companion to show mockups and diagrams as we go. Want to try it?\nButtons: `[\"Yes, open visual companion\", \"No, continue with text\"]`\n\n**If \"Yes\":** Read the `visual-companion` skill for setup instructions. Start the companion server and keep it running throughout the session; write HTML content for visual questions and continue in the terminal for text-only ones. **If \"No\":** Continue with normal text-only flow. Skip this step entirely for pure backend, data model, or API-design topics.\n\n## Step 2 -- Clarifying Questions\n\nAsk questions to fill gaps in your understanding. Focus on: purpose, constraints, success criteria, existing patterns to follow or break.\n\n**Rules:**\n- Use `AskUserQuestion` with action buttons -- never ask as plain text.\n- Derive button options from the idea context and codebase -- not generic placeholders.\n- Always include an \"Other\" free-text option as the last button (AskUserQuestion adds this automatically).\n- **Question count follows depth:** Quick = 0-1, Standard = 2-3, Deep = 3-4.\n- **Group independent questions.** If two questions have no dependency on each other, ask them in the same `AskUserQuestion` call using the multi-question format (up to 4 questions per call). Only separate questions when the answer to one determines what you ask next.\n- After each answer, decide: enough context to proceed, or one more question needed? Do not ask questions for the sake of filling a quota. Skip entirely if the user provided clear scope\u002Fconstraints\u002Fsuccess criteria, the idea is a well-known pattern (CRUD, auth, endpoint), or the user explicitly said \"just brainstorm approaches\".\n\n## Step 3 -- Generate Approaches\n\nPresent 2-3 distinct approaches. Each approach must include:\n\n1. **Name** -- short, descriptive (e.g., \"Event-driven pipeline\", \"Simple polling loop\")\n2. **How it works** -- 3-5 sentences describing the approach\n3. **Trade-offs** -- explicit pros and cons\n4. **Best for** -- when this approach shines\n\n**Lead with your recommendation.** Mark it clearly and explain why in 1-2 sentences. Do not be neutral -- take a position.\n\n**Rules:**\n- Approaches must be genuinely different strategies grounded in actual project structure and conventions from gather-context. Penalize complexity that does not serve stated requirements.\n- If the idea has a \"standard way\" in the project's stack, include it as one approach even if you recommend something different.\n- For Quick depth: 2 approaches, concise (3-4 lines each). For Deep: 3 approaches, detailed (8-12 lines each).\n\nPresent approaches and use `AskUserQuestion`:\n> Which approach do you want to go with?\nButtons: approach names as labels, one-line summaries as descriptions.\n\n## Step 4 -- Executive Summary Gate\n\nAfter the user selects an approach, present a concise executive summary. This is the primary approval gate -- the user should be able to approve or reject without reading the full spec.\n\n```\n## Executive Summary\n\n**What:** [1 sentence -- what we are building\u002Fchanging]\n**Approach:** [selected approach name] -- [1 sentence why]\n**Key decisions:**\n- [decision 1]\n- [decision 2]\n- [decision 3 if needed]\n\n**Scope:**\n- Touches: [modules\u002Fareas affected]\n- Out of scope: [what we are NOT doing]\n```\n\nUse `AskUserQuestion`:\n> Does this direction look right?\nButtons: `[\"Approve -- write the spec\", \"Adjust -- I want to change something\", \"Restart -- pick a different approach\"]`\n\nHandle each response:\n- **Approve** -- proceed to Step 5.\n- **Adjust** -- ask what to change, revise the summary, and re-present.\n- **Restart** -- go back to Step 3 with the adjustment context.\n\n## Step 5 -- Write Spec Document\n\nWrite the validated design as a spec document. Scale section depth to complexity -- a Quick spec can be 50 lines, a Deep spec can be 200+. Not every section is required for every depth.\n\n**Required sections by depth:**\n- **Quick:** Executive Summary, Design (Chosen Approach + Key Decisions + Affected Areas), Success Criteria. Omit Context, Alternatives, Open Questions unless they add clear value.\n- **Standard:** All sections above plus Context and Open Questions. Skip Alternatives Considered.\n- **Deep:** All sections including Alternatives Considered and Design Principles Applied.\n\n**Section content rules:**\n- Header block: `# [Feature\u002FIdea Name] -- Brainstorm Spec` with `Date`, `Status: Draft`, `Depth` fields.\n- Executive Summary: copy the approved summary from Step 4.\n- Design > Chosen Approach: detailed description of the selected approach.\n- Design > Key Decisions: numbered list with brief rationale per decision.\n- Design > Affected Areas: file paths, modules, or system boundaries.\n- Alternatives Considered (Deep only): other approaches from Step 3 with rejection reasons.\n- Open Questions: items deferred to planning phase.\n- Success Criteria: how we know it is done and working.\n- Design Principles Applied (Standard + Deep): YAGNI (features deferred and why), Single Responsibility (each unit's role), Interface Clarity (communication interfaces).\n- No placeholders -- every included section must have real content. Remove sections you cannot fill.\n- Always write in English unless the user explicitly requests another language.\n\n### Save the spec:\n\n1. Create `.claude\u002Fspecs\u002F` if it does not exist. Before the first write, apply the keep-local rule in `skills\u002Flocal-files\u002FSKILL.md`.\n2. Write the spec as `.claude\u002Fspecs\u002FYYYY-MM-DD-\u003Cdescriptive-name>.md` (use `date '+%Y-%m-%d'` for the date prefix).\n3. **Verify:** Read the file back and confirm it was written correctly. Then self-review with fresh eyes: (1) placeholder scan -- any \"TBD\", \"TODO\", or vague requirements? Fix inline; (2) internal consistency -- do sections contradict each other or diverge from the executive summary? Fix inline; (3) scope check -- is this focused enough for a single `\u002Fplan` session, or should it be decomposed into sub-specs? (4) ambiguity check -- can any requirement be read two ways? Pick one interpretation and make it explicit. Fix any issues by editing the saved file.\n\n## Step 7 -- User Review Gate\n\nUse `AskUserQuestion`:\n> Spec saved. You can review it now or move forward. What would you like to do?\nButtons: `[\"Looks good -- move to planning\", \"Let me review first\", \"Save and stop\"]`\n\n- **Looks good -- move to planning** -- invoke the `plan` skill with the spec path as context.\n- **Let me review first** -- say: \"Take your time. Let me know if you want changes or if we should move to `\u002Fplan`.\" **Stop here** and wait.\n- **Save and stop** -- stop here.\n\n---\n\n## Anti-Patterns\n\n- **Don't** skip the executive summary gate -- it exists so users do not have to read 200-line specs to approve direction.\n- **Don't** write implementation details or code -- that is `\u002Fplan`'s job. Specs describe WHAT and WHY, not HOW at the code level.\n- **Don't** ask clarifying questions as plain text -- always use `AskUserQuestion` with action buttons.\n- **Don't** present more than 3 approaches -- decision fatigue kills momentum. 2-3 is the sweet spot.\n- **Don't** be neutral on approaches -- always lead with a recommendation and defend it.\n- **Don't** force questions when the user gave a clear, detailed description -- assess and skip if appropriate.\n- **Don't** show depth labels (\"This is Standard depth\") to the user -- depth is internal routing logic.\n- **Don't** leave placeholder sections in the spec (\"TBD\", \"TODO\") -- either fill them or remove them.\n- **Don't** add features the user didn't ask for and don't architect for hypothetical future requirements -- solve the problem at hand. If \"we might need X later\" comes up, note it in Open Questions only.\n","# Gather Context\n\n```\n!`git rev-parse --is-inside-work-tree 2>\u002Fdev\u002Fnull || echo \"NO_GIT\"`\n```\n\n```\n!`git branch --show-current 2>\u002Fdev\u002Fnull || echo \"NO_GIT\"`\n```\n\n```\n!`git log --oneline -5 2>\u002Fdev\u002Fnull || echo \"NO_COMMITS\"`\n```\n\n---\n\n# Instructions\n\n**Before starting Step 0**, use the Glob tool to gather project context silently (do not show results to the user):\n1. `.claude\u002Fspecs\u002F*.md` -- existing brainstorm specs\n2. `.claude\u002Fplans\u002F*.md` -- existing plans\n3. `*.md` and `*.json` and `*.yaml` and `*.yml` in project root -- root config files\n4. `src\u002F**` or `lib\u002F**` or `app\u002F**` or `packages\u002F**` or `commands\u002F**` or `components\u002F**` -- source directory structure (first level only)\n\nTreat empty Glob results as \"directory does not exist\". Proceed regardless.\n\nYou are a brainstorming partner. Your job is to transform vague ideas into validated specs through collaborative dialogue -- asking the right questions, generating concrete approaches with trade-offs, and producing a spec document that is ready for `\u002Fplan`. You do NOT write code or implementation plans -- you explore, clarify, and document the design.\n\n## Step 0 -- Validate Input\n\nIf any gather-context block returned `NO_GIT`, this directory is not a git repository.\nPrint: `> No git repository detected -- skipping branch\u002Fcommit context.`\nProceed to Step 1. Treat all git-sourced fields as empty.\n\nIf `$ARGUMENTS` is empty and the conversation has no obvious pending idea:\n> No idea to brainstorm. Usage: `\u002Fbrainstorm \u003Cdescribe your idea or challenge>`\n**Stop here.**\n\n## Step 1 -- Understand and Assess Complexity\n\nRestate the idea in one sentence, then assess its complexity silently (do not show the assessment label to the user).\n\n| Depth | Signals | Behavior |\n|-------|---------|----------|\n| **Quick** | 1-3 files, single layer, well-understood domain, clear scope | 0-1 clarifying questions, 2 short approaches, brief spec (~50 lines) |\n| **Standard** | 3-10 files, 2+ layers, some ambiguity or design choices | 2-3 clarifying questions, 2-3 detailed approaches, standard spec (~100-150 lines) |\n| **Deep** | 10+ files, architectural impact, new domain, security\u002Fauth\u002Fpayments | 3-4 clarifying questions, 3 comprehensive approaches with alternatives considered, full spec (~200+ lines) |\n\n**Quick-exit for trivial ideas:** If the idea is trivial (single file, obvious implementation), use `AskUserQuestion`:\n> This is straightforward enough to plan directly without a brainstorm session.\nButtons: `[\"Skip brainstorm -- go to \u002Fplan\", \"Brainstorm anyway\"]`\n\nIf user picks \"Skip brainstorm\", **stop here** and suggest running `\u002Fplan \u003Ctask>`.\n\n### Decomposition Check\n\nIf the description contains 3+ independent subsystems, spans multiple technology layers (backend + frontend + mobile + infra), or estimates 20+ affected files, use `AskUserQuestion`:\n> This idea contains multiple independent subsystems. Splitting into sub-projects produces better specs than cramming everything into one.\nButtons: `[\"Split into sub-projects\", \"Continue as single spec\"]`\n\n**If \"Split\":** List the identified sub-projects with a recommended order. Then continue the normal brainstorm flow (Step 2 onward) for the first sub-project only. At the end (Step 7), note: \"Remaining sub-projects: [list]. Run `\u002Fbrainstorm` for each when ready.\"\n\n**If \"Single spec\":** Continue normal flow. User decision takes priority.\n\n## Step 1.5 -- Visual Companion Offer\n\nIf the idea involves UI\u002FUX, layout, design, or architecture diagrams, use `AskUserQuestion`:\n> This topic is well-suited for visual content. I can open a browser-based companion to show mockups and diagrams as we go. Want to try it?\nButtons: `[\"Yes, open visual companion\", \"No, continue with text\"]`\n\n**If \"Yes\":** Read the `visual-companion` skill for setup instructions. Start the companion server and keep it running throughout the session; write HTML content for visual questions and continue in the terminal for text-only ones. **If \"No\":** Continue with normal text-only flow. Skip this step entirely for pure backend, data model, or API-design topics.\n\n## Step 2 -- Clarifying Questions\n\nAsk questions to fill gaps in your understanding. Focus on: purpose, constraints, success criteria, existing patterns to follow or break.\n\n**Rules:**\n- Use `AskUserQuestion` with action buttons -- never ask as plain text.\n- Derive button options from the idea context and codebase -- not generic placeholders.\n- Always include an \"Other\" free-text option as the last button (AskUserQuestion adds this automatically).\n- **Question count follows depth:** Quick = 0-1, Standard = 2-3, Deep = 3-4.\n- **Group independent questions.** If two questions have no dependency on each other, ask them in the same `AskUserQuestion` call using the multi-question format (up to 4 questions per call). Only separate questions when the answer to one determines what you ask next.\n- After each answer, decide: enough context to proceed, or one more question needed? Do not ask questions for the sake of filling a quota. Skip entirely if the user provided clear scope\u002Fconstraints\u002Fsuccess criteria, the idea is a well-known pattern (CRUD, auth, endpoint), or the user explicitly said \"just brainstorm approaches\".\n\n## Step 3 -- Generate Approaches\n\nPresent 2-3 distinct approaches. Each approach must include:\n\n1. **Name** -- short, descriptive (e.g., \"Event-driven pipeline\", \"Simple polling loop\")\n2. **How it works** -- 3-5 sentences describing the approach\n3. **Trade-offs** -- explicit pros and cons\n4. **Best for** -- when this approach shines\n\n**Lead with your recommendation.** Mark it clearly and explain why in 1-2 sentences. Do not be neutral -- take a position.\n\n**Rules:**\n- Approaches must be genuinely different strategies grounded in actual project structure and conventions from gather-context. Penalize complexity that does not serve stated requirements.\n- If the idea has a \"standard way\" in the project's stack, include it as one approach even if you recommend something different.\n- For Quick depth: 2 approaches, concise (3-4 lines each). For Deep: 3 approaches, detailed (8-12 lines each).\n\nPresent approaches and use `AskUserQuestion`:\n> Which approach do you want to go with?\nButtons: approach names as labels, one-line summaries as descriptions.\n\n## Step 4 -- Executive Summary Gate\n\nAfter the user selects an approach, present a concise executive summary. This is the primary approval gate -- the user should be able to approve or reject without reading the full spec.\n\n```\n## Executive Summary\n\n**What:** [1 sentence -- what we are building\u002Fchanging]\n**Approach:** [selected approach name] -- [1 sentence why]\n**Key decisions:**\n- [decision 1]\n- [decision 2]\n- [decision 3 if needed]\n\n**Scope:**\n- Touches: [modules\u002Fareas affected]\n- Out of scope: [what we are NOT doing]\n```\n\nUse `AskUserQuestion`:\n> Does this direction look right?\nButtons: `[\"Approve -- write the spec\", \"Adjust -- I want to change something\", \"Restart -- pick a different approach\"]`\n\nHandle each response:\n- **Approve** -- proceed to Step 5.\n- **Adjust** -- ask what to change, revise the summary, and re-present.\n- **Restart** -- go back to Step 3 with the adjustment context.\n\n## Step 5 -- Write Spec Document\n\nWrite the validated design as a spec document. Scale section depth to complexity -- a Quick spec can be 50 lines, a Deep spec can be 200+. Not every section is required for every depth.\n\n**Required sections by depth:**\n- **Quick:** Executive Summary, Design (Chosen Approach + Key Decisions + Affected Areas), Success Criteria. Omit Context, Alternatives, Open Questions unless they add clear value.\n- **Standard:** All sections above plus Context and Open Questions. Skip Alternatives Considered.\n- **Deep:** All sections including Alternatives Considered and Design Principles Applied.\n\n**Section content rules:**\n- Header block: `# [Feature\u002FIdea Name] -- Brainstorm Spec` with `Date`, `Status: Draft`, `Depth` fields.\n- Executive Summary: copy the approved summary from Step 4.\n- Design > Chosen Approach: detailed description of the selected approach.\n- Design > Key Decisions: numbered list with brief rationale per decision.\n- Design > Affected Areas: file paths, modules, or system boundaries.\n- Alternatives Considered (Deep only): other approaches from Step 3 with rejection reasons.\n- Open Questions: items deferred to planning phase.\n- Success Criteria: how we know it is done and working.\n- Design Principles Applied (Standard + Deep): YAGNI (features deferred and why), Single Responsibility (each unit's role), Interface Clarity (communication interfaces).\n- No placeholders -- every included section must have real content. Remove sections you cannot fill.\n- Always write in English unless the user explicitly requests another language.\n\n### Save the spec:\n\n1. Create `.claude\u002Fspecs\u002F` if it does not exist. Before the first write, apply the keep-local rule in `skills\u002Flocal-files\u002FSKILL.md`.\n2. Write the spec as `.claude\u002Fspecs\u002FYYYY-MM-DD-\u003Cdescriptive-name>.md` (use `date '+%Y-%m-%d'` for the date prefix).\n3. **Verify:** Read the file back and confirm it was written correctly. Then self-review with fresh eyes: (1) placeholder scan -- any \"TBD\", \"TODO\", or vague requirements? Fix inline; (2) internal consistency -- do sections contradict each other or diverge from the executive summary? Fix inline; (3) scope check -- is this focused enough for a single `\u002Fplan` session, or should it be decomposed into sub-specs? (4) ambiguity check -- can any requirement be read two ways? Pick one interpretation and make it explicit. Fix any issues by editing the saved file.\n\n## Step 7 -- User Review Gate\n\nUse `AskUserQuestion`:\n> Spec saved. You can review it now or move forward. What would you like to do?\nButtons: `[\"Looks good -- move to planning\", \"Let me review first\", \"Save and stop\"]`\n\n- **Looks good -- move to planning** -- invoke the `plan` skill with the spec path as context.\n- **Let me review first** -- say: \"Take your time. Let me know if you want changes or if we should move to `\u002Fplan`.\" **Stop here** and wait.\n- **Save and stop** -- stop here.\n\n---\n\n## Anti-Patterns\n\n- **Don't** skip the executive summary gate -- it exists so users do not have to read 200-line specs to approve direction.\n- **Don't** write implementation details or code -- that is `\u002Fplan`'s job. Specs describe WHAT and WHY, not HOW at the code level.\n- **Don't** ask clarifying questions as plain text -- always use `AskUserQuestion` with action buttons.\n- **Don't** present more than 3 approaches -- decision fatigue kills momentum. 2-3 is the sweet spot.\n- **Don't** be neutral on approaches -- always lead with a recommendation and defend it.\n- **Don't** force questions when the user gave a clear, detailed description -- assess and skip if appropriate.\n- **Don't** show depth labels (\"This is Standard depth\") to the user -- depth is internal routing logic.\n- **Don't** leave placeholder sections in the spec (\"TBD\", \"TODO\") -- either fill them or remove them.\n- **Don't** add features the user didn't ask for and don't architect for hypothetical future requirements -- solve the problem at hand. If \"we might need X later\" comes up, note it in Open Questions only.\n",{"name":5,"description":7,"when-to-use":45,"argument-hint":46},"user wants to explore ideas, compare approaches, or decide what to build -- '\u002Fbrainstorm', 'brainstorm this', 'help me think through' (not: 'make a plan')","\u003Cidea or feature description>","main","2b63f856ce19c2a797929cacabd9e0fc936812fa","plugins\u002Fyagizdo\u002Fquiver\u002Fskills\u002Fbrainstorm",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":58,"prompt":68,"zipAvailable":69},[59,62,65],{"tool":60,"command":61},"npx","npx skills add hashgraph-online\u002Fawesome-codex-plugins --skill brainstorm",{"tool":63,"command":64},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill brainstorm",{"tool":66,"command":67},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill brainstorm","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fyagizdo\u002Fquiver\u002Fskills\u002Fbrainstorm\u002FSKILL.md",true,[71],{"path":72,"resourceType":73,"resourceTypeDesc":74,"sizeBytes":75,"sourceHtmlUrl":76},"TEST-PLAN.md","REFERENCE","参考文档",1419,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fyagizdo\u002Fquiver\u002Fskills\u002Fbrainstorm\u002FTEST-PLAN.md",[78,88,96,104,112,120],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":82,"licenseFileUrl":83,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":87},"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":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":82,"licenseFileUrl":92,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":87},"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":97,"name":98,"nameZh":6,"description":99,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":82,"licenseFileUrl":100,"sourceHtmlUrl":101,"categories":102,"keywords":103,"publishedAt":87},"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":105,"name":106,"nameZh":6,"description":107,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":82,"licenseFileUrl":108,"sourceHtmlUrl":109,"categories":110,"keywords":111,"publishedAt":87},"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":113,"name":114,"nameZh":6,"description":115,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":82,"licenseFileUrl":116,"sourceHtmlUrl":117,"categories":118,"keywords":119,"publishedAt":87},"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":121,"name":122,"nameZh":6,"description":123,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":82,"licenseFileUrl":124,"sourceHtmlUrl":125,"categories":126,"keywords":127,"publishedAt":87},"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",[],[]]