[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6C43PPMRMAAZ6NSB66KTP4Q":3,"skill-same:01M6C43PPMRMAAZ6NSB66KTP4Q":61},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":22,"publishedAt":35,"linkOnly":36,"markdownContent":37,"markdownBody":38,"frontMatter":39,"refName":40,"commitSha":41,"skillDirectory":42,"forksCount":43,"repositoryHtmlUrl":44,"repositoryHomepageUrl":6,"ownerHtmlUrl":45,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":46,"install":47,"resources":60},"01M6C43PPMRMAAZ6NSB66KTP4Q","brainstorming",null,"Structured Socratic questioning for exploring ideas and solutions. Use when exploring new features, evaluating approaches, or thinking through complex decisions. DO NOT USE FOR: architecture evaluation or SOLID analysis (use software-architecture), UI component design (use frontend-design), or coordinating implementation lanes (use parallel-execution).","Grimblaz\u002Fagent-orchestra","Grimblaz","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F74755849?v=4","01M6C430M9XZDHGHPWQVTQ3KMA","01M6C430RJY3MMX0QAZ3X8DR3Y",3,"MIT","https:\u002F\u002Fgithub.com\u002FGrimblaz\u002Fagent-orchestra\u002Fblob\u002Fmain\u002Fskills\u002Fbrainstorming\u002FSKILL.md",[17],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000009","前端开发","SCENARIO","使用场景",[5,23,24,25,26,27,28,29,30,31,32,33,34],"frontend","design","solid","component","architecture","ui","Evaluation","execution","analysis","parallel","decisions","use","2026-11-10 10:12:30",false,"---\nname: brainstorming\ndescription: \"Structured Socratic questioning for exploring ideas and solutions. Use when exploring new features, evaluating approaches, or thinking through complex decisions. DO NOT USE FOR: architecture evaluation or SOLID analysis (use software-architecture), UI component design (use frontend-design), or coordinating implementation lanes (use parallel-execution).\"\n---\n\n# Brainstorming Skill\n\nGuide for structured exploration of ideas through Socratic questioning.\n\n## When to Use\n\n- Exploring new feature ideas or requirements\n- Evaluating multiple solution approaches\n- Challenging assumptions about a problem\n- Breaking down complex decisions\n- Early-stage design discussions\n\n## Socratic Questioning Framework\n\n### 1. Clarifying Questions\n\n- What do you mean by...?\n- What is the core problem we're solving?\n- Can you give an example?\n- What would success look like?\n\n### 2. Probing Assumptions\n\n- What are we assuming here?\n- Why do we believe this is true?\n- What if the opposite were true?\n- What are we taking for granted?\n\n### 3. Exploring Perspectives\n\n- How would [stakeholder] view this?\n- What would a user expect?\n- What would a skeptic say?\n- How have others solved similar problems?\n\n### 4. Examining Evidence\n\n- What evidence supports this approach?\n- Are there counter-examples?\n- What data would change our mind?\n- How confident are we in this?\n\n### 5. Considering Consequences\n\n- What happens if we do this?\n- What are the second-order effects?\n- What could go wrong?\n- What's the cost of being wrong?\n\n### 6. Questioning the Question\n\n- Is this the right question to ask?\n- What question should we be asking instead?\n- Are we solving the right problem?\n\n## Brainstorming Session Structure\n\n```\n1. DEFINE (5 min)\n   - State the problem\u002Fopportunity clearly\n   - Identify constraints and goals\n\n2. DIVERGE (15 min)\n   - Generate many ideas without judgment\n   - Build on each other's ideas\n   - Encourage wild ideas\n\n3. CHALLENGE (10 min)\n   - Apply Socratic questions to top ideas\n   - Identify hidden assumptions\n   - Explore edge cases\n\n4. CONVERGE (10 min)\n   - Evaluate ideas against criteria\n   - Combine complementary approaches\n   - Select promising directions\n\n5. NEXT STEPS (5 min)\n   - Define concrete actions\n   - Assign owners and timelines\n```\n\n## Project-Specific Context\n\n[CUSTOMIZE] Add domain-specific questions relevant to your project:\n\n- Industry-specific considerations\n- Technical constraints unique to your stack\n- Stakeholder perspectives to consider\n- Common assumptions in your domain\n\n## Output Artifacts\n\nAfter brainstorming, document:\n\n1. Problem statement (refined)\n2. Key insights discovered\n3. Assumptions identified (and which were challenged)\n4. Top approaches with pros\u002Fcons\n5. Decision and rationale\n6. Open questions for future exploration\n\n## Gotchas\n\n| Trigger                                             | Gotcha                                                         | Fix                                                                                      |\n| --------------------------------------------------- | -------------------------------------------------------------- | ---------------------------------------------------------------------------------------- |\n| \"This approach seems good\" in the first few minutes | Premature convergence — first idea is never fully examined     | Enforce a DIVERGE phase before CONVERGE; exhaust alternatives before committing          |\n| Everyone agrees quickly with no pushback            | Groupthink — consensus silences better options                 | Assign devil's advocate; use §2 Probing Assumptions questions to challenge the consensus |\n| 30+ minutes of questioning with no decision         | Analysis paralysis — endless questioning without converging    | Time-box phases using the Session Structure; reach CONVERGE by minute 30                 |\n| Questions framed as \"Shouldn't we use X?\"           | Leading questions — forecloses alternatives before exploration | Rephrase as open questions per §1 Clarifying format (\"What are the options here?\")       |\n| Socratic questions met with defensiveness           | Defensive responses — posture shuts down exploration           | Frame questions as discovery, not criticism; restate the exploration goal                |\n","# Brainstorming Skill\n\nGuide for structured exploration of ideas through Socratic questioning.\n\n## When to Use\n\n- Exploring new feature ideas or requirements\n- Evaluating multiple solution approaches\n- Challenging assumptions about a problem\n- Breaking down complex decisions\n- Early-stage design discussions\n\n## Socratic Questioning Framework\n\n### 1. Clarifying Questions\n\n- What do you mean by...?\n- What is the core problem we're solving?\n- Can you give an example?\n- What would success look like?\n\n### 2. Probing Assumptions\n\n- What are we assuming here?\n- Why do we believe this is true?\n- What if the opposite were true?\n- What are we taking for granted?\n\n### 3. Exploring Perspectives\n\n- How would [stakeholder] view this?\n- What would a user expect?\n- What would a skeptic say?\n- How have others solved similar problems?\n\n### 4. Examining Evidence\n\n- What evidence supports this approach?\n- Are there counter-examples?\n- What data would change our mind?\n- How confident are we in this?\n\n### 5. Considering Consequences\n\n- What happens if we do this?\n- What are the second-order effects?\n- What could go wrong?\n- What's the cost of being wrong?\n\n### 6. Questioning the Question\n\n- Is this the right question to ask?\n- What question should we be asking instead?\n- Are we solving the right problem?\n\n## Brainstorming Session Structure\n\n```\n1. DEFINE (5 min)\n   - State the problem\u002Fopportunity clearly\n   - Identify constraints and goals\n\n2. DIVERGE (15 min)\n   - Generate many ideas without judgment\n   - Build on each other's ideas\n   - Encourage wild ideas\n\n3. CHALLENGE (10 min)\n   - Apply Socratic questions to top ideas\n   - Identify hidden assumptions\n   - Explore edge cases\n\n4. CONVERGE (10 min)\n   - Evaluate ideas against criteria\n   - Combine complementary approaches\n   - Select promising directions\n\n5. NEXT STEPS (5 min)\n   - Define concrete actions\n   - Assign owners and timelines\n```\n\n## Project-Specific Context\n\n[CUSTOMIZE] Add domain-specific questions relevant to your project:\n\n- Industry-specific considerations\n- Technical constraints unique to your stack\n- Stakeholder perspectives to consider\n- Common assumptions in your domain\n\n## Output Artifacts\n\nAfter brainstorming, document:\n\n1. Problem statement (refined)\n2. Key insights discovered\n3. Assumptions identified (and which were challenged)\n4. Top approaches with pros\u002Fcons\n5. Decision and rationale\n6. Open questions for future exploration\n\n## Gotchas\n\n| Trigger                                             | Gotcha                                                         | Fix                                                                                      |\n| --------------------------------------------------- | -------------------------------------------------------------- | ---------------------------------------------------------------------------------------- |\n| \"This approach seems good\" in the first few minutes | Premature convergence — first idea is never fully examined     | Enforce a DIVERGE phase before CONVERGE; exhaust alternatives before committing          |\n| Everyone agrees quickly with no pushback            | Groupthink — consensus silences better options                 | Assign devil's advocate; use §2 Probing Assumptions questions to challenge the consensus |\n| 30+ minutes of questioning with no decision         | Analysis paralysis — endless questioning without converging    | Time-box phases using the Session Structure; reach CONVERGE by minute 30                 |\n| Questions framed as \"Shouldn't we use X?\"           | Leading questions — forecloses alternatives before exploration | Rephrase as open questions per §1 Clarifying format (\"What are the options here?\")       |\n| Socratic questions met with defensiveness           | Defensive responses — posture shuts down exploration           | Frame questions as discovery, not criticism; restate the exploration goal                |\n",{"name":5,"description":7},"main","d5486aacc32c9ca1b07173cfd530f8fe75c29e58","skills\u002Fbrainstorming",0,"https:\u002F\u002Fgithub.com\u002FGrimblaz\u002Fagent-orchestra","https:\u002F\u002Fgithub.com\u002FGrimblaz","2026-08-16 01:12:46",{"source":8,"skillName":5,"commands":48,"prompt":58,"zipAvailable":59},[49,52,55],{"tool":50,"command":51},"npx","npx skills add Grimblaz\u002Fagent-orchestra --skill brainstorming",{"tool":53,"command":54},"bunx","bunx skills add Grimblaz\u002Fagent-orchestra --skill brainstorming",{"tool":56,"command":57},"pnpm","pnpm dlx skills add Grimblaz\u002Fagent-orchestra --skill brainstorming","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FGrimblaz\u002Fagent-orchestra\u002Fblob\u002Fmain\u002Fskills\u002Fbrainstorming\u002FSKILL.md",true,[],[62,90,115,131,159,177],{"skillNo":63,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":66,"categories":67,"keywords":72,"publishedAt":35},"01M6C48YMJVFHM7DVGG1WWW5RJ","webapp-testing","Playwright end-to-end testing guidance for web apps, with practical patterns and setup steps. Use when creating or improving browser-based E2E coverage, test stability, and CI execution. DO NOT USE FOR: React component tests (use ui-testing), canvas game interaction (use browser-canvas-testing), TDD workflow (use test-driven-development), debugging failures (use systematic-debugging), or randomized property tests (use property-based-testing).","https:\u002F\u002Fgithub.com\u002FGrimblaz\u002Fagent-orchestra\u002Fblob\u002Fmain\u002Fskills\u002Fwebapp-testing\u002FSKILL.md",[68,71],{"categoryNo":69,"categoryName":70,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},[73,74,75,76,77,78,79,80,81,82,26,83,84,85,86,30,87,88,89,34],"testing","webapp testing","webapp","canvas","tdd","workflow","playwright","test","web","react","debugging","development","browser","ci","e2e","game","coverage",{"skillNo":91,"name":92,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":94,"categories":95,"keywords":96,"publishedAt":35},"01M6C48TNNP2KCSQXV8YK7SK49","verification-before-completion","Evidence-based verification checklist before marking work complete. Use before PRs, releases, marking tickets done, or any \"I'm finished\" declaration; also when naming a baseline commit for a differential suite claim, when designing a mutation campaign or red-run evidence, when making an absence claim, a universal claim, or a one-time demonstration offered as a standing guarantee, when attributing a measurement or claiming a sweep or verification loop is complete, and when stating what a check or a CI suite will do about a change. DO NOT USE FOR: post-merge cleanup or archival (use post-pr-review) or processing GitHub review comments (use code-review-intake).","https:\u002F\u002Fgithub.com\u002FGrimblaz\u002Fagent-orchestra\u002Fblob\u002Fmain\u002Fskills\u002Fverification-before-completion\u002FSKILL.md",[],[97,98,99,100,101,102,103,104,105,106,107,108,86,109,110,111,112,34,113,114],"verification","verification before completion","review","change","commit","merge","pr","cleanup","run","code","code-review","intake","loop","verification loop","work","check","evidence","campaign",{"skillNo":116,"name":117,"nameZh":6,"description":118,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":119,"categories":120,"keywords":121,"publishedAt":35},"01M6C48QZWNTP7JGKD32QZAKKX","validation-methodology","Reusable validation and review methodology for staged validation, failure triage, and prosecution-depth setup. Use when running validation ladders, triaging failures, or executing adversarial review passes. DO NOT USE FOR: CE Gate orchestration, specialist dispatch ownership, or step execution flow (keep those in Code-Conductor).","https:\u002F\u002Fgithub.com\u002FGrimblaz\u002Fagent-orchestra\u002Fblob\u002Fmain\u002Fskills\u002Fvalidation-methodology\u002FSKILL.md",[],[122,123,124,99,125,126,127,128,106,129,30,34,130],"validation","methodology","validation methodology","triage","orchestration","setup","adversarial review","flow","dispatch",{"skillNo":132,"name":133,"nameZh":6,"description":134,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":135,"categories":136,"keywords":145,"publishedAt":35},"01M6C48MCAHG5Z79BJ369CRYRZ","upstream-onboarding","Shared opening-phase protocol for upstream agents (Experience-Owner, Solution-Designer, Issue-Planner) and Code-Conductor when invoked on an existing GitHub issue. Renders a scaled context brief and runs a standards check on inherited work at each phase boundary. Use when a user-invocable agent receives a request referencing an existing GitHub issue and must load solution-authoring and upstream-onboarding at the opening phase. DO NOT USE FOR: subagent dispatches (which already operate within an assessed session context); post-merge review (use post-pr-review); research or non-tree subagents.","https:\u002F\u002Fgithub.com\u002FGrimblaz\u002Fagent-orchestra\u002Fblob\u002Fmain\u002Fskills\u002Fupstream-onboarding\u002FSKILL.md",[137,140],{"categoryNo":138,"categoryName":139,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":141,"categoryName":142,"taxonomyType":143,"taxonomyTypeDesc":144},"01JBSEEDCAT000000000000038","人力资源","PROFESSION","适用职业",[146,147,99,148,149,102,150,103,106,151,152,153,154,155,156,111,112,157,158,34],"onboarding","upstream onboarding","github","research","standards check","protocol","brief","boundary","designer","subagent","planner","user","session",{"skillNo":160,"name":161,"nameZh":6,"description":162,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":163,"categories":164,"keywords":173,"publishedAt":35},"01M6C48GPVE120TGPMD1CS365H","ui-testing","Resilient React component testing strategies focusing on user behavior. Use when writing or reviewing component-level React tests, fixing flaky component tests, or establishing React testing patterns. DO NOT USE FOR: Playwright E2E tests (use webapp-testing), canvas game interaction (use browser-canvas-testing), TDD workflow (use test-driven-development), debugging failures (use systematic-debugging), UI component design (use frontend-design), or randomized property tests (use property-based-testing).","https:\u002F\u002Fgithub.com\u002FGrimblaz\u002Fagent-orchestra\u002Fblob\u002Fmain\u002Fskills\u002Fui-testing\u002FSKILL.md",[165,166,167,170],{"categoryNo":69,"categoryName":70,"taxonomyType":20,"taxonomyTypeDesc":21},{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},{"categoryNo":168,"categoryName":169,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000015","视觉设计",{"categoryNo":171,"categoryName":172,"taxonomyType":143,"taxonomyTypeDesc":144},"01JBSEEDCAT000000000000032","设计师",[73,28,174,23,24,175,76,78,79,80,82,26,83,84,85,176,87,88,34,75],"ui testing","writing","testing patterns",{"skillNo":178,"name":179,"nameZh":6,"description":180,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":181,"categories":182,"keywords":185,"publishedAt":35},"01M6C48DRJ9XBDR2FW0W37DY53","ui-iteration","Reusable screenshot-driven UI polish workflow for iterative visual refinement. Use when improving layout, hierarchy, spacing, feedback, or Tailwind-based presentation through repeated review-and-adjust passes. DO NOT USE FOR: functional bug fixing, accessibility-only audits, or major redesign strategy work (use Code-Smith or frontend-design).","https:\u002F\u002Fgithub.com\u002FGrimblaz\u002Fagent-orchestra\u002Fblob\u002Fmain\u002Fskills\u002Fui-iteration\u002FSKILL.md",[183,184],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},{"categoryNo":171,"categoryName":172,"taxonomyType":143,"taxonomyTypeDesc":144},[28,186,23,24,99,78,187,106,188,189,190,191,192,111,193,194,34,195],"ui iteration","accessibility","screenshot","Tailwind","polish","ui polish","feedback","redesign","strategy","only"]