fix(agent-teams): remove Context7 MCP dependency, align frontmatter with conductor patterns, bump to v1.0.1

Remove .mcp.json to eliminate external MCP dependency that likely caused plugin load failure.
Add tools: field to all agents, version: field to all skills, matching conductor plugin patterns.
This commit is contained in:
Seth Hobson
2026-02-05 17:30:35 -05:00
parent b187ce780d
commit fb9eba62b2
17 changed files with 23 additions and 22 deletions

View File

@@ -1,6 +1,7 @@
---
name: multi-reviewer-patterns
description: Coordinate parallel code reviews across multiple quality dimensions with finding deduplication, severity calibration, and consolidated reporting. Use this skill when organizing multi-reviewer code reviews, calibrating finding severity, or consolidating review results.
version: 1.0.1
---
# Multi-Reviewer Patterns

View File

@@ -1,6 +1,7 @@
---
name: parallel-debugging
description: Debug complex issues using competing hypotheses with parallel investigation, evidence collection, and root cause arbitration. Use this skill when debugging bugs with multiple potential causes, performing root cause analysis, or organizing parallel investigation workflows.
version: 1.0.1
---
# Parallel Debugging

View File

@@ -1,6 +1,7 @@
---
name: parallel-feature-development
description: Coordinate parallel feature development with file ownership strategies, conflict avoidance rules, and integration patterns for multi-agent implementation. Use this skill when decomposing features for parallel development, establishing file ownership boundaries, or managing integration between parallel work streams.
version: 1.0.1
---
# Parallel Feature Development

View File

@@ -1,6 +1,7 @@
---
name: task-coordination-strategies
description: Decompose complex tasks, design dependency graphs, and coordinate multi-agent work with proper task descriptions and workload balancing. Use this skill when breaking down work for agent teams, managing task dependencies, or monitoring team progress.
version: 1.0.1
---
# Task Coordination Strategies

View File

@@ -1,6 +1,7 @@
---
name: team-communication-protocols
description: Structured messaging protocols for agent team communication including message type selection, plan approval, shutdown procedures, and anti-patterns to avoid. Use this skill when establishing team communication norms, handling plan approvals, or managing team shutdown.
version: 1.0.1
---
# Team Communication Protocols

View File

@@ -1,6 +1,7 @@
---
name: team-composition-patterns
description: Design optimal agent team compositions with sizing heuristics, preset configurations, and agent type selection. Use this skill when deciding team size, selecting agent types, or configuring team presets for multi-agent workflows.
version: 1.0.1
---
# Team Composition Patterns
@@ -59,7 +60,7 @@ Best practices for composing multi-agent teams, selecting team sizes, choosing a
- **Size**: 3 researchers
- **Agents**: 3x `general-purpose`
- **Default areas**: Each assigned a different research question, module, or topic
- **Capabilities**: Codebase search (Grep, Glob, Read), web search (WebSearch, WebFetch), library documentation (Context7 MCP)
- **Capabilities**: Codebase search (Grep, Glob, Read), web search (WebSearch, WebFetch)
- **Use when**: Need to understand a codebase, research libraries, compare approaches, or gather information from code and web sources in parallel
### Security Team

View File

@@ -149,7 +149,6 @@ Each researcher has access to:
- **Codebase**: `Grep`, `Glob`, `Read` — search and read local files
- **Web**: `WebSearch`, `WebFetch` — search the web and fetch page content
- **Library Docs**: Context7 MCP (`resolve-library-id`, `query-docs`) — look up current documentation for any library
- **Deep Exploration**: `Task` with `subagent_type: Explore` — spawn sub-explorers for deep dives
### Task Template
@@ -162,7 +161,6 @@ Description:
Tools to prioritize:
- Codebase: Grep/Glob/Read for local code analysis
- Web: WebSearch/WebFetch for articles, examples, best practices
- Docs: Context7 MCP for up-to-date library documentation
Deliverable: Summary with citations (file:line for code, URLs for web)
Output format: Structured report with sections, evidence, and recommendations
```
@@ -170,7 +168,6 @@ Description:
### Variations
- **Codebase-only**: 3 researchers exploring different modules or patterns locally
- **Documentation**: 3 researchers using Context7 to compare library APIs and patterns
- **Web research**: 3 researchers using WebSearch to survey approaches, benchmarks, or best practices
- **Mixed**: 1 codebase researcher + 1 docs researcher + 1 web researcher (recommended for evaluating new libraries)
@@ -178,8 +175,8 @@ Description:
```
Researcher 1 (codebase): "How does our current auth system work? Trace the flow from login to token validation."
Researcher 2 (docs): "Use Context7 to look up the latest NextAuth.js v5 API. How does it handle JWT and session management?"
Researcher 3 (web): "Search for comparisons between NextAuth, Clerk, and Auth0 for Next.js apps. Focus on pricing, DX, and migration effort."
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?"
```
## Security Team Preset