[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6JVP8BH3Q89SETF8B8DWB66":3,"skill-same:01M6JVP8BH3Q89SETF8B8DWB66":97},{"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":54,"linkOnly":55,"markdownContent":56,"markdownBody":57,"frontMatter":58,"refName":59,"commitSha":60,"skillDirectory":61,"forksCount":62,"repositoryHtmlUrl":63,"repositoryHomepageUrl":64,"ownerHtmlUrl":65,"ownerBlogUrl":66,"ownerDescription":67,"updatedAt":68,"install":69,"resources":82},"01M6JVP8BH3Q89SETF8B8DWB66","brainstorming",null,"Use when defining ambiguous or high-complexity new features, product behavior, UI\u002Fcomponent design, architecture choices, contract changes, or when grilling\u002Fpressure-testing a plan or design. Routine small requests stay on the fast path.","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\u002FGanyuanRan\u002FAegis\u002Fskills\u002Fbrainstorming\u002FSKILL.md",[18,23,28],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000015","视觉设计","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000032","设计师","PROFESSION","适用职业",{"categoryNo":29,"categoryName":30,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000037","律师与法务",[5,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48,49,50,51,52,53],"contract","routine","ambiguous","when","new","grilling","fast","behavior","requests","high","changes","use","path","ui","features","product","component","plan","architecture","design","testing","complexity","2026-11-10 10:12:30",false,"---\nname: brainstorming\ndescription: \"Use when defining ambiguous or high-complexity new features, product behavior, UI\u002Fcomponent design, architecture choices, contract changes, or when grilling\u002Fpressure-testing a plan or design. Routine small requests stay on the fast path.\"\n---\n\n\u003CEXPLICIT-MODE-GATE>\nIf activation mode is explicit (`~\u002F.config\u002Faegis\u002Fconfig.toml` has\n`activation_mode = \"explicit\"`, or `AEGIS_ACTIVATION_MODE=explicit` is visible\nin the environment) and the current user request did not explicitly invoke\nAegis or this skill by name, exit back to the fast path: answer concisely\nwithout this workflow's checklist, ceremony, or document requirements. If the\nuser explicitly named Aegis or this skill, proceed normally.\n\u003C\u002FEXPLICIT-MODE-GATE>\n\n# Execute\n\nChoose the route before reading references:\n\n1. Tiny wording edits, simple Q&A\u002Fstatus, local utility or mechanical changes\n   stay on the fast path. Bugs\u002Fdiagnosis use `systematic-debugging`; PR, diff,\n   or current-code review uses `requesting-code-review`; explicit goal framing\n   uses `goal-framing`. File count alone does not decide design complexity.\n2. Direct interview requests use `Grilling Mode` below; soft challenge intent\n   requires its one-line mode confirmation. Ordinary evaluation is not grilling.\n3. Ambiguous or medium\u002Fhigh-complexity feature, product, UI, architecture or\n   contract design follows `Default Design Path`. Escalate depth from evidence:\n   contracts, owners, persistence, migration, security, consumers and blast radius.\n\n\u003CHARD-GATE>\nDo NOT write code, scaffold projects, or invoke implementation skills until the\nneeded design\u002Fspec approval is satisfied. Existing approval satisfies unchanged\ndecisions; clarify only decision-changing gaps. Grilling never authorizes\nimplementation or normal design artifacts while the interview is active.\n\u003C\u002FHARD-GATE>\n\n## Route Fixtures\n\nThese rows are calibration expectations for method behavior, not a runtime\nregex router. The Agent selects the route from evidence; route selection is\nnot a user question.\n\n| Scenario | Route |\n| --- | --- |\n| 想法还没想清楚，先梳理功能设计 | normal brainstorming, compact output first |\n| 讨论公共 API 契约和兼容边界 | normal brainstorming, design sections before implementation |\n| 盘问\u002F拷问\u002F审问这个方案，不要顺着我 | `Grilling Mode` |\n| 修复登录按钮的空指针 | `systematic-debugging` |\n| review 当前 PR \u002F diff \u002F 当前代码 | `requesting-code-review` |\n| 给我一个有目标的方案 | `goal-framing` when goal intent is explicit; otherwise normal brainstorming |\n| 把按钮文案从保存改成提交 | fast-path; no design ceremony |\n\n## Grilling Mode\n\n### Grilling Entry Signals\n\n- **Direct:** `grill me`, `grill this plan`, `审问我`, `盘问我`, `拷问我`, or an\n  explicit request to interrogate\u002Fpressure-test a plan enters this mode.\n- **Soft:** challenge assumptions, find holes, red-team, or \"别顺着我\" without\n  explicit interview intent: ask only `Grill or normal brainstorming?` and\n  enter only after confirmation.\n- **Not grilling:** literal phrase explanations stay explanatory; PR, diff, or current-code review routes to `requesting-code-review`.\n\nGrilling Mode overrides the normal brainstorming execution flow. Suspend the\nDefault Design Path, compact output contract, and documentation or planning\nrequirements until the user exits the interview; retain the no-implementation\ngate. Only after entry, read `grilling-mode-reference.md` for interview pace,\nopening, questions and exit procedure. Do not read it for ordinary design,\nsoft-intent confirmation, or literal phrase explanations.\nStop the interview when the user says stop, defer, or that questions are\nsufficient. Its summary does not authorize planning or implementation; return\nto the normal design approval gate if the user asks to proceed.\n\n## Default Design Path\n\nTrack the applicable steps in order; conditional steps do not create tasks or\nartifacts until their trigger is met. Keep one workflow, not separate checklist,\nprocess and after-design passes.\n\n1. **Ground the request.** Inspect current files, relevant authority docs and\n   recent changes. Passively use active `CONTEXT.md`\u002F`CONTEXT-MAP.md` terms;\n   compose `establishing-project-context` only for a real semantic conflict.\n   Decompose independent subsystems before designing them. Define the user's\n   usable result, delivery and meaningful failure states; an unsupported action\n   remains an unmet need, not a reason to silently narrow the requirement.\n2. **Clarify decision-changing gaps.** Follow the authority contract below.\n   Ask one question at a time, preferably with choices and a recommendation.\n   Reuse answers and approvals; do not ask the user for repository facts.\n3. **Frame scope and alternatives.** Maintain the working drafts below, propose\n   2-3 approaches with trade-offs and a recommendation, and say what is in,\n   deferred or owned elsewhere. Apply only evidence-triggered checks from the\n   conditional table before recommending the approach.\n4. **Present the design.** Scale sections to complexity: affected architecture,\n   components\u002Fdata flow, failure\u002Frecovery, consumers, compatibility and testing.\n   Follow existing patterns; keep each unit cohesive and testable, and remove\n   unnecessary features. Obtain required approval for each applicable design\n   section before proceeding; return to clarification when evidence changes it.\n5. **Persist only when needed.** Apply the Doc Necessity Gate. For a written\n   Design Spec, load the self-review section, fix placeholders, contradictions,\n   ambiguity, scope and boundary defects, then obtain user review. A small Spec\n   Brief may use concise review unless project authority requires a formal gate.\n6. **Hand off only when ready.** Check Design Ready And Design Complete below;\n   preserve ADR signals for durable owner\u002Fcontract\u002Fschema\u002Fdependency\u002Fcompatibility\u002F\n   runtime-boundary changes, including source refs, alternatives and baseline-sync\n   questions. Do not create accepted architecture memory from unexecuted ideas.\n   The terminal state is invoking `writing-plans`, not another implementation\n   skill. For a scope ending at discussion or options, deliver that result;\n   do not advance beyond the user's request.\n\n## Compact output contract\n\nUse natural, proportional prose, not a mandatory stack of named cards.\n`Aegis Visibility` briefly explains the task-specific value of design first.\nKeep these working drafts current as scope changes; they are in-session views\nunless the Doc Necessity Gate requires persistence:\n\n- `TaskIntentDraft`: outcome, goal, success evidence, stop condition, non-goals,\n  scope and risks;\n- `BaselineReadSetHint`: candidate authority refs and gaps;\n- `BaselineUsageDraft`: required, delivered-context (optional), acknowledged,\n  cited and missing refs, plus the advisory decision;\n- `ImpactStatementDraft`: affected layers, owners, invariants, compatibility\n  and non-goals.\n\nPresent the relevant intent, evidence, impact, options and decision needed at\nthis stage. Conditional lenses below add only their applicable findings;\nmentioning a lens does not activate its template. Do not repeat satisfied checks\nor emit empty cards. Preserve decision-relevant meaning and evidence limits.\n\n## Doc Necessity Gate\n\nBefore writing any spec, plan, ADR or baseline artifact:\n\n1. If an existing spec\u002Fplan\u002FADR\u002Fbaseline owns this surface, update it in place;\n   never create a sibling owner.\n2. Write the smallest artifact only for a durable\u002Firreversible surface (schema,\n   public API, owner, dependency, migration, compatibility retirement), cross-session\u002F\n   cross-person handoff, or an approval\u002Fauthority requirement. Otherwise keep\n   compact drafts in-session and write no document.\n3. Re-check at edit time and closeout; expand only if uncertainty or impact grows.\n   Workspace creation and spec persistence follow project authority. Read the\n   workspace\u002Fbootstrap reference only after selecting a durable artifact.\n\n## Role And Authority Contract\n\n### Agent-owned decisions\n\nResolve these directly without asking the user:\n\n- repository investigation strategy and evidence gathering order\n- file and function organization inside an accepted owner\n- testing commands and proportional verification mechanics\n- inline versus subagent execution when policy already allows it\n- reversible implementation structure that does not change product behavior,\n  contract, authority, or durable boundaries\n\n### User-owned decisions\n\nAsk the user only for:\n\n- product behavior or preference\n- irreversible, destructive, external, public, production, or sensitive impact\n- explicit product\u002Fcontract commitments only the user can make\n- necessary information unavailable from repository, tools, and authority docs\n\nEvery user question must pass this test:\n\n> If the user chooses another answer, which design boundary, behavior, owner,\n> acceptance criterion, or risk decision changes?\n\nIf none changes, do not ask. When a question passes this test,\nattach a recommended option and the reason for it, so the user decides\nbetween framed choices instead of researching. This classification clarifies which decisions\nare user-owned; it does not remove the approval points this workflow already\ndefines.\n\n## Conditional Detailed Guidance\n\nFor design detail, read only the evidence-matched heading of\n`expanded-design-guidance.md`, never the whole file. Do not load design detail\nfor route selection, first-turn clarification, route-away cases, or an active\nGrilling Mode interview. The main file owns routing, approval and handoff;\nreferences supply the selected procedure or template only.\n\n| Evidence trigger | Exact section to read \u002F action |\n| --- | --- |\n| Repository evidence is insufficient and a bounded probe can change the approach | `## Design Probe` |\n| The software scenario class is known and its domain risks matter | `## Software Scenario Profiles`; use only the relevant profile |\n| Doc Necessity Gate selects a spec\u002Fworkspace artifact | `## Documentation And Workspace Bootstrap`; a named baseline template only when initializing that exact file |\n| A written Design Spec is ready for review | `## Spec Self-Review` |\n| A baseline-dependent recommendation needs structured usage evidence | `### Baseline Usage Draft` under `## Design Artifact Templates` |\n| Requirements, scenarios or acceptance remain incomplete or disputed before a design recommendation | `### Requirement Ready Check`; stay at proposal\u002Fspec clarification until decision-changing gaps are resolved |\n| An approach introduces an owner, skill, artifact, adapter, fallback, compatibility path, workflow step or metric | `### Existence Check`; reuse the existing owner when sufficient |\n| Ambiguous product, feature, workflow or architecture choices | `### Product Risk Lens`; keep value, non-goals, trade-offs and the decision compact |\n| Choosing a medium\u002Fhigh-complexity implementation direction | `### Plan-Time Complexity Check And Complexity Budget`; inspect actual owners\u002Ffile shape before choosing |\n| Novel mechanism, protocol, artifact or interaction; unresolved alternatives after internal reuse checks; domain outside repository evidence | `### Prior-Art And Reuse Lens` (Prior-Art & Reuse Lens); routine established patterns need no external research ceremony |\n| Both what to build and where it belongs are at issue | `### Baseline Role Alignment`; distinguish requirement truth from architecture truth |\n\nBefore approach selection, unresolved new\u002Fduplicate owners, fallback, adapter,\ncompat-only carrier, delete-first questions, unverified assumptions or a\n\"long-term stable\" claim after Existence Check escalate to\n`first-principles-review` and its `Decision Hygiene Review`; return here once\nthat decision surface is clean. Do not make this a universal design ceremony.\n\nFor narrower architecture coherence risks, use `Architecture Integrity Lens`:\ninvariant, canonical owner\u002Fcontract, responsibility overlap, higher-level\nsimplification, retirement\u002Ffalsifier and verdict. For internal retirement vs\ncompatibility retention vs persistent-state confirmation, compose `anti-entropy-governance`;\nit chooses `delete-first | compat-exception | confirmation-first` without\ntransferring destructive authority to this skill.\n\nFor user-facing interface or interaction design, compose `ui-ux-governance` and\ncarry scoped experience rules into existing acceptance criteria. Design approval\nand handoff remain here.\n\n## Design Ready And Design Complete\n\nApproach selection is ready when:\n\n- the desired outcome and primary scenario are known;\n- scope and non-goals are explicit;\n- current behavior and the target delta are grounded;\n- key invariants and the likely canonical owner are identified;\n- at least one observable acceptance criterion exists;\n- no open unknown can still change the approach category.\n\nNot every unknown must be eliminated; only decision-changing unknowns block\nconvergence.\n\nThe design can hand off when all applicable conditions hold:\n\n- the selected approach and canonical owner are explicit;\n- fixed behavior\u002Fcontract and implementation-owned choices are separated;\n- alternatives were materially compared or excluded by evidence;\n- critical assumptions have evidence or explicit acceptance;\n- failure\u002Frecovery and consumer impact are covered where applicable;\n- acceptance criteria are observable and usable by verification;\n- new owners, fallbacks, adapters, compatibility, or persistence have creation\n  proof and retirement\u002Frollback treatment;\n- every user-owned decision has real user approval.\n\nDesign Complete is method readiness, not completion authority. Transition to\nwriting-plans only after these conditions hold; do not carry unresolved\ndecision-changing unknowns into the plan.\n","\u003CEXPLICIT-MODE-GATE>\nIf activation mode is explicit (`~\u002F.config\u002Faegis\u002Fconfig.toml` has\n`activation_mode = \"explicit\"`, or `AEGIS_ACTIVATION_MODE=explicit` is visible\nin the environment) and the current user request did not explicitly invoke\nAegis or this skill by name, exit back to the fast path: answer concisely\nwithout this workflow's checklist, ceremony, or document requirements. If the\nuser explicitly named Aegis or this skill, proceed normally.\n\u003C\u002FEXPLICIT-MODE-GATE>\n\n# Execute\n\nChoose the route before reading references:\n\n1. Tiny wording edits, simple Q&A\u002Fstatus, local utility or mechanical changes\n   stay on the fast path. Bugs\u002Fdiagnosis use `systematic-debugging`; PR, diff,\n   or current-code review uses `requesting-code-review`; explicit goal framing\n   uses `goal-framing`. File count alone does not decide design complexity.\n2. Direct interview requests use `Grilling Mode` below; soft challenge intent\n   requires its one-line mode confirmation. Ordinary evaluation is not grilling.\n3. Ambiguous or medium\u002Fhigh-complexity feature, product, UI, architecture or\n   contract design follows `Default Design Path`. Escalate depth from evidence:\n   contracts, owners, persistence, migration, security, consumers and blast radius.\n\n\u003CHARD-GATE>\nDo NOT write code, scaffold projects, or invoke implementation skills until the\nneeded design\u002Fspec approval is satisfied. Existing approval satisfies unchanged\ndecisions; clarify only decision-changing gaps. Grilling never authorizes\nimplementation or normal design artifacts while the interview is active.\n\u003C\u002FHARD-GATE>\n\n## Route Fixtures\n\nThese rows are calibration expectations for method behavior, not a runtime\nregex router. The Agent selects the route from evidence; route selection is\nnot a user question.\n\n| Scenario | Route |\n| --- | --- |\n| 想法还没想清楚，先梳理功能设计 | normal brainstorming, compact output first |\n| 讨论公共 API 契约和兼容边界 | normal brainstorming, design sections before implementation |\n| 盘问\u002F拷问\u002F审问这个方案，不要顺着我 | `Grilling Mode` |\n| 修复登录按钮的空指针 | `systematic-debugging` |\n| review 当前 PR \u002F diff \u002F 当前代码 | `requesting-code-review` |\n| 给我一个有目标的方案 | `goal-framing` when goal intent is explicit; otherwise normal brainstorming |\n| 把按钮文案从保存改成提交 | fast-path; no design ceremony |\n\n## Grilling Mode\n\n### Grilling Entry Signals\n\n- **Direct:** `grill me`, `grill this plan`, `审问我`, `盘问我`, `拷问我`, or an\n  explicit request to interrogate\u002Fpressure-test a plan enters this mode.\n- **Soft:** challenge assumptions, find holes, red-team, or \"别顺着我\" without\n  explicit interview intent: ask only `Grill or normal brainstorming?` and\n  enter only after confirmation.\n- **Not grilling:** literal phrase explanations stay explanatory; PR, diff, or current-code review routes to `requesting-code-review`.\n\nGrilling Mode overrides the normal brainstorming execution flow. Suspend the\nDefault Design Path, compact output contract, and documentation or planning\nrequirements until the user exits the interview; retain the no-implementation\ngate. Only after entry, read `grilling-mode-reference.md` for interview pace,\nopening, questions and exit procedure. Do not read it for ordinary design,\nsoft-intent confirmation, or literal phrase explanations.\nStop the interview when the user says stop, defer, or that questions are\nsufficient. Its summary does not authorize planning or implementation; return\nto the normal design approval gate if the user asks to proceed.\n\n## Default Design Path\n\nTrack the applicable steps in order; conditional steps do not create tasks or\nartifacts until their trigger is met. Keep one workflow, not separate checklist,\nprocess and after-design passes.\n\n1. **Ground the request.** Inspect current files, relevant authority docs and\n   recent changes. Passively use active `CONTEXT.md`\u002F`CONTEXT-MAP.md` terms;\n   compose `establishing-project-context` only for a real semantic conflict.\n   Decompose independent subsystems before designing them. Define the user's\n   usable result, delivery and meaningful failure states; an unsupported action\n   remains an unmet need, not a reason to silently narrow the requirement.\n2. **Clarify decision-changing gaps.** Follow the authority contract below.\n   Ask one question at a time, preferably with choices and a recommendation.\n   Reuse answers and approvals; do not ask the user for repository facts.\n3. **Frame scope and alternatives.** Maintain the working drafts below, propose\n   2-3 approaches with trade-offs and a recommendation, and say what is in,\n   deferred or owned elsewhere. Apply only evidence-triggered checks from the\n   conditional table before recommending the approach.\n4. **Present the design.** Scale sections to complexity: affected architecture,\n   components\u002Fdata flow, failure\u002Frecovery, consumers, compatibility and testing.\n   Follow existing patterns; keep each unit cohesive and testable, and remove\n   unnecessary features. Obtain required approval for each applicable design\n   section before proceeding; return to clarification when evidence changes it.\n5. **Persist only when needed.** Apply the Doc Necessity Gate. For a written\n   Design Spec, load the self-review section, fix placeholders, contradictions,\n   ambiguity, scope and boundary defects, then obtain user review. A small Spec\n   Brief may use concise review unless project authority requires a formal gate.\n6. **Hand off only when ready.** Check Design Ready And Design Complete below;\n   preserve ADR signals for durable owner\u002Fcontract\u002Fschema\u002Fdependency\u002Fcompatibility\u002F\n   runtime-boundary changes, including source refs, alternatives and baseline-sync\n   questions. Do not create accepted architecture memory from unexecuted ideas.\n   The terminal state is invoking `writing-plans`, not another implementation\n   skill. For a scope ending at discussion or options, deliver that result;\n   do not advance beyond the user's request.\n\n## Compact output contract\n\nUse natural, proportional prose, not a mandatory stack of named cards.\n`Aegis Visibility` briefly explains the task-specific value of design first.\nKeep these working drafts current as scope changes; they are in-session views\nunless the Doc Necessity Gate requires persistence:\n\n- `TaskIntentDraft`: outcome, goal, success evidence, stop condition, non-goals,\n  scope and risks;\n- `BaselineReadSetHint`: candidate authority refs and gaps;\n- `BaselineUsageDraft`: required, delivered-context (optional), acknowledged,\n  cited and missing refs, plus the advisory decision;\n- `ImpactStatementDraft`: affected layers, owners, invariants, compatibility\n  and non-goals.\n\nPresent the relevant intent, evidence, impact, options and decision needed at\nthis stage. Conditional lenses below add only their applicable findings;\nmentioning a lens does not activate its template. Do not repeat satisfied checks\nor emit empty cards. Preserve decision-relevant meaning and evidence limits.\n\n## Doc Necessity Gate\n\nBefore writing any spec, plan, ADR or baseline artifact:\n\n1. If an existing spec\u002Fplan\u002FADR\u002Fbaseline owns this surface, update it in place;\n   never create a sibling owner.\n2. Write the smallest artifact only for a durable\u002Firreversible surface (schema,\n   public API, owner, dependency, migration, compatibility retirement), cross-session\u002F\n   cross-person handoff, or an approval\u002Fauthority requirement. Otherwise keep\n   compact drafts in-session and write no document.\n3. Re-check at edit time and closeout; expand only if uncertainty or impact grows.\n   Workspace creation and spec persistence follow project authority. Read the\n   workspace\u002Fbootstrap reference only after selecting a durable artifact.\n\n## Role And Authority Contract\n\n### Agent-owned decisions\n\nResolve these directly without asking the user:\n\n- repository investigation strategy and evidence gathering order\n- file and function organization inside an accepted owner\n- testing commands and proportional verification mechanics\n- inline versus subagent execution when policy already allows it\n- reversible implementation structure that does not change product behavior,\n  contract, authority, or durable boundaries\n\n### User-owned decisions\n\nAsk the user only for:\n\n- product behavior or preference\n- irreversible, destructive, external, public, production, or sensitive impact\n- explicit product\u002Fcontract commitments only the user can make\n- necessary information unavailable from repository, tools, and authority docs\n\nEvery user question must pass this test:\n\n> If the user chooses another answer, which design boundary, behavior, owner,\n> acceptance criterion, or risk decision changes?\n\nIf none changes, do not ask. When a question passes this test,\nattach a recommended option and the reason for it, so the user decides\nbetween framed choices instead of researching. This classification clarifies which decisions\nare user-owned; it does not remove the approval points this workflow already\ndefines.\n\n## Conditional Detailed Guidance\n\nFor design detail, read only the evidence-matched heading of\n`expanded-design-guidance.md`, never the whole file. Do not load design detail\nfor route selection, first-turn clarification, route-away cases, or an active\nGrilling Mode interview. The main file owns routing, approval and handoff;\nreferences supply the selected procedure or template only.\n\n| Evidence trigger | Exact section to read \u002F action |\n| --- | --- |\n| Repository evidence is insufficient and a bounded probe can change the approach | `## Design Probe` |\n| The software scenario class is known and its domain risks matter | `## Software Scenario Profiles`; use only the relevant profile |\n| Doc Necessity Gate selects a spec\u002Fworkspace artifact | `## Documentation And Workspace Bootstrap`; a named baseline template only when initializing that exact file |\n| A written Design Spec is ready for review | `## Spec Self-Review` |\n| A baseline-dependent recommendation needs structured usage evidence | `### Baseline Usage Draft` under `## Design Artifact Templates` |\n| Requirements, scenarios or acceptance remain incomplete or disputed before a design recommendation | `### Requirement Ready Check`; stay at proposal\u002Fspec clarification until decision-changing gaps are resolved |\n| An approach introduces an owner, skill, artifact, adapter, fallback, compatibility path, workflow step or metric | `### Existence Check`; reuse the existing owner when sufficient |\n| Ambiguous product, feature, workflow or architecture choices | `### Product Risk Lens`; keep value, non-goals, trade-offs and the decision compact |\n| Choosing a medium\u002Fhigh-complexity implementation direction | `### Plan-Time Complexity Check And Complexity Budget`; inspect actual owners\u002Ffile shape before choosing |\n| Novel mechanism, protocol, artifact or interaction; unresolved alternatives after internal reuse checks; domain outside repository evidence | `### Prior-Art And Reuse Lens` (Prior-Art & Reuse Lens); routine established patterns need no external research ceremony |\n| Both what to build and where it belongs are at issue | `### Baseline Role Alignment`; distinguish requirement truth from architecture truth |\n\nBefore approach selection, unresolved new\u002Fduplicate owners, fallback, adapter,\ncompat-only carrier, delete-first questions, unverified assumptions or a\n\"long-term stable\" claim after Existence Check escalate to\n`first-principles-review` and its `Decision Hygiene Review`; return here once\nthat decision surface is clean. Do not make this a universal design ceremony.\n\nFor narrower architecture coherence risks, use `Architecture Integrity Lens`:\ninvariant, canonical owner\u002Fcontract, responsibility overlap, higher-level\nsimplification, retirement\u002Ffalsifier and verdict. For internal retirement vs\ncompatibility retention vs persistent-state confirmation, compose `anti-entropy-governance`;\nit chooses `delete-first | compat-exception | confirmation-first` without\ntransferring destructive authority to this skill.\n\nFor user-facing interface or interaction design, compose `ui-ux-governance` and\ncarry scoped experience rules into existing acceptance criteria. Design approval\nand handoff remain here.\n\n## Design Ready And Design Complete\n\nApproach selection is ready when:\n\n- the desired outcome and primary scenario are known;\n- scope and non-goals are explicit;\n- current behavior and the target delta are grounded;\n- key invariants and the likely canonical owner are identified;\n- at least one observable acceptance criterion exists;\n- no open unknown can still change the approach category.\n\nNot every unknown must be eliminated; only decision-changing unknowns block\nconvergence.\n\nThe design can hand off when all applicable conditions hold:\n\n- the selected approach and canonical owner are explicit;\n- fixed behavior\u002Fcontract and implementation-owned choices are separated;\n- alternatives were materially compared or excluded by evidence;\n- critical assumptions have evidence or explicit acceptance;\n- failure\u002Frecovery and consumer impact are covered where applicable;\n- acceptance criteria are observable and usable by verification;\n- new owners, fallbacks, adapters, compatibility, or persistence have creation\n  proof and retirement\u002Frollback treatment;\n- every user-owned decision has real user approval.\n\nDesign Complete is method readiness, not completion authority. Transition to\nwriting-plans only after these conditions hold; do not carry unresolved\ndecision-changing unknowns into the plan.\n",{"name":5,"description":7},"main","cebc3dce495d7eb80d3b1d5841f877a4a92e162d","plugins\u002FGanyuanRan\u002FAegis\u002Fskills\u002Fbrainstorming",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":70,"prompt":80,"zipAvailable":81},[71,74,77],{"tool":72,"command":73},"npx","npx skills add hashgraph-online\u002Fawesome-codex-plugins --skill brainstorming",{"tool":75,"command":76},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill brainstorming",{"tool":78,"command":79},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill brainstorming","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FGanyuanRan\u002FAegis\u002Fskills\u002Fbrainstorming\u002FSKILL.md",true,[83,89,93],{"path":84,"resourceType":85,"resourceTypeDesc":86,"sizeBytes":87,"sourceHtmlUrl":88},"expanded-design-guidance.md","REFERENCE","参考文档",16093,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FGanyuanRan\u002FAegis\u002Fskills\u002Fbrainstorming\u002Fexpanded-design-guidance.md",{"path":90,"resourceType":85,"resourceTypeDesc":86,"sizeBytes":91,"sourceHtmlUrl":92},"grilling-mode-reference.md",2207,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FGanyuanRan\u002FAegis\u002Fskills\u002Fbrainstorming\u002Fgrilling-mode-reference.md",{"path":94,"resourceType":85,"resourceTypeDesc":86,"sizeBytes":95,"sourceHtmlUrl":96},"spec-document-reviewer-prompt.md",1742,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FGanyuanRan\u002FAegis\u002Fskills\u002Fbrainstorming\u002Fspec-document-reviewer-prompt.md",[98,108,116,124,132,140],{"skillNo":99,"name":100,"nameZh":6,"description":101,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":102,"licenseFileUrl":103,"sourceHtmlUrl":104,"categories":105,"keywords":106,"publishedAt":107},"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":109,"name":110,"nameZh":6,"description":111,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":102,"licenseFileUrl":112,"sourceHtmlUrl":113,"categories":114,"keywords":115,"publishedAt":107},"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":117,"name":118,"nameZh":6,"description":119,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":102,"licenseFileUrl":120,"sourceHtmlUrl":121,"categories":122,"keywords":123,"publishedAt":107},"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":125,"name":126,"nameZh":6,"description":127,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":102,"licenseFileUrl":128,"sourceHtmlUrl":129,"categories":130,"keywords":131,"publishedAt":107},"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":133,"name":134,"nameZh":6,"description":135,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":102,"licenseFileUrl":136,"sourceHtmlUrl":137,"categories":138,"keywords":139,"publishedAt":107},"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":141,"name":142,"nameZh":6,"description":143,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":102,"licenseFileUrl":144,"sourceHtmlUrl":145,"categories":146,"keywords":147,"publishedAt":107},"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",[],[]]