Setting the file. One moment.
Skill 08 · Team Composition Patterns
Subchapter 8.2
references/preset-teams.mdMarkdown9 KBView on GitHub
Detailed preset team configurations with task templates for common workflows.
Command: /team-spawn review
agent-teams:team-reviewer| Name | Dimension | Focus Areas |
|---|---|---|
| security-reviewer | Security | Input validation, auth, injection, secrets, CVEs |
| performance-reviewer | Performance | Query efficiency, memory, caching, async patterns |
| architecture-reviewer | Architecture | SOLID, coupling, patterns, error handling |
Subject: Review {target} for {dimension} issues
Description:
Dimension: {dimension}
Target: {file list or diff}
Checklist: {dimension-specific checklist}
Output format: Structured findings with file:line, severity, evidence, fix--reviewers security,testing (2 members)--reviewers security,performance,architecture,testing,accessibility (5 members)--reviewers architecture,testing,accessibility (3 members)Command: /team-spawn debug
--hypotheses Nagent-teams:team-debugger| Name | Role |
|---|---|
| investigator-1 | Investigates hypothesis 1 |
| investigator-2 | Investigates hypothesis 2 |
| investigator-3 | Investigates hypothesis 3 |
Subject: Investigate hypothesis: {hypothesis summary}
Description:
Hypothesis: {full hypothesis statement}
Scope: {files/module/project}
Evidence criteria:
Confirming: {what would confirm}
Falsifying: {what would falsify}
Report format: confidence level, evidence with file:line, causal chainCommand: /team-spawn feature
agent-teams:team-lead + agent-teams:team-implementer| Name | Role | Responsibility |
|---|---|---|
| feature-lead | team-lead | Decomposition, coordination, integration |
| implementer-1 | team-implementer | Work stream 1 (assigned files) |
| implementer-2 | team-implementer | Work stream 2 (assigned files) |
Subject: Implement {work stream name}
Description:
Owned files: {explicit file list}
Requirements: {specific deliverables}
Interface contract: {shared types/APIs}
Acceptance criteria: {verification steps}
Blocked by: {dependency task IDs if any}Command: /team-spawn fullstack
agent-teams:team-lead + 3x agent-teams:team-implementer| Name | Role | Layer |
|---|---|---|
| fullstack-lead | team-lead | Coordination, integration |
| frontend-dev | team-implementer | UI components, client-side logic |
| backend-dev | team-implementer | API endpoints, business logic |
| test-dev | team-implementer | Unit, integration, e2e tests |
frontend-dev ──┐
├──→ test-dev (blocked by both)
backend-dev ──┘Command: /team-spawn research
general-purpose| Name | Role | Focus |
|---|---|---|
| researcher-1 | general-purpose | Research area 1 (e.g., codebase architecture) |
| researcher-2 | general-purpose | Research area 2 (e.g., library documentation) |
| researcher-3 | general-purpose | Research area 3 (e.g., web resources & examples) |
Each researcher has access to:
Grep, Glob, Read — search and read local filesWebSearch, WebFetch — search the web and fetch page contentTask with subagent_type: Explore — spawn sub-explorers for deep divesSubject: Research {topic or question}
Description:
Question: {specific research question}
Scope: {codebase files, web resources, library docs, or all}
Tools to prioritize:
- Codebase: Grep/Glob/Read for local code analysis
- Web: WebSearch/WebFetch for articles, examples, best practices
Deliverable: Summary with citations (file:line for code, URLs for web)
Output format: Structured report with sections, evidence, and recommendationsResearcher 1 (codebase): "How does our current auth system work? Trace the flow from login to token validation."
Researcher 2 (web): "Search for comparisons between NextAuth, Clerk, and Auth0 for Next.js apps. Focus on pricing, DX, and migration effort."
Researcher 3 (docs): "Look up the latest NextAuth.js v5 API docs. How does it handle JWT and session management?"Command: /team-spawn security
agent-teams:team-reviewer| Name | Dimension | Focus Areas |
|---|---|---|
| vuln-reviewer | OWASP/Vulns | Injection, XSS, CSRF, deserialization, SSRF |
| auth-reviewer | Auth/Access | Authentication, authorization, session management |
| deps-reviewer | Dependencies | CVEs, supply chain, outdated packages, license risks |
| config-reviewer | Secrets/Config | Hardcoded secrets, env vars, debug endpoints, CORS |
Subject: Security audit {target} for {dimension}
Description:
Dimension: {security sub-dimension}
Target: {file list, directory, or entire project}
Checklist: {dimension-specific security checklist}
Output format: Structured findings with file:line, CVSS-like severity, evidence, remediation
Standards: OWASP Top 10, CWE references where applicable--reviewers owasp,secrets (2 members for fast audit)Command: /team-spawn migration
agent-teams:team-lead + 2x agent-teams:team-implementer + agent-teams:team-reviewer| Name | Role | Responsibility |
|---|---|---|
| migration-lead | team-lead | Migration plan, coordination, conflict handling |
| migrator-1 | team-implementer | Migration stream 1 (assigned files/modules) |
| migrator-2 | team-implementer | Migration stream 2 (assigned files/modules) |
| migration-verify | team-reviewer | Verify migrated code correctness and patterns |
Subject: Migrate {module/files} from {old} to {new}
Description:
Owned files: {explicit file list}
Migration rules: {specific transformation patterns}
Old pattern: {what to change from}
New pattern: {what to change to}
Acceptance criteria: {tests pass, no regressions, new patterns used}
Blocked by: {dependency task IDs if any}migration-lead (plan) → migrator-1 ──┐
→ migrator-2 ──┼→ migration-verify
┘