[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7AJ18QSWTJ2SAGX0CWJGTRF":3,"skill-same:01M7AJ18QSWTJ2SAGX0CWJGTRF":51},{"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":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":28,"commitSha":29,"skillDirectory":30,"forksCount":31,"repositoryHtmlUrl":32,"repositoryHomepageUrl":6,"ownerHtmlUrl":33,"ownerBlogUrl":34,"ownerDescription":35,"updatedAt":36,"install":37,"resources":50},"01M7AJ18QSWTJ2SAGX0CWJGTRF","speckit-spex-teams-research",null,"Parallel codebase research for planning via parallel agent teams","jimmidyson\u002Fkcp-cluster-api","jimmidyson","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F464659?v=4","01M7AHMAJZVCKJFJ493ENNT2AF","Jimmi Dyson","01M7AHMAKKXY03Y7QK73HWEQQN",1,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fjimmidyson\u002Fkcp-cluster-api\u002Fblob\u002Fmain\u002F.specify\u002Fextensions\u002Fspex-teams\u002F.specify-dev\u002Fagent-commands\u002Fclaude\u002Fspeckit-spex-teams-research\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: speckit-spex-teams-research\ndescription: Parallel codebase research for planning via parallel agent teams\ncompatibility: Requires spec-kit project structure with .specify\u002F directory\nmetadata:\n  author: github-spec-kit\n  source: spex-teams:commands\u002Fspeckit.spex-teams.research.md\n---\n\n# Teams Research: Parallel Codebase Exploration for Planning\n\n## Overview\n\nThis command orchestrates parallel codebase research using parallel agent teams during the plan phase. The lead session analyzes the spec to identify research topics, spawns research agents to explore different parts of the codebase simultaneously, collects their findings, and then generates the plan with comprehensive codebase knowledge.\n\n## Prerequisites\n\n### Parallel Agent Teams Prerequisite\n\n{harness:agent-teams}\nVerify that the parallel agent teams feature is available on the current harness.\nIf not available, fall back to single-session research for this session.\n{\u002Fharness:agent-teams}\n\n**If teams are available:** Proceed with team research.\n\n## Phase 1: Research Topic Identification\n\nRead the spec.md and identify what codebase knowledge is needed to create a solid plan.\n\n### Identify Research Areas\n\nFrom the spec, extract:\n\n1. **Existing code to modify**: Which files, modules, or packages does the spec reference or affect?\n2. **Patterns to follow**: What existing patterns in the codebase should the plan adopt?\n3. **Integration points**: Where does the new feature connect to existing code?\n4. **Technology questions**: What libraries, frameworks, or tools are already in use that are relevant?\n\n### Group into Independent Research Topics\n\nOrganize the areas into independent research topics that can be explored in parallel. Each topic should be:\n\n- **Self-contained**: An agent can research it without needing results from other topics\n- **Focused**: Specific enough to produce actionable findings (not \"explore the whole codebase\")\n- **Relevant**: Directly needed for plan creation\n\n**Examples of good research topics:**\n- \"Explore the authentication module: middleware chain, session handling, token validation patterns\"\n- \"Map the database schema and migration patterns for the user-related tables\"\n- \"Analyze the existing API endpoint structure: routing, validation, error handling conventions\"\n- \"Review the test infrastructure: test helpers, fixtures, integration test patterns\"\n\n### Parallelism Assessment\n\n- **If 0-1 research topics exist** (spec is simple or self-contained): Skip team creation, research directly in the current session. Report: \"Single research area, no parallelism benefit. Researching directly.\"\n- **If 2+ independent research topics exist**: Proceed with agent spawning.\n\n## Phase 2: Research Agent Spawning\n\n### Spawn Rules\n\n- Spawn **one agent per research topic**\n- **Maximum 4 research agents** (research is read-only, so less coordination overhead than implementation, but keep it bounded)\n- If more than 4 topics, merge the least complex ones together\n- **All agents are read-only**: They explore and report, they do not modify files\n\n### Agent Prompt Template\n\nEach research agent receives:\n\n```\nYou are a codebase research agent for the [feature-name] feature planning phase.\n\n## Your Research Topic\n\n[Description of what to research]\n\n## Spec Context\n\n[Relevant sections of spec.md that motivate this research]\n\n## Research Instructions\n\n1. Explore the relevant code thoroughly using Read, Grep, and Glob tools\n2. Document your findings in a structured format:\n   - **Files examined**: List the key files you looked at\n   - **Patterns found**: Describe coding patterns, conventions, and structures\n   - **Integration points**: Where new code would connect to existing code\n   - **Constraints discovered**: Anything that limits or shapes the implementation approach\n   - **Recommendations**: Suggest how the plan should handle this area\n3. Be specific: include file paths, function names, and line references\n4. Do NOT modify any files. This is a read-only research mission.\n5. When done, send your findings back to the lead.\n```\n\n### Spawning Process\n\nCreate an agent team for parallel research:\n\n```\nCreate an agent team for codebase research on [feature-name].\n\nSpawn [N] research agents:\n- Agent 1: [research topic description]\n- Agent 2: [research topic description]\n...\n\nEach agent should explore the codebase and report findings. Read-only, no file modifications.\nWait for all agents to complete before proceeding.\n```\n\n## Phase 3: Findings Consolidation\n\nAfter all research agents report back:\n\n1. **Collect all findings** from teammate messages\n2. **Synthesize**: Identify common patterns across findings, resolve contradictions, note gaps\n3. **Build a research summary**: Organize findings by relevance to plan sections\n4. **Identify any remaining unknowns**: If research revealed new questions, note them for the plan's assumptions section\n\n## Phase 4: Plan Generation\n\nWith research findings in hand, generate the plan:\n\n1. Use the consolidated research as input alongside the spec\n2. Reference specific files, patterns, and integration points discovered by agents\n3. The plan should reflect the actual codebase state, not assumptions\n4. Include a brief \"Research Basis\" note in the plan acknowledging what was explored\n\nThen proceed with normal plan-phase flow (review-spec if spex-gates extension is active, etc.).\n\n## Sequential Fallback\n\nWhen teams cannot be used (feature flag not active, single research topic, simple spec):\n\nResearch the codebase directly in the current session, then generate the plan. This is the normal behavior when the teams extension is not active.\n\n## Multi-Agent Dispatch\n\nThe parallel dispatch mechanism varies by harness:\n\n{harness:agent-teams-research-dispatch}\nUse the agent's team mechanism to spawn research agents.\nIf the current harness does not support parallel dispatch, research all topics sequentially.\n{\u002Fharness:agent-teams-research-dispatch}\n\n## Key Principles\n\n- **Research is read-only**: Agents explore, they never modify files\n- **Lead consolidates and plans**: Research agents gather data, the lead makes design decisions\n- **Breadth over depth**: Better to have a broad understanding than deep knowledge of one area\n- **Graceful degradation**: Always fall back to single-session research if teams can't help\n- **Keep research focused**: Every research topic must tie back to a plan need from the spec","# Teams Research: Parallel Codebase Exploration for Planning\n\n## Overview\n\nThis command orchestrates parallel codebase research using parallel agent teams during the plan phase. The lead session analyzes the spec to identify research topics, spawns research agents to explore different parts of the codebase simultaneously, collects their findings, and then generates the plan with comprehensive codebase knowledge.\n\n## Prerequisites\n\n### Parallel Agent Teams Prerequisite\n\n{harness:agent-teams}\nVerify that the parallel agent teams feature is available on the current harness.\nIf not available, fall back to single-session research for this session.\n{\u002Fharness:agent-teams}\n\n**If teams are available:** Proceed with team research.\n\n## Phase 1: Research Topic Identification\n\nRead the spec.md and identify what codebase knowledge is needed to create a solid plan.\n\n### Identify Research Areas\n\nFrom the spec, extract:\n\n1. **Existing code to modify**: Which files, modules, or packages does the spec reference or affect?\n2. **Patterns to follow**: What existing patterns in the codebase should the plan adopt?\n3. **Integration points**: Where does the new feature connect to existing code?\n4. **Technology questions**: What libraries, frameworks, or tools are already in use that are relevant?\n\n### Group into Independent Research Topics\n\nOrganize the areas into independent research topics that can be explored in parallel. Each topic should be:\n\n- **Self-contained**: An agent can research it without needing results from other topics\n- **Focused**: Specific enough to produce actionable findings (not \"explore the whole codebase\")\n- **Relevant**: Directly needed for plan creation\n\n**Examples of good research topics:**\n- \"Explore the authentication module: middleware chain, session handling, token validation patterns\"\n- \"Map the database schema and migration patterns for the user-related tables\"\n- \"Analyze the existing API endpoint structure: routing, validation, error handling conventions\"\n- \"Review the test infrastructure: test helpers, fixtures, integration test patterns\"\n\n### Parallelism Assessment\n\n- **If 0-1 research topics exist** (spec is simple or self-contained): Skip team creation, research directly in the current session. Report: \"Single research area, no parallelism benefit. Researching directly.\"\n- **If 2+ independent research topics exist**: Proceed with agent spawning.\n\n## Phase 2: Research Agent Spawning\n\n### Spawn Rules\n\n- Spawn **one agent per research topic**\n- **Maximum 4 research agents** (research is read-only, so less coordination overhead than implementation, but keep it bounded)\n- If more than 4 topics, merge the least complex ones together\n- **All agents are read-only**: They explore and report, they do not modify files\n\n### Agent Prompt Template\n\nEach research agent receives:\n\n```\nYou are a codebase research agent for the [feature-name] feature planning phase.\n\n## Your Research Topic\n\n[Description of what to research]\n\n## Spec Context\n\n[Relevant sections of spec.md that motivate this research]\n\n## Research Instructions\n\n1. Explore the relevant code thoroughly using Read, Grep, and Glob tools\n2. Document your findings in a structured format:\n   - **Files examined**: List the key files you looked at\n   - **Patterns found**: Describe coding patterns, conventions, and structures\n   - **Integration points**: Where new code would connect to existing code\n   - **Constraints discovered**: Anything that limits or shapes the implementation approach\n   - **Recommendations**: Suggest how the plan should handle this area\n3. Be specific: include file paths, function names, and line references\n4. Do NOT modify any files. This is a read-only research mission.\n5. When done, send your findings back to the lead.\n```\n\n### Spawning Process\n\nCreate an agent team for parallel research:\n\n```\nCreate an agent team for codebase research on [feature-name].\n\nSpawn [N] research agents:\n- Agent 1: [research topic description]\n- Agent 2: [research topic description]\n...\n\nEach agent should explore the codebase and report findings. Read-only, no file modifications.\nWait for all agents to complete before proceeding.\n```\n\n## Phase 3: Findings Consolidation\n\nAfter all research agents report back:\n\n1. **Collect all findings** from teammate messages\n2. **Synthesize**: Identify common patterns across findings, resolve contradictions, note gaps\n3. **Build a research summary**: Organize findings by relevance to plan sections\n4. **Identify any remaining unknowns**: If research revealed new questions, note them for the plan's assumptions section\n\n## Phase 4: Plan Generation\n\nWith research findings in hand, generate the plan:\n\n1. Use the consolidated research as input alongside the spec\n2. Reference specific files, patterns, and integration points discovered by agents\n3. The plan should reflect the actual codebase state, not assumptions\n4. Include a brief \"Research Basis\" note in the plan acknowledging what was explored\n\nThen proceed with normal plan-phase flow (review-spec if spex-gates extension is active, etc.).\n\n## Sequential Fallback\n\nWhen teams cannot be used (feature flag not active, single research topic, simple spec):\n\nResearch the codebase directly in the current session, then generate the plan. This is the normal behavior when the teams extension is not active.\n\n## Multi-Agent Dispatch\n\nThe parallel dispatch mechanism varies by harness:\n\n{harness:agent-teams-research-dispatch}\nUse the agent's team mechanism to spawn research agents.\nIf the current harness does not support parallel dispatch, research all topics sequentially.\n{\u002Fharness:agent-teams-research-dispatch}\n\n## Key Principles\n\n- **Research is read-only**: Agents explore, they never modify files\n- **Lead consolidates and plans**: Research agents gather data, the lead makes design decisions\n- **Breadth over depth**: Better to have a broad understanding than deep knowledge of one area\n- **Graceful degradation**: Always fall back to single-session research if teams can't help\n- **Keep research focused**: Every research topic must tie back to a plan need from the spec",{"name":5,"metadata":24,"description":7,"compatibility":27},{"author":25,"source":26},"github-spec-kit","spex-teams:commands\u002Fspeckit.spex-teams.research.md","Requires spec-kit project structure with .specify\u002F directory","main","bf2af6077064ba2889ff548f6745f7a89096b9e7",".specify\u002Fextensions\u002Fspex-teams\u002F.specify-dev\u002Fagent-commands\u002Fclaude\u002Fspeckit-spex-teams-research",0,"https:\u002F\u002Fgithub.com\u002Fjimmidyson\u002Fkcp-cluster-api","https:\u002F\u002Fgithub.com\u002Fjimmidyson","https:\u002F\u002Feng.d2iq.com\u002F","Principal Engineer at Nutanix ","2026-11-14 13:13:21",{"source":8,"skillName":5,"commands":38,"prompt":48,"zipAvailable":49},[39,42,45],{"tool":40,"command":41},"npx","npx skills add jimmidyson\u002Fkcp-cluster-api --skill speckit-spex-teams-research",{"tool":43,"command":44},"bunx","bunx skills add jimmidyson\u002Fkcp-cluster-api --skill speckit-spex-teams-research",{"tool":46,"command":47},"pnpm","pnpm dlx skills add jimmidyson\u002Fkcp-cluster-api --skill speckit-spex-teams-research","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjimmidyson\u002Fkcp-cluster-api\u002Fblob\u002Fmain\u002F.specify\u002Fextensions\u002Fspex-teams\u002F.specify-dev\u002Fagent-commands\u002Fclaude\u002Fspeckit-spex-teams-research\u002FSKILL.md",true,[],[52,59,66,73,80,87],{"skillNo":53,"name":54,"nameZh":6,"description":55,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":56,"categories":57,"keywords":58,"publishedAt":19},"01M7AJ1CGXH74ZSZPQ1DP8RQA2","speckit-spex-worktrees-manage","Manage git worktrees for isolated feature development - create after specify, list active worktrees, finish and cleanup","https:\u002F\u002Fgithub.com\u002Fjimmidyson\u002Fkcp-cluster-api\u002Fblob\u002Fmain\u002F.specify\u002Fextensions\u002Fspex-worktrees\u002F.specify-dev\u002Fagent-commands\u002Fclaude\u002Fspeckit-spex-worktrees-manage\u002FSKILL.md",[],[],{"skillNo":60,"name":61,"nameZh":6,"description":62,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":63,"categories":64,"keywords":65,"publishedAt":19},"01M7AJ14V817SCP3YPDSR9E968","speckit-spex-teams-orchestrate","Unified team orchestration: parallel task implementation with spec guardian review pattern via parallel agent teams","https:\u002F\u002Fgithub.com\u002Fjimmidyson\u002Fkcp-cluster-api\u002Fblob\u002Fmain\u002F.specify\u002Fextensions\u002Fspex-teams\u002F.specify-dev\u002Fagent-commands\u002Fclaude\u002Fspeckit-spex-teams-orchestrate\u002FSKILL.md",[],[],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":19},"01M7AJ12G1WGNDSGBVX73ADMTR","speckit-spex-teams-implement","Parallel implementation via agent teams for independent tasks","https:\u002F\u002Fgithub.com\u002Fjimmidyson\u002Fkcp-cluster-api\u002Fblob\u002Fmain\u002F.specify\u002Fextensions\u002Fspex-teams\u002F.specify-dev\u002Fagent-commands\u002Fclaude\u002Fspeckit-spex-teams-implement\u002FSKILL.md",[],[],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":19},"01M7AJ0ZAAP2EDC2DV873YDND9","speckit-spex-gates-verify","Final verification gate: tests, code hygiene, spec compliance, and drift check","https:\u002F\u002Fgithub.com\u002Fjimmidyson\u002Fkcp-cluster-api\u002Fblob\u002Fmain\u002F.specify\u002Fextensions\u002Fspex-gates\u002F.specify-dev\u002Fagent-commands\u002Fclaude\u002Fspeckit-spex-gates-verify\u002FSKILL.md",[],[],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":19},"01M7AJ0W0J07D6X6M77FAYJYPE","speckit-spex-gates-stamp","Final gate before completion - invokes verification for tests, code hygiene, spec compliance, and drift check","https:\u002F\u002Fgithub.com\u002Fjimmidyson\u002Fkcp-cluster-api\u002Fblob\u002Fmain\u002F.specify\u002Fextensions\u002Fspex-gates\u002F.specify-dev\u002Fagent-commands\u002Fclaude\u002Fspeckit-spex-gates-stamp\u002FSKILL.md",[],[],{"skillNo":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":93,"publishedAt":19},"01M7AJ0G09FAQQ2Z4QGRKV5EVK","speckit-spex-gates-review-spec","Review specifications for soundness, completeness, and implementability","https:\u002F\u002Fgithub.com\u002Fjimmidyson\u002Fkcp-cluster-api\u002Fblob\u002Fmain\u002F.specify\u002Fextensions\u002Fspex-gates\u002F.specify-dev\u002Fagent-commands\u002Fclaude\u002Fspeckit-spex-gates-review-spec\u002FSKILL.md",[],[]]