summoner
Multi-agent orchestration skill for complex tasks requiring coordination, decomposition, and quality control. Use for large implementations, refactoring projects, multi-component features, or any work requiring multiple specialized agents.
View on GitHubTable of content
Multi-agent orchestration skill for complex tasks requiring coordination, decomposition, and quality control. Use for large implementations, refactoring projects, multi-component features, or any work requiring multiple specialized agents.
Installation
npx claude-plugins install @Overlord-Z/claudeshack/summoner
Contents
Folders: References, scripts
Files: README.md, SKILL.md
Documentation
Multi-Agent Orchestration for Complex Tasks
The Summoner skill transforms Claude Code into a sophisticated project orchestrator, breaking down complex tasks into manageable units and coordinating specialized agents to deliver high-quality, production-ready code.
What is the Summoner?
The Summoner is a meta-skill that excels at:
- Task Decomposition: Breaking complex requirements into atomic, well-defined tasks
- Context Management: Preserving all necessary context while avoiding bloat
- Agent Orchestration: Summoning and coordinating specialized agents
- Quality Assurance: Ensuring DRY, CLEAN, SOLID principles throughout
- Risk Mitigation: Preventing assumptions, scope creep, and breaking changes
When to Use
✅ Use Summoner For:
- Multi-component features (3+ files/components)
- Large refactoring projects (architectural changes)
- Migration projects (API versions, frameworks, databases)
- Complex bug fixes (multiple related issues)
- New system implementations (auth, payments, etc.)
❌ Don’t Use Summoner For:
- Single file changes
- Simple bug fixes
- Straightforward feature additions
- Routine maintenance
- Quick patches
How It Works
1. Task Analysis
↓
2. Create Mission Control Document (MCD)
↓
3. Decompose into Phases & Tasks
↓
4. For Each Task:
- Summon Specialized Agent
- Provide Bounded Context
- Monitor & Validate
↓
5. Integration & Quality Control
↓
6. Deliver Production-Ready Code
Quick Start
1. Activate the Skill
Simply request it in Claude Code:
Use the summoner skill to implement user authentication with OAuth2
2. Or Explicitly Reference
I need to refactor our API layer to use GraphQL. This is a complex task that
will touch multiple services. Can you use the Summoner skill to orchestrate this?
Components
📄 Templates
mission-control-template.md: Master planning documentagent-spec-template.md: Agent assignment specificationsquality-gates.md: Comprehensive quality checklist
🔧 Scripts
init_mission.py: Initialize new Mission Control Documentsvalidate_quality.py: Interactive quality gate validation
📚 References
All templates and quality standards are in the References/ directory.
Directory Structure
summoner/
├── SKILL.md # Main skill definition
├── README.md # This file
├── scripts/
│ ├── init_mission.py # MCD initializer
│ └── validate_quality.py # Quality validator
├── References/
│ ├── mission-control-template.md
│ ├── agent-spec-template.md
│ └── quality-gates.md
└── Assets/
└── (reserved for future templates)
Example Workflow
Scenario: Implement Real-Time Notifications
Activate Summoner
Use the summoner skill to add real-time notifications to our app using WebSockets. This needs to work across web and mobile clients.Summoner Creates MCD
- Analyzes requirements
- Creates
mission-real-time-notifications.md - Breaks down into phases and tasks
Phase 1: Backend Infrastructure
- Task 1.1: WebSocket server setup (Backend Agent)
- Task 1.2: Message queue integration (Backend Agent)
- Task 1.3: Authentication middleware (Security Agent)
Phase 2: Client Integration
- Task 2.1: Web client WebSocket handler (Frontend Agent)
- Task 2.2: Mobile client integration (Mobile Agent)
- Task 2.3: Reconnection logic (Frontend/Mobile Agents)
Phase 3: Testing & Polish
- Task 3.1: Integration tests (QA Agent)
- Task 3.2: Load testing (Performance Agent)
- Task 3.3: Documentation (Documentation Agent)
Quality Control
- Validate all quality gates
- Integration testing
- Final review
Key Features
🎯 Context Preservation
Every task in the MCD includes:
- Exact context needed (no more, no less)
- Clear inputs and outputs
- Explicit dependencies
- Validation criteria
🛡️ Quality Enforcement
Three levels of quality gates:
- Task-level: DRY, testing, documentation
- Phase-level: Integration, CLEAN, performance, security
- Project-level: SOLID, architecture, production readiness
📊 Progress Tracking
Mission Control Document provides:
- Real-time progress updates
- Risk register
- Decision log
- Integration checklist
🚫 Zero Slop Policy
The Summoner prevents:
- Assumption-driven development
- Context bloat
- Scope creep
- Breaking changes without migration paths
- Code duplication
- Untested code
Using the Scripts
Initialize a Mission
python .claude/skills/summoner/scripts/init_mission.py "Add User Authentication"
Creates mission-add-user-authentication.md ready for editing.
Validate Quality
# Interactive validation
python .claude/skills/summoner/scripts/validate_quality.py --level task --interactive
# Print checklist for manual review
python .claude/skil
...(truncated)
## Source
[View on GitHub](https://github.com/Overlord-Z/ClaudeShack)