spawn-research-agents
Use when conducting codebase research to orchestrate specialized agents in parallel for comprehensive investigation.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
메뉴
Use when conducting codebase research to orchestrate specialized agents in parallel for comprehensive investigation.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
Generic migration orchestrator that reads CHANGELOG.md to understand and execute version-specific migrations
Determine feature slug interactively by auto-detecting next number and prompting user for description
Share personal documents to the shared namespace with atomic git commit and push
Use when creating implementation plans to generate properly structured plans with phases, success criteria, and project references.
Use when documenting research findings to create properly structured research documents with frontmatter, sections, and file references.
ALWAYS check this skill before using grep, glob, Task tool, or doing any codebase exploration. Guides you to use specialized agents that are more efficient than basic tools.
| name | spawn-research-agents |
| description | Use when conducting codebase research to orchestrate specialized agents in parallel for comprehensive investigation. |
Use specialized agents in parallel to research different aspects of the codebase efficiently.
Choose agents based on research needs:
Always start with locators:
codebase-locator - Find WHERE files/components arethoughts-locator - Find WHAT documentation existsThen use analyzers on findings:
codebase-analyzer - Understand HOW specific code workscodebase-pattern-finder - Find SIMILAR implementationsthoughts-analyzer - Extract insights from specific docsOnly if user explicitly requests:
web-search-researcher - External researchSpawn multiple agents at once using multiple Task calls in a single message:
Task(subagent_type="codebase-locator", prompt="Find all authentication files")
Task(subagent_type="thoughts-locator", prompt="Find auth-related documentation")
Then wait for both to complete before spawning follow-up agents.
Research question: "How does authentication work?"
Step 1 - Locate (parallel):
Task(subagent_type="codebase-locator", prompt="Find all authentication-related files including handlers, middleware, and services")
Task(subagent_type="thoughts-locator", prompt="Find any documentation about authentication implementation")
Step 2 - Analyze (parallel, after step 1 completes):
Task(subagent_type="codebase-analyzer", prompt="Analyze authentication flow from login endpoint through JWT generation")
Task(subagent_type="codebase-pattern-finder", prompt="Find examples of how other endpoints use authentication middleware")
Step 3 - Synthesize: Combine findings with specific file paths and line numbers.