[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71C1EEF68H4B06NP6A8BWD8":3,"skill-same:01M71C1EEF68H4B06NP6A8BWD8":68},{"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":35,"linkOnly":36,"markdownContent":37,"markdownBody":38,"frontMatter":39,"refName":41,"commitSha":42,"skillDirectory":43,"forksCount":14,"repositoryHtmlUrl":44,"repositoryHomepageUrl":6,"ownerHtmlUrl":45,"ownerBlogUrl":6,"ownerDescription":46,"updatedAt":47,"install":48,"resources":61},"01M71C1EEF68H4B06NP6A8BWD8","brainstorming",null,"Socratic questioning protocol + user communication. MANDATORY for complex requests, new features, or unclear requirements. Includes progress reporting and error handling.","yqecea\u002Fgem-swarm","yqecea","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F196189405?v=4","01M71C12KWH5QPTE12J69335KF","Yusuf","01M71C12MFS3BRGNE5SSHB4DY9",1,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fyqecea\u002Fgem-swarm\u002Fblob\u002Fmain\u002Fsrc\u002Fskills\u002Fdomain\u002Fbrainstorming\u002FSKILL.md",[],[5,19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34],"communication","user","grep","protocol","features","reporting","read","socratic questioning","requests","progress","socratic","error handling","requirements","new","for","error","2026-11-10 10:12:30",false,"---\nname: brainstorming\ndescription: Socratic questioning protocol + user communication. MANDATORY for complex requests, new features, or unclear requirements. Includes progress reporting and error handling.\nallowed-tools: Read, Glob, Grep\n---\n\n# Brainstorming & Communication Protocol\n\n> **MANDATORY:** Use for complex\u002Fvague requests, new features, updates.\n\n---\n\n## 🛑 SOCRATIC GATE (ENFORCEMENT)\n\n### When to Trigger\n\n| Pattern | Action |\n|---------|--------|\n| \"Build\u002FCreate\u002FMake [thing]\" without details | 🛑 ASK 3 questions |\n| Complex feature or architecture | 🛑 Clarify before implementing |\n| Update\u002Fchange request | 🛑 Confirm scope |\n| Vague requirements | 🛑 Ask purpose, users, constraints |\n\n### 🚫 MANDATORY: 3 Questions Before Implementation\n\n1. **STOP** - Do NOT start coding\n2. **ASK** - Minimum 3 questions:\n   - 🎯 Purpose: What problem are you solving?\n   - 👥 Users: Who will use this?\n   - 📦 Scope: Must-have vs nice-to-have?\n3. **WAIT** - Get response before proceeding\n\n---\n\n## 🧠 Dynamic Question Generation\n\n**⛔ NEVER use static templates.** Read `dynamic-questioning.md` for principles.\n\n### Core Principles\n\n| Principle | Meaning |\n|-----------|---------|\n| **Questions Reveal Consequences** | Each question connects to an architectural decision |\n| **Context Before Content** | Understand greenfield\u002Ffeature\u002Frefactor\u002Fdebug context first |\n| **Minimum Viable Questions** | Each question must eliminate implementation paths |\n| **Generate Data, Not Assumptions** | Don't guess—ask with trade-offs |\n\n### Question Generation Process\n\n```\n1. Parse request → Extract domain, features, scale indicators\n2. Identify decision points → Blocking vs. deferable\n3. Generate questions → Priority: P0 (blocking) > P1 (high-leverage) > P2 (nice-to-have)\n4. Format with trade-offs → What, Why, Options, Default\n```\n\n### Question Format (MANDATORY)\n\n```markdown\n### [PRIORITY] **[DECISION POINT]**\n\n**Question:** [Clear question]\n\n**Why This Matters:**\n- [Architectural consequence]\n- [Affects: cost\u002Fcomplexity\u002Ftimeline\u002Fscale]\n\n**Options:**\n| Option | Pros | Cons | Best For |\n|--------|------|------|----------|\n| A | [+] | [-] | [Use case] |\n\n**If Not Specified:** [Default + rationale]\n```\n\n**For detailed domain-specific question banks and algorithms**, see: `dynamic-questioning.md`\n\n---\n\n## Progress Reporting (PRINCIPLE-BASED)\n\n**PRINCIPLE:** Transparency builds trust. Status must be visible and actionable.\n\n### Status Board Format\n\n| Agent | Status | Current Task | Progress |\n|-------|--------|--------------|----------|\n| [Agent Name] | ✅🔄⏳❌⚠️ | [Task description] | [% or count] |\n\n### Status Icons\n\n| Icon | Meaning | Usage |\n|------|---------|-------|\n| ✅ | Completed | Task finished successfully |\n| 🔄 | Running | Currently executing |\n| ⏳ | Waiting | Blocked, waiting for dependency |\n| ❌ | Error | Failed, needs attention |\n| ⚠️ | Warning | Potential issue, not blocking |\n\n---\n\n## Error Handling (PRINCIPLE-BASED)\n\n**PRINCIPLE:** Errors are opportunities for clear communication.\n\n### Error Response Pattern\n\n```\n1. Acknowledge the error\n2. Explain what happened (user-friendly)\n3. Offer specific solutions with trade-offs\n4. Ask user to choose or provide alternative\n```\n\n### Error Categories\n\n| Category | Response Strategy |\n|----------|-------------------|\n| **Port Conflict** | Offer alternative port or close existing |\n| **Dependency Missing** | Auto-install or ask permission |\n| **Build Failure** | Show specific error + suggested fix |\n| **Unclear Error** | Ask for specifics: screenshot, console output |\n\n---\n\n## Completion Message (PRINCIPLE-BASED)\n\n**PRINCIPLE:** Celebrate success, guide next steps.\n\n### Completion Structure\n\n```\n1. Success confirmation (celebrate briefly)\n2. Summary of what was done (concrete)\n3. How to verify\u002Ftest (actionable)\n4. Next steps suggestion (proactive)\n```\n\n---\n\n## Communication Principles\n\n| Principle | Implementation |\n|-----------|----------------|\n| **Concise** | No unnecessary details, get to point |\n| **Visual** | Use emojis (✅🔄⏳❌) for quick scanning |\n| **Specific** | \"~2 minutes\" not \"wait a bit\" |\n| **Alternatives** | Offer multiple paths when stuck |\n| **Proactive** | Suggest next step after completion |\n\n---\n\n## Anti-Patterns (AVOID)\n\n| Anti-Pattern | Why |\n|--------------|-----|\n| Jumping to solutions before understanding | Wastes time on wrong problem |\n| Assuming requirements without asking | Creates wrong output |\n| Over-engineering first version | Delays value delivery |\n| Ignoring constraints | Creates unusable solutions |\n| \"I think\" phrases | Uncertainty → Ask instead |\n\n---\n","# Brainstorming & Communication Protocol\n\n> **MANDATORY:** Use for complex\u002Fvague requests, new features, updates.\n\n---\n\n## 🛑 SOCRATIC GATE (ENFORCEMENT)\n\n### When to Trigger\n\n| Pattern | Action |\n|---------|--------|\n| \"Build\u002FCreate\u002FMake [thing]\" without details | 🛑 ASK 3 questions |\n| Complex feature or architecture | 🛑 Clarify before implementing |\n| Update\u002Fchange request | 🛑 Confirm scope |\n| Vague requirements | 🛑 Ask purpose, users, constraints |\n\n### 🚫 MANDATORY: 3 Questions Before Implementation\n\n1. **STOP** - Do NOT start coding\n2. **ASK** - Minimum 3 questions:\n   - 🎯 Purpose: What problem are you solving?\n   - 👥 Users: Who will use this?\n   - 📦 Scope: Must-have vs nice-to-have?\n3. **WAIT** - Get response before proceeding\n\n---\n\n## 🧠 Dynamic Question Generation\n\n**⛔ NEVER use static templates.** Read `dynamic-questioning.md` for principles.\n\n### Core Principles\n\n| Principle | Meaning |\n|-----------|---------|\n| **Questions Reveal Consequences** | Each question connects to an architectural decision |\n| **Context Before Content** | Understand greenfield\u002Ffeature\u002Frefactor\u002Fdebug context first |\n| **Minimum Viable Questions** | Each question must eliminate implementation paths |\n| **Generate Data, Not Assumptions** | Don't guess—ask with trade-offs |\n\n### Question Generation Process\n\n```\n1. Parse request → Extract domain, features, scale indicators\n2. Identify decision points → Blocking vs. deferable\n3. Generate questions → Priority: P0 (blocking) > P1 (high-leverage) > P2 (nice-to-have)\n4. Format with trade-offs → What, Why, Options, Default\n```\n\n### Question Format (MANDATORY)\n\n```markdown\n### [PRIORITY] **[DECISION POINT]**\n\n**Question:** [Clear question]\n\n**Why This Matters:**\n- [Architectural consequence]\n- [Affects: cost\u002Fcomplexity\u002Ftimeline\u002Fscale]\n\n**Options:**\n| Option | Pros | Cons | Best For |\n|--------|------|------|----------|\n| A | [+] | [-] | [Use case] |\n\n**If Not Specified:** [Default + rationale]\n```\n\n**For detailed domain-specific question banks and algorithms**, see: `dynamic-questioning.md`\n\n---\n\n## Progress Reporting (PRINCIPLE-BASED)\n\n**PRINCIPLE:** Transparency builds trust. Status must be visible and actionable.\n\n### Status Board Format\n\n| Agent | Status | Current Task | Progress |\n|-------|--------|--------------|----------|\n| [Agent Name] | ✅🔄⏳❌⚠️ | [Task description] | [% or count] |\n\n### Status Icons\n\n| Icon | Meaning | Usage |\n|------|---------|-------|\n| ✅ | Completed | Task finished successfully |\n| 🔄 | Running | Currently executing |\n| ⏳ | Waiting | Blocked, waiting for dependency |\n| ❌ | Error | Failed, needs attention |\n| ⚠️ | Warning | Potential issue, not blocking |\n\n---\n\n## Error Handling (PRINCIPLE-BASED)\n\n**PRINCIPLE:** Errors are opportunities for clear communication.\n\n### Error Response Pattern\n\n```\n1. Acknowledge the error\n2. Explain what happened (user-friendly)\n3. Offer specific solutions with trade-offs\n4. Ask user to choose or provide alternative\n```\n\n### Error Categories\n\n| Category | Response Strategy |\n|----------|-------------------|\n| **Port Conflict** | Offer alternative port or close existing |\n| **Dependency Missing** | Auto-install or ask permission |\n| **Build Failure** | Show specific error + suggested fix |\n| **Unclear Error** | Ask for specifics: screenshot, console output |\n\n---\n\n## Completion Message (PRINCIPLE-BASED)\n\n**PRINCIPLE:** Celebrate success, guide next steps.\n\n### Completion Structure\n\n```\n1. Success confirmation (celebrate briefly)\n2. Summary of what was done (concrete)\n3. How to verify\u002Ftest (actionable)\n4. Next steps suggestion (proactive)\n```\n\n---\n\n## Communication Principles\n\n| Principle | Implementation |\n|-----------|----------------|\n| **Concise** | No unnecessary details, get to point |\n| **Visual** | Use emojis (✅🔄⏳❌) for quick scanning |\n| **Specific** | \"~2 minutes\" not \"wait a bit\" |\n| **Alternatives** | Offer multiple paths when stuck |\n| **Proactive** | Suggest next step after completion |\n\n---\n\n## Anti-Patterns (AVOID)\n\n| Anti-Pattern | Why |\n|--------------|-----|\n| Jumping to solutions before understanding | Wastes time on wrong problem |\n| Assuming requirements without asking | Creates wrong output |\n| Over-engineering first version | Delays value delivery |\n| Ignoring constraints | Creates unusable solutions |\n| \"I think\" phrases | Uncertainty → Ask instead |\n\n---\n",{"name":5,"description":7,"allowed-tools":40},"Read, Glob, Grep","main","923c514d4d5e15bbfd65ec7eaf949a997679aa3e","src\u002Fskills\u002Fdomain\u002Fbrainstorming","https:\u002F\u002Fgithub.com\u002Fyqecea\u002Fgem-swarm","https:\u002F\u002Fgithub.com\u002Fyqecea","15 y.o Data Science,Student","2026-04-26 20:00:27",{"source":8,"skillName":5,"commands":49,"prompt":59,"zipAvailable":60},[50,53,56],{"tool":51,"command":52},"npx","npx skills add yqecea\u002Fgem-swarm --skill brainstorming",{"tool":54,"command":55},"bunx","bunx skills add yqecea\u002Fgem-swarm --skill brainstorming",{"tool":57,"command":58},"pnpm","pnpm dlx skills add yqecea\u002Fgem-swarm --skill brainstorming","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fyqecea\u002Fgem-swarm\u002Fblob\u002Fmain\u002Fsrc\u002Fskills\u002Fdomain\u002Fbrainstorming\u002FSKILL.md",true,[62],{"path":63,"resourceType":64,"resourceTypeDesc":65,"sizeBytes":66,"sourceHtmlUrl":67},"dynamic-questioning.md","REFERENCE","参考文档",11619,"https:\u002F\u002Fgithub.com\u002Fyqecea\u002Fgem-swarm\u002Fblob\u002Fmain\u002Fsrc\u002Fskills\u002Fdomain\u002Fbrainstorming\u002Fdynamic-questioning.md",[69,82,96,107,117,142],{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":35},"01M71C74XVPP23ST10E8MYJZA0","validation","Cross-cutting validation methodology for verifying phase outputs and project integrity","https:\u002F\u002Fgithub.com\u002Fyqecea\u002Fgem-swarm\u002Fblob\u002Fmain\u002Fsrc\u002Fskills\u002Fshared\u002Fvalidation\u002FSKILL.md",[],[71,76,33,77,78,79,80,81],"validation methodology","project","outputs","phase","methodology","integrity",{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":35},"01M71C72PTKRV481M975R3QDDE","session-management","Manages orchestration session state, tracking, and resumption","https:\u002F\u002Fgithub.com\u002Fyqecea\u002Fgem-swarm\u002Fblob\u002Fmain\u002Fsrc\u002Fskills\u002Fshared\u002Fsession-management\u002FSKILL.md",[],[89,90,91,92,93,94,95],"session management","session","management","session state","orchestration","state","tracking",{"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":15,"licenseFileUrl":6,"sourceHtmlUrl":100,"categories":101,"keywords":102,"publishedAt":35},"01M71C6ZY1EGM4SGVYT4B2HHD7","implementation-planning","Generates detailed implementation plans from finalized designs","https:\u002F\u002Fgithub.com\u002Fyqecea\u002Fgem-swarm\u002Fblob\u002Fmain\u002Fsrc\u002Fskills\u002Fshared\u002Fimplementation-planning\u002FSKILL.md",[],[103,104,105,106],"planning","implementation","implementation planning","plans",{"skillNo":108,"name":109,"nameZh":6,"description":110,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":111,"categories":112,"keywords":113,"publishedAt":35},"01M71C6XQVGMDFJ50BP5SBDS76","execution","Phase execution methodology for orchestration workflows with error handling and completion protocols","https:\u002F\u002Fgithub.com\u002Fyqecea\u002Fgem-swarm\u002Fblob\u002Fmain\u002Fsrc\u002Fskills\u002Fshared\u002Fexecution\u002FSKILL.md",[],[109,33,80,34,114,93,79,115,30,116],"workflows","protocols","with",{"skillNo":118,"name":119,"nameZh":6,"description":120,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":121,"categories":122,"keywords":133,"publishedAt":35},"01M71C6VY8APWMNK1XEJ3WP7A2","design-dialogue","Guides structured design conversations for complex engineering tasks","https:\u002F\u002Fgithub.com\u002Fyqecea\u002Fgem-swarm\u002Fblob\u002Fmain\u002Fsrc\u002Fskills\u002Fshared\u002Fdesign-dialogue\u002FSKILL.md",[123,128],{"categoryNo":124,"categoryName":125,"taxonomyType":126,"taxonomyTypeDesc":127},"01JBSEEDCAT000000000000015","视觉设计","SCENARIO","使用场景",{"categoryNo":129,"categoryName":130,"taxonomyType":131,"taxonomyTypeDesc":132},"01JBSEEDCAT000000000000032","设计师","PROFESSION","适用职业",[134,135,136,137,138,33,139,140,141],"dialogue","design","design dialogue","guides","conversations","tasks","engineering","structured",{"skillNo":143,"name":144,"nameZh":6,"description":145,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":146,"categories":147,"keywords":154,"publishedAt":35},"01M71C6R4RJWG3S2R26778TPD8","delegation","Agent delegation best practices for constructing effective subagent prompts with proper scoping","https:\u002F\u002Fgithub.com\u002Fyqecea\u002Fgem-swarm\u002Fblob\u002Fmain\u002Fsrc\u002Fskills\u002Fshared\u002Fdelegation\u002FSKILL.md",[148,151],{"categoryNo":149,"categoryName":150,"taxonomyType":126,"taxonomyTypeDesc":127},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":152,"categoryName":153,"taxonomyType":126,"taxonomyTypeDesc":127},"01JBSEEDCAT000000000000023","Skill与智能体开发",[144,155,156,33,157,116,158],"subagent","scoping","best practices","prompts"]