[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71STH3ZNRFCQ90XVFDHMQSN":3,"skill-same:01M71STH3ZNRFCQ90XVFDHMQSN":71},{"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":25,"publishedAt":46,"linkOnly":47,"markdownContent":48,"markdownBody":49,"frontMatter":50,"refName":51,"commitSha":52,"skillDirectory":53,"forksCount":13,"repositoryHtmlUrl":54,"repositoryHomepageUrl":6,"ownerHtmlUrl":55,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":56,"install":57,"resources":70},"01M71STH3ZNRFCQ90XVFDHMQSN","multi-agent-brainstorming",null,"Use this skill when a design or idea requires higher confidence, risk reduction, or formal review. This skill orchestrates a structured, sequential multi-agent design review where each agent has a strict, non-overlapping role. It prevents blind spots, false confidence, and premature convergence.","javiertarazon\u002Fide-agente-free-jt7-","javiertarazon","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F153141207?v=4","01M71R52TB3S9HXKH6WSNT8A7V","01M71R52VG5KS2DKDDH4GDQ30A",0,"MIT","https:\u002F\u002Fgithub.com\u002Fjaviertarazon\u002Fide-agente-free-jt7-\u002Fblob\u002Frelease\u002Fv4.2.11-panel-pro\u002F.github\u002Fskills\u002Fmulti-agent-brainstorming\u002FSKILL.md",[17,22],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000015","视觉设计","SCENARIO","使用场景",{"categoryNo":23,"categoryName":24,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000023","Skill与智能体开发",[26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45],"multi agent brainstorming","multi","brainstorming","multi agent","it","agent design","role","use","design review","risk","idea","multi-agent","convergence","review","unknown","when","false","design","spots","community","2026-11-10 13:02:02",false,"---\nname: multi-agent-brainstorming\ndescription: \n  Use this skill when a design or idea requires higher confidence,\n  risk reduction, or formal review. This skill orchestrates a\n  structured, sequential multi-agent design review where each agent\n  has a strict, non-overlapping role. It prevents blind spots,\n  false confidence, and premature convergence.\nrisk: unknown\nsource: community\n---\n\n# Multi-Agent Brainstorming (Structured Design Review)\n\n## Purpose\n\nTransform a single-agent design into a **robust, review-validated design**\nby simulating a formal peer-review process using multiple constrained agents.\n\nThis skill exists to:\n- surface hidden assumptions\n- identify failure modes early\n- validate non-functional constraints\n- stress-test designs before implementation\n- prevent idea swarm chaos\n\nThis is **not parallel brainstorming**.\nIt is **sequential design review with enforced roles**.\n\n---\n\n## Operating Model\n\n- One agent designs.\n- Other agents review.\n- No agent may exceed its mandate.\n- Creativity is centralized; critique is distributed.\n- Decisions are explicit and logged.\n\nThe process is **gated** and **terminates by design**.\n\n---\n\n## Agent Roles (Non-Negotiable)\n\nEach agent operates under a **hard scope limit**.\n\n### 1️⃣ Primary Designer (Lead Agent)\n\n**Role:**\n- Owns the design\n- Runs the standard `brainstorming` skill\n- Maintains the Decision Log\n\n**May:**\n- Ask clarification questions\n- Propose designs and alternatives\n- Revise designs based on feedback\n\n**May NOT:**\n- Self-approve the final design\n- Ignore reviewer objections\n- Invent requirements post-lock\n\n---\n\n### 2️⃣ Skeptic \u002F Challenger Agent\n\n**Role:**\n- Assume the design will fail\n- Identify weaknesses and risks\n\n**May:**\n- Question assumptions\n- Identify edge cases\n- Highlight ambiguity or overconfidence\n- Flag YAGNI violations\n\n**May NOT:**\n- Propose new features\n- Redesign the system\n- Offer alternative architectures\n\nPrompting guidance:\n> “Assume this design fails in production. Why?”\n\n---\n\n### 3️⃣ Constraint Guardian Agent\n\n**Role:**\n- Enforce non-functional and real-world constraints\n\nFocus areas:\n- performance\n- scalability\n- reliability\n- security & privacy\n- maintainability\n- operational cost\n\n**May:**\n- Reject designs that violate constraints\n- Request clarification of limits\n\n**May NOT:**\n- Debate product goals\n- Suggest feature changes\n- Optimize beyond stated requirements\n\n---\n\n### 4️⃣ User Advocate Agent\n\n**Role:**\n- Represent the end user\n\nFocus areas:\n- cognitive load\n- usability\n- clarity of flows\n- error handling from user perspective\n- mismatch between intent and experience\n\n**May:**\n- Identify confusing or misleading aspects\n- Flag poor defaults or unclear behavior\n\n**May NOT:**\n- Redesign architecture\n- Add features\n- Override stated user goals\n\n---\n\n### 5️⃣ Integrator \u002F Arbiter Agent\n\n**Role:**\n- Resolve conflicts\n- Finalize decisions\n- Enforce exit criteria\n\n**May:**\n- Accept or reject objections\n- Require design revisions\n- Declare the design complete\n\n**May NOT:**\n- Invent new ideas\n- Add requirements\n- Reopen locked decisions without cause\n\n---\n\n## The Process\n\n### Phase 1 — Single-Agent Design\n\n1. Primary Designer runs the **standard `brainstorming` skill**\n2. Understanding Lock is completed and confirmed\n3. Initial design is produced\n4. Decision Log is started\n\nNo other agents participate yet.\n\n---\n\n### Phase 2 — Structured Review Loop\n\nAgents are invoked **one at a time**, in the following order:\n\n1. Skeptic \u002F Challenger\n2. Constraint Guardian\n3. User Advocate\n\nFor each reviewer:\n- Feedback must be explicit and scoped\n- Objections must reference assumptions or decisions\n- No new features may be introduced\n\nPrimary Designer must:\n- Respond to each objection\n- Revise the design if required\n- Update the Decision Log\n\n---\n\n### Phase 3 — Integration & Arbitration\n\nThe Integrator \u002F Arbiter reviews:\n- the final design\n- the Decision Log\n- unresolved objections\n\nThe Arbiter must explicitly decide:\n- which objections are accepted\n- which are rejected (with rationale)\n\n---\n\n## Decision Log (Mandatory Artifact)\n\nThe Decision Log must record:\n\n- Decision made\n- Alternatives considered\n- Objections raised\n- Resolution and rationale\n\nNo design is considered valid without a completed log.\n\n---\n\n## Exit Criteria (Hard Stop)\n\nYou may exit multi-agent brainstorming **only when all are true**:\n\n- Understanding Lock was completed\n- All reviewer agents have been invoked\n- All objections are resolved or explicitly rejected\n- Decision Log is complete\n- Arbiter has declared the design acceptable\n- \nIf any criterion is unmet:\n- Continue review\n- Do NOT proceed to implementation\nIf this skill was invoked by a routing or orchestration layer, you MUST report the final disposition explicitly as one of: APPROVED, REVISE, or REJECT, with a brief rationale.\n---\n\n## Failure Modes This Skill Prevents\n\n- Idea swarm chaos\n- Hallucinated consensus\n- Overconfident single-agent designs\n- Hidden assumptions\n- Premature implementation\n- Endless debate\n\n---\n\n## Key Principles\n\n- One designer, many reviewers\n- Creativity is centralized\n- Critique is constrained\n- Decisions are explicit\n- Process must terminate\n\n---\n\n## Final Reminder\n\nThis skill exists to answer one question with confidence:\n\n> “If this design fails, did we do everything reasonable to catch it early?”\n\nIf the answer is unclear, **do not exit this skill**.\n\n\n## When to Use\nThis skill is applicable to execute the workflow or actions described in the overview.\n","# Multi-Agent Brainstorming (Structured Design Review)\n\n## Purpose\n\nTransform a single-agent design into a **robust, review-validated design**\nby simulating a formal peer-review process using multiple constrained agents.\n\nThis skill exists to:\n- surface hidden assumptions\n- identify failure modes early\n- validate non-functional constraints\n- stress-test designs before implementation\n- prevent idea swarm chaos\n\nThis is **not parallel brainstorming**.\nIt is **sequential design review with enforced roles**.\n\n---\n\n## Operating Model\n\n- One agent designs.\n- Other agents review.\n- No agent may exceed its mandate.\n- Creativity is centralized; critique is distributed.\n- Decisions are explicit and logged.\n\nThe process is **gated** and **terminates by design**.\n\n---\n\n## Agent Roles (Non-Negotiable)\n\nEach agent operates under a **hard scope limit**.\n\n### 1️⃣ Primary Designer (Lead Agent)\n\n**Role:**\n- Owns the design\n- Runs the standard `brainstorming` skill\n- Maintains the Decision Log\n\n**May:**\n- Ask clarification questions\n- Propose designs and alternatives\n- Revise designs based on feedback\n\n**May NOT:**\n- Self-approve the final design\n- Ignore reviewer objections\n- Invent requirements post-lock\n\n---\n\n### 2️⃣ Skeptic \u002F Challenger Agent\n\n**Role:**\n- Assume the design will fail\n- Identify weaknesses and risks\n\n**May:**\n- Question assumptions\n- Identify edge cases\n- Highlight ambiguity or overconfidence\n- Flag YAGNI violations\n\n**May NOT:**\n- Propose new features\n- Redesign the system\n- Offer alternative architectures\n\nPrompting guidance:\n> “Assume this design fails in production. Why?”\n\n---\n\n### 3️⃣ Constraint Guardian Agent\n\n**Role:**\n- Enforce non-functional and real-world constraints\n\nFocus areas:\n- performance\n- scalability\n- reliability\n- security & privacy\n- maintainability\n- operational cost\n\n**May:**\n- Reject designs that violate constraints\n- Request clarification of limits\n\n**May NOT:**\n- Debate product goals\n- Suggest feature changes\n- Optimize beyond stated requirements\n\n---\n\n### 4️⃣ User Advocate Agent\n\n**Role:**\n- Represent the end user\n\nFocus areas:\n- cognitive load\n- usability\n- clarity of flows\n- error handling from user perspective\n- mismatch between intent and experience\n\n**May:**\n- Identify confusing or misleading aspects\n- Flag poor defaults or unclear behavior\n\n**May NOT:**\n- Redesign architecture\n- Add features\n- Override stated user goals\n\n---\n\n### 5️⃣ Integrator \u002F Arbiter Agent\n\n**Role:**\n- Resolve conflicts\n- Finalize decisions\n- Enforce exit criteria\n\n**May:**\n- Accept or reject objections\n- Require design revisions\n- Declare the design complete\n\n**May NOT:**\n- Invent new ideas\n- Add requirements\n- Reopen locked decisions without cause\n\n---\n\n## The Process\n\n### Phase 1 — Single-Agent Design\n\n1. Primary Designer runs the **standard `brainstorming` skill**\n2. Understanding Lock is completed and confirmed\n3. Initial design is produced\n4. Decision Log is started\n\nNo other agents participate yet.\n\n---\n\n### Phase 2 — Structured Review Loop\n\nAgents are invoked **one at a time**, in the following order:\n\n1. Skeptic \u002F Challenger\n2. Constraint Guardian\n3. User Advocate\n\nFor each reviewer:\n- Feedback must be explicit and scoped\n- Objections must reference assumptions or decisions\n- No new features may be introduced\n\nPrimary Designer must:\n- Respond to each objection\n- Revise the design if required\n- Update the Decision Log\n\n---\n\n### Phase 3 — Integration & Arbitration\n\nThe Integrator \u002F Arbiter reviews:\n- the final design\n- the Decision Log\n- unresolved objections\n\nThe Arbiter must explicitly decide:\n- which objections are accepted\n- which are rejected (with rationale)\n\n---\n\n## Decision Log (Mandatory Artifact)\n\nThe Decision Log must record:\n\n- Decision made\n- Alternatives considered\n- Objections raised\n- Resolution and rationale\n\nNo design is considered valid without a completed log.\n\n---\n\n## Exit Criteria (Hard Stop)\n\nYou may exit multi-agent brainstorming **only when all are true**:\n\n- Understanding Lock was completed\n- All reviewer agents have been invoked\n- All objections are resolved or explicitly rejected\n- Decision Log is complete\n- Arbiter has declared the design acceptable\n- \nIf any criterion is unmet:\n- Continue review\n- Do NOT proceed to implementation\nIf this skill was invoked by a routing or orchestration layer, you MUST report the final disposition explicitly as one of: APPROVED, REVISE, or REJECT, with a brief rationale.\n---\n\n## Failure Modes This Skill Prevents\n\n- Idea swarm chaos\n- Hallucinated consensus\n- Overconfident single-agent designs\n- Hidden assumptions\n- Premature implementation\n- Endless debate\n\n---\n\n## Key Principles\n\n- One designer, many reviewers\n- Creativity is centralized\n- Critique is constrained\n- Decisions are explicit\n- Process must terminate\n\n---\n\n## Final Reminder\n\nThis skill exists to answer one question with confidence:\n\n> “If this design fails, did we do everything reasonable to catch it early?”\n\nIf the answer is unclear, **do not exit this skill**.\n\n\n## When to Use\nThis skill is applicable to execute the workflow or actions described in the overview.\n",{"name":5,"risk":40,"source":45,"description":7},"release\u002Fv4.2.11-panel-pro","a92ea02bcf7e2b3dbaf46d49696c29a3cb490d4f",".github\u002Fskills\u002Fmulti-agent-brainstorming","https:\u002F\u002Fgithub.com\u002Fjaviertarazon\u002Fide-agente-free-jt7-","https:\u002F\u002Fgithub.com\u002Fjaviertarazon","2026-07-12 07:10:45",{"source":8,"skillName":5,"commands":58,"prompt":68,"zipAvailable":69},[59,62,65],{"tool":60,"command":61},"npx","npx skills add javiertarazon\u002Fide-agente-free-jt7- --skill multi-agent-brainstorming",{"tool":63,"command":64},"bunx","bunx skills add javiertarazon\u002Fide-agente-free-jt7- --skill multi-agent-brainstorming",{"tool":66,"command":67},"pnpm","pnpm dlx skills add javiertarazon\u002Fide-agente-free-jt7- --skill multi-agent-brainstorming","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjaviertarazon\u002Fide-agente-free-jt7-\u002Fblob\u002Frelease\u002Fv4.2.11-panel-pro\u002F.github\u002Fskills\u002Fmulti-agent-brainstorming\u002FSKILL.md",true,[],[72,98,123,143,158,180],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":81,"publishedAt":46},"01M71TQ7Q6Z10VWF3C2H5X1KW9","zustand-store-ts","Create Zustand stores with TypeScript, subscribeWithSelector middleware, and proper state\u002Faction separation. Use when building React state management, creating global stores, or implementing reacti...","https:\u002F\u002Fgithub.com\u002Fjaviertarazon\u002Fide-agente-free-jt7-\u002Fblob\u002Frelease\u002Fv4.2.11-panel-pro\u002F.github\u002Fskills\u002Fzustand-store-ts\u002FSKILL.md",[78],{"categoryNo":79,"categoryName":80,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000009","前端开发",[82,83,84,45,85,86,33,87,41,40,88,89,90,91,92,93,94,95,96,97],"zustand","store","zustand store ts","middleware","implementing","react state management","react","with","state","create","state management","typescript","action","management","separation","global",{"skillNo":99,"name":100,"nameZh":6,"description":101,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":102,"categories":103,"keywords":105,"publishedAt":46},"01M71TQ5EAR40G6W0MV5ZDVEZT","zoom-automation","Automate Zoom meeting creation, management, recordings, webinars, and participant tracking via Rube MCP (Composio). Always search tools first for current schemas.","https:\u002F\u002Fgithub.com\u002Fjaviertarazon\u002Fide-agente-free-jt7-\u002Fblob\u002Frelease\u002Fv4.2.11-panel-pro\u002F.github\u002Fskills\u002Fzoom-automation\u002FSKILL.md",[104],{"categoryNo":23,"categoryName":24,"taxonomyType":20,"taxonomyTypeDesc":21},[106,107,108,45,109,110,111,112,113,40,114,115,116,117,118,119,120,121,95,122],"zoom automation","zoom","automation","creation","for","search","schemas","MCP","first","via","meeting","search tools","tracking","webinars","composio","recordings","Tools",{"skillNo":124,"name":125,"nameZh":6,"description":126,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":127,"categories":128,"keywords":130,"publishedAt":46},"01M71TQ29B1EYBCEAP1ZBGXQ1A","zoho-crm-automation","Automate Zoho CRM tasks via Rube MCP (Composio): create\u002Fupdate records, search contacts, manage leads, and convert leads. Always search tools first for current schemas.","https:\u002F\u002Fgithub.com\u002Fjaviertarazon\u002Fide-agente-free-jt7-\u002Fblob\u002Frelease\u002Fv4.2.11-panel-pro\u002F.github\u002Fskills\u002Fzoho-crm-automation\u002FSKILL.md",[129],{"categoryNo":23,"categoryName":24,"taxonomyType":20,"taxonomyTypeDesc":21},[131,132,108,133,134,135,45,136,137,110,138,111,112,139,113,40,140,141,142,91],"crm automation","zoho crm automation","crm","zoho crm","zoho","leads","manage leads","manage","records","convert","tasks","contacts",{"skillNo":144,"name":145,"nameZh":6,"description":146,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":147,"categories":148,"keywords":150,"publishedAt":46},"01M71TPZPMN60DH0XV58KVHY23","zendesk-automation","Automate Zendesk tasks via Rube MCP (Composio): tickets, users, organizations, replies. Always search tools first for current schemas.","https:\u002F\u002Fgithub.com\u002Fjaviertarazon\u002Fide-agente-free-jt7-\u002Fblob\u002Frelease\u002Fv4.2.11-panel-pro\u002F.github\u002Fskills\u002Fzendesk-automation\u002FSKILL.md",[149],{"categoryNo":23,"categoryName":24,"taxonomyType":20,"taxonomyTypeDesc":21},[151,108,152,45,110,111,112,113,153,40,141,154,155,114,115,156,117,120,122,157],"zendesk automation","zendesk","organizations","replies","users","tickets","automate",{"skillNo":159,"name":160,"nameZh":6,"description":161,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":162,"categories":163,"keywords":164,"publishedAt":46},"01M71TPXDWKHKG4N6TVEPXWD0N","zapier-make-patterns","No-code automation democratizes workflow building. Zapier and Make (formerly Integromat) let non-developers automate business processes without writing code. But no-code doesn't mean no-complexity ...","https:\u002F\u002Fgithub.com\u002Fjaviertarazon\u002Fide-agente-free-jt7-\u002Fblob\u002Frelease\u002Fv4.2.11-panel-pro\u002F.github\u002Fskills\u002Fzapier-make-patterns\u002FSKILL.md",[],[165,166,167,168,169,170,171,172,173,108,174,40,175,176,177,178,179,157],"zapier make patterns","zapier","patterns","make","No-Code","complexity","writing","spawner","business","workflow","code","integromat","apache","processes","but",{"skillNo":181,"name":182,"nameZh":6,"description":183,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":184,"categories":185,"keywords":189,"publishedAt":46},"01M71TPT5T10WXNKW9G7ZXZ27W","youtube-summarizer","Extract transcripts from YouTube videos and generate comprehensive, detailed summaries using intelligent analysis frameworks","https:\u002F\u002Fgithub.com\u002Fjaviertarazon\u002Fide-agente-free-jt7-\u002Fblob\u002Frelease\u002Fv4.2.11-panel-pro\u002F.github\u002Fskills\u002Fyoutube-summarizer\u002FSKILL.md",[186],{"categoryNo":187,"categoryName":188,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000016","图像与多媒体",[190,191,192,193,45,194,195,196,197,198,199,200,175,201,202,203,204,205,206,207],"summarizer","youtube","youtube summarizer","Video","content-analysis","frameworks","copilot","2025","github-copilot","extract transcripts","analysis","codex","cli","summaries","github","generate","summarization","2026"]