[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6KB8DQ9KSN9TZ8FB5H5NV9C":3,"skill-same:01M6KB8DQ9KSN9TZ8FB5H5NV9C":57},{"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":29,"linkOnly":30,"markdownContent":31,"markdownBody":32,"frontMatter":33,"refName":35,"commitSha":36,"skillDirectory":37,"forksCount":38,"repositoryHtmlUrl":39,"repositoryHomepageUrl":6,"ownerHtmlUrl":40,"ownerBlogUrl":41,"ownerDescription":6,"updatedAt":42,"install":43,"resources":56},"01M6KB8DQ9KSN9TZ8FB5H5NV9C","spawn",null,"Launch N parallel subagents in isolated git worktrees to compete on the session task.","afaizalam2003\u002FMaster-claude-skill","afaizalam2003","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F222019359?v=4","01M6K8F2XNT0HKBPF00JQ78SV3","Faiz Alam","01M6K8F31EBXAPER0EG8R9HTR5",3,"MIT","https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fengineering\u002Fagenthub\u002Fskills\u002Fspawn\u002FSKILL.md",[],[5,19,20,21,22,23,24,25,26,27,28],"launch","git","parallel","git worktrees","session","subagents","hub","worktrees","task","compete","2026-11-10 10:12:30",false,"---\nname: \"spawn\"\ndescription: \"Launch N parallel subagents in isolated git worktrees to compete on the session task.\"\ncommand: \u002Fhub:spawn\n---\n\n# \u002Fhub:spawn — Launch Parallel Agents\n\nSpawn N subagents that work on the same task in parallel, each in an isolated git worktree.\n\n## Usage\n\n```\n\u002Fhub:spawn                                    # Spawn agents for the latest session\n\u002Fhub:spawn 20260317-143022                    # Spawn agents for a specific session\n\u002Fhub:spawn --template optimizer               # Use optimizer template for dispatch prompts\n\u002Fhub:spawn --template refactorer              # Use refactorer template\n```\n\n## Templates\n\nWhen `--template \u003Cname>` is provided, use the dispatch prompt from `references\u002Fagent-templates.md` instead of the default prompt below. Available templates:\n\n| Template | Pattern | Use Case |\n|----------|---------|----------|\n| `optimizer` | Edit → eval → keep\u002Fdiscard → repeat x10 | Performance, latency, size reduction |\n| `refactorer` | Restructure → test → iterate until green | Code quality, tech debt |\n| `test-writer` | Write tests → measure coverage → repeat | Test coverage gaps |\n| `bug-fixer` | Reproduce → diagnose → fix → verify | Bug fix with competing approaches |\n\nWhen using a template, replace all `{variables}` with values from the session config. Assign each agent a **different strategy** appropriate to the template and task — diverse strategies maximize the value of parallel exploration.\n\n## What It Does\n\n1. Load session config from `.agenthub\u002Fsessions\u002F{session-id}\u002Fconfig.yaml`\n2. For each agent 1..N:\n   - Write task assignment to `.agenthub\u002Fboard\u002Fdispatch\u002F`\n   - Build agent prompt with task, constraints, and board write instructions\n3. Launch ALL agents in a **single message** with multiple Agent tool calls:\n\n```\nAgent(\n  prompt: \"You are agent-{i} in hub session {session-id}.\n\nYour task: {task}\n\nRead your full assignment at .agenthub\u002Fboard\u002Fdispatch\u002F{seq}-agent-{i}.md\n\nInstructions:\n1. Work in your worktree — make changes, run tests, iterate\n2. Commit all changes with descriptive messages\n3. Write your result summary to .agenthub\u002Fboard\u002Fresults\u002Fagent-{i}-result.md\n   Include: approach taken, files changed, metric if available, confidence level\n4. Exit when done\n\nConstraints:\n- Do NOT read or modify other agents' work\n- Do NOT access .agenthub\u002Fboard\u002Fresults\u002F for other agents\n- Commit early and often with descriptive messages\n- If you hit a dead end, commit what you have and explain in your result\",\n  isolation: \"worktree\"\n)\n```\n\n4. Update session state to `running` via:\n```bash\npython {skill_path}\u002Fscripts\u002Fsession_manager.py --update {session-id} --state running\n```\n\n## Critical Rules\n\n- **All agents in ONE message** — spawn all Agent tool calls simultaneously for true parallelism\n- **isolation: \"worktree\"** is mandatory — each agent needs its own filesystem\n- **Never modify session config** after spawn — agents rely on stable configuration\n- **Each agent gets a unique board post** — dispatch posts are numbered sequentially\n\n## After Spawn\n\nTell the user:\n- {N} agents launched in parallel\n- Each working in an isolated worktree\n- Monitor with `\u002Fhub:status`\n- Evaluate when done with `\u002Fhub:eval`\n","# \u002Fhub:spawn — Launch Parallel Agents\n\nSpawn N subagents that work on the same task in parallel, each in an isolated git worktree.\n\n## Usage\n\n```\n\u002Fhub:spawn                                    # Spawn agents for the latest session\n\u002Fhub:spawn 20260317-143022                    # Spawn agents for a specific session\n\u002Fhub:spawn --template optimizer               # Use optimizer template for dispatch prompts\n\u002Fhub:spawn --template refactorer              # Use refactorer template\n```\n\n## Templates\n\nWhen `--template \u003Cname>` is provided, use the dispatch prompt from `references\u002Fagent-templates.md` instead of the default prompt below. Available templates:\n\n| Template | Pattern | Use Case |\n|----------|---------|----------|\n| `optimizer` | Edit → eval → keep\u002Fdiscard → repeat x10 | Performance, latency, size reduction |\n| `refactorer` | Restructure → test → iterate until green | Code quality, tech debt |\n| `test-writer` | Write tests → measure coverage → repeat | Test coverage gaps |\n| `bug-fixer` | Reproduce → diagnose → fix → verify | Bug fix with competing approaches |\n\nWhen using a template, replace all `{variables}` with values from the session config. Assign each agent a **different strategy** appropriate to the template and task — diverse strategies maximize the value of parallel exploration.\n\n## What It Does\n\n1. Load session config from `.agenthub\u002Fsessions\u002F{session-id}\u002Fconfig.yaml`\n2. For each agent 1..N:\n   - Write task assignment to `.agenthub\u002Fboard\u002Fdispatch\u002F`\n   - Build agent prompt with task, constraints, and board write instructions\n3. Launch ALL agents in a **single message** with multiple Agent tool calls:\n\n```\nAgent(\n  prompt: \"You are agent-{i} in hub session {session-id}.\n\nYour task: {task}\n\nRead your full assignment at .agenthub\u002Fboard\u002Fdispatch\u002F{seq}-agent-{i}.md\n\nInstructions:\n1. Work in your worktree — make changes, run tests, iterate\n2. Commit all changes with descriptive messages\n3. Write your result summary to .agenthub\u002Fboard\u002Fresults\u002Fagent-{i}-result.md\n   Include: approach taken, files changed, metric if available, confidence level\n4. Exit when done\n\nConstraints:\n- Do NOT read or modify other agents' work\n- Do NOT access .agenthub\u002Fboard\u002Fresults\u002F for other agents\n- Commit early and often with descriptive messages\n- If you hit a dead end, commit what you have and explain in your result\",\n  isolation: \"worktree\"\n)\n```\n\n4. Update session state to `running` via:\n```bash\npython {skill_path}\u002Fscripts\u002Fsession_manager.py --update {session-id} --state running\n```\n\n## Critical Rules\n\n- **All agents in ONE message** — spawn all Agent tool calls simultaneously for true parallelism\n- **isolation: \"worktree\"** is mandatory — each agent needs its own filesystem\n- **Never modify session config** after spawn — agents rely on stable configuration\n- **Each agent gets a unique board post** — dispatch posts are numbered sequentially\n\n## After Spawn\n\nTell the user:\n- {N} agents launched in parallel\n- Each working in an isolated worktree\n- Monitor with `\u002Fhub:status`\n- Evaluate when done with `\u002Fhub:eval`\n",{"name":5,"command":34,"description":7},"\u002Fhub:spawn","main","0b48cbb0e6d5be6ff68c0f6b28bc0c65ee21c4a1","engineering\u002Fagenthub\u002Fskills\u002Fspawn",2,"https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill","https:\u002F\u002Fgithub.com\u002Fafaizalam2003","https:\u002F\u002Fwww.linkedin.com\u002Fin\u002Fmdfaizalam2003\u002F","2026-04-01 04:35:43",{"source":8,"skillName":5,"commands":44,"prompt":54,"zipAvailable":55},[45,48,51],{"tool":46,"command":47},"npx","npx skills add afaizalam2003\u002FMaster-claude-skill --skill spawn",{"tool":49,"command":50},"bunx","bunx skills add afaizalam2003\u002FMaster-claude-skill --skill spawn",{"tool":52,"command":53},"pnpm","pnpm dlx skills add afaizalam2003\u002FMaster-claude-skill --skill spawn","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fengineering\u002Fagenthub\u002Fskills\u002Fspawn\u002FSKILL.md",true,[],[58,90,115,140,172,192],{"skillNo":59,"name":60,"nameZh":6,"description":61,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":62,"categories":63,"keywords":69,"publishedAt":29},"01M6KC4E8MYR9DBAZTAXHKYMMH","soc2-compliance","Use when the user asks to prepare for SOC 2 audits, map Trust Service Criteria, build control matrices, collect audit evidence, perform gap analysis, or assess SOC 2 Type I vs Type II readiness.","https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fra-qm-team\u002Fsoc2-compliance\u002FSKILL.md",[64],{"categoryNo":65,"categoryName":66,"taxonomyType":67,"taxonomyTypeDesc":68},"01JBSEEDCAT000000000000037","律师与法务","PROFESSION","适用职业",[70,71,72,73,74,75,76,77,78,79,80,81,82,83,84,85,86,87,88,89],"compliance","soc2","soc2 compliance","audit evidence","audit","collect","soc","analysis","use","evidence","trust","build","map","control","type","gap","readiness","gap analysis","assess","for",{"skillNo":91,"name":92,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":94,"categories":95,"keywords":96,"publishedAt":29},"01M6KC461R3GKGZ1TAYHVR1MW9","risk-management-specialist","Medical device risk management specialist implementing ISO 14971 throughout product lifecycle. Provides risk analysis, risk evaluation, risk control, and post-production information analysis. Use when user mentions risk management, ISO 14971, risk analysis, FMEA, fault tree analysis, hazard identification, risk control, risk matrix, benefit-risk analysis, residual risk, risk acceptability, or post-market risk.","https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fra-qm-team\u002Frisk-management-specialist\u002FSKILL.md",[],[97,98,99,100,101,102,103,104,77,78,105,106,107,108,109,110,111,112,113,114],"risk","risk management specialist","management","risk management","risk evaluation","product","Evaluation","lifecycle","risk matrix","iso","medical","iso 14971","identification","information","post-production","tree","matrix","implementing",{"skillNo":116,"name":117,"nameZh":6,"description":118,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":119,"categories":120,"keywords":121,"publishedAt":29},"01M6KC3HF5ZFSSP2NZF68PEPFB","regulatory-affairs-head","Senior Regulatory Affairs Manager for HealthTech and MedTech companies. Prepares FDA 510(k), De Novo, and PMA submission packages; analyzes regulatory pathways for new medical devices; drafts responses to FDA deficiency letters and Notified Body queries; develops CE marking technical documentation under EU MDR 2017\u002F745; coordinates multi-market approval strategies across FDA, EU, Health Canada, PMDA, and NMPA; and maintains regulatory intelligence on evolving standards. Use when users need to plan or execute FDA submissions, navigate 510(k) or PMA approval processes, achieve CE marking, prepare pre-submission meeting materials, write regulatory strategy documents, respond to agency queries, or manage compliance documentation for medical device market access.","https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fra-qm-team\u002Fregulatory-affairs-head\u002FSKILL.md",[],[122,123,124,125,126,127,128,129,130,78,131,132,133,134,135,136,137,138,139,89],"regulatory affairs head","regulatory","head","documents","devices","health","plan","write","strategy","standards","queries","manage","strategies","de","users","respond","medical devices","manager",{"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":15,"licenseFileUrl":6,"sourceHtmlUrl":144,"categories":145,"keywords":154,"publishedAt":29},"01M6KC34Z8M1559EY1CXYBJB1A","quality-manager-qms-iso13485","ISO 13485 Quality Management System implementation and maintenance for medical device organizations. Provides QMS design, documentation control, internal auditing, CAPA management, and certification support. Use when working with medical device quality systems, preparing for ISO 13485 audits, managing regulatory compliance documentation, setting up corrective actions, or building audit preparation programs. Useful for quality management, audit preparation, regulatory compliance, medical device documentation, and corrective action workflows.","https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fra-qm-team\u002Fquality-manager-qms-iso13485\u002FSKILL.md",[146,151],{"categoryNo":147,"categoryName":148,"taxonomyType":149,"taxonomyTypeDesc":150},"01JBSEEDCAT000000000000015","视觉设计","SCENARIO","使用场景",{"categoryNo":152,"categoryName":153,"taxonomyType":67,"taxonomyTypeDesc":68},"01JBSEEDCAT000000000000032","设计师",[155,156,139,157,158,159,160,161,162,78,163,164,165,166,167,168,169,170,89,171],"quality manager qms iso13485","quality","design","workflows","validation","actions","certification","system","maintenance","document","systems","records","ISO 13485","organizations","corrective action","internal audit","preparation",{"skillNo":173,"name":174,"nameZh":6,"description":175,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":176,"categories":177,"keywords":179,"publishedAt":29},"01M6KC2FXHBHXYX2ZZ17Y3GDB4","quality-manager-qmr","Senior Quality Manager Responsible Person (QMR) for HealthTech and MedTech companies. Provides quality system governance, management review leadership, regulatory compliance oversight, and quality performance monitoring per ISO 13485 Clause 5.5.2.","https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fra-qm-team\u002Fquality-manager-qmr\u002FSKILL.md",[178],{"categoryNo":65,"categoryName":66,"taxonomyType":67,"taxonomyTypeDesc":68},[180,156,139,181,182,183,184,185,70,186,162,187,123,188,189,190,106,167,89,191],"quality manager qmr","review","policy","performance","governance","monitoring","regulatory compliance","oversight","cost","culture","leadership","person",{"skillNo":193,"name":194,"nameZh":6,"description":195,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":196,"categories":197,"keywords":205,"publishedAt":29},"01M6KC1VRR5JTDBNZANHPS6VR6","quality-documentation-manager","Document control system management for medical device QMS. Covers document numbering, version control, change management, and 21 CFR Part 11 compliance. Use for document control procedures, change control workflow, document numbering, version management, electronic signature compliance, or regulatory documentation review.","https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fra-qm-team\u002Fquality-documentation-manager\u002FSKILL.md",[198,201,204],{"categoryNo":199,"categoryName":200,"taxonomyType":149,"taxonomyTypeDesc":150},"01JBSEEDCAT000000000000002","文档处理",{"categoryNo":202,"categoryName":203,"taxonomyType":149,"taxonomyTypeDesc":150},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":65,"categoryName":66,"taxonomyType":67,"taxonomyTypeDesc":68},[206,207,156,139,181,208,209,74,162,210,211,212,213,214,107,215,216,217,218,89],"documentation","quality documentation manager","workflow","change","change management","list","master","system management","documentation review","cfr","21 cfr part 11","change control","retention"]