mirror of
https://github.com/affaan-m/ECC.git
synced 2026-08-20 06:25:43 +02:00
Gaurav Dubey
9d1ecb0754
The `.opencode/commands/*.md` frontmatter referenced agents with the Claude Code plugin namespace (`agent: everything-claude-code:<name>`), but ECC's opencode integration registers its agents unscoped in `opencode.json`'s `agent` map (`code-reviewer`, `planner`, ...), and that file's own `command` section already references them unscoped. The `everything-claude-code:` scope resolves under no opencode config (the opencode plugin package is `ecc-universal`, and inline-config agents are bare), so subtask commands like `/code-review` hard-fail with `Agent not found: everything-claude-code:code-reviewer`. Non-subtask commands fall back to the default agent and appear to work — which is why only some commands failed. Strip the `everything-claude-code:` prefix from all 30 command frontmatter agent ids so they match the registered agents, fix the MIGRATION.md example, and replace the test that enforced the broken scoped invariant with one that asserts each command agent id is a registered opencode agent (fails on the old scoped ids, passes on the fix). Fixes #2477
2.4 KiB
2.4 KiB
description, agent, subtask
| description | agent | subtask |
|---|---|---|
| Orchestrate multiple agents for complex tasks | planner | true |
Orchestrate Command
Orchestrate multiple specialized agents for this complex task: $ARGUMENTS
Your Task
- Analyze task complexity and break into subtasks
- Identify optimal agents for each subtask
- Create execution plan with dependencies
- Coordinate execution - parallel where possible
- Synthesize results into unified output
Available Agents
| Agent | Specialty | Use For |
|---|---|---|
| planner | Implementation planning | Complex feature design |
| architect | System design | Architectural decisions |
| code-reviewer | Code quality | Review changes |
| security-reviewer | Security analysis | Vulnerability detection |
| tdd-guide | Test-driven dev | Feature implementation |
| build-error-resolver | Build fixes | TypeScript/build errors |
| e2e-runner | E2E testing | User flow testing |
| doc-updater | Documentation | Updating docs |
| refactor-cleaner | Code cleanup | Dead code removal |
| go-reviewer | Go code | Go-specific review |
| go-build-resolver | Go builds | Go build errors |
| database-reviewer | Database | Query optimization |
Orchestration Patterns
Sequential Execution
planner → tdd-guide → code-reviewer → security-reviewer
Use when: Later tasks depend on earlier results
Parallel Execution
┌→ security-reviewer
planner →├→ code-reviewer
└→ architect
Use when: Tasks are independent
Fan-Out/Fan-In
┌→ agent-1 ─┐
planner →├→ agent-2 ─┼→ synthesizer
└→ agent-3 ─┘
Use when: Multiple perspectives needed
Execution Plan Format
Phase 1: [Name]
- Agent: [agent-name]
- Task: [specific task]
- Depends on: [none or previous phase]
Phase 2: [Name] (parallel)
- Agent A: [agent-name]
- Task: [specific task]
- Agent B: [agent-name]
- Task: [specific task]
- Depends on: Phase 1
Phase 3: Synthesis
- Combine results from Phase 2
- Generate unified output
Coordination Rules
- Plan before execute - Create full execution plan first
- Minimize handoffs - Reduce context switching
- Parallelize when possible - Independent tasks in parallel
- Clear boundaries - Each agent has specific scope
- Single source of truth - One agent owns each artifact
NOTE: Complex tasks benefit from multi-agent orchestration. Simple tasks should use single agents directly.