-
Notifications
You must be signed in to change notification settings - Fork 4
Agent Overview
Comprehensive guide to all 11 aistack agent types with comparison and use cases.
| Agent | Primary Role | Key Capabilities | Best For |
|---|---|---|---|
| Coder | Write & modify code | write-code, edit-code, refactor, debug | Implementation tasks |
| Researcher | Gather information | search-code, analyze-patterns, explore-codebase | Code exploration |
| Tester | Write & run tests | write-tests, run-tests, identify-edge-cases | Quality assurance |
| Reviewer | Code review | code-review, security-review, best-practices | Quality checks |
| Adversarial | Break code | adversarial-review, edge-case-analysis | Security testing |
| Architect | System design | system-design, technical-decisions | Architecture |
| Coordinator | Orchestrate agents | task-decomposition, workflow-management | Multi-agent flows |
| Analyst | Analyze data | data-analysis, performance-profiling | Metrics & insights |
| DevOps | Infrastructure | ci-cd-setup, containerization, deployment | Operations |
| Documentation | Write docs | api-documentation, tutorials, runbooks | Documentation |
| Security Auditor | Security audit | vulnerability-scanning, compliance-checking | Security |
Simple (Single Focus):
- Coder - Write code
- Tester - Write tests
- Researcher - Find information
Moderate (Multiple Skills):
- Reviewer - Multiple review types
- Documentation - Various doc types
- Analyst - Different analysis methods
Complex (Orchestration):
- Architect - System-wide decisions
- Coordinator - Multi-agent coordination
- DevOps - Full infrastructure stack
- Security Auditor - Comprehensive audits
- Adversarial - Attack modeling
High Frequency:
- Coder (implementation)
- Tester (quality assurance)
- Reviewer (code review)
Medium Frequency:
- Researcher (exploration)
- Documentation (docs)
- Architect (design)
Specialized:
- Adversarial (security-critical code)
- Security Auditor (compliance)
- DevOps (infrastructure)
- Coordinator (complex workflows)
- Analyst (performance issues)
Purpose: Expert software engineer for writing clean, maintainable code
System Prompt Highlights:
- Write simple, readable code
- Follow established patterns
- Avoid over-engineering
- Include essential error handling
Capabilities:
-
write-code- Create new code -
edit-code- Modify existing code -
refactor- Improve code quality -
debug- Fix issues -
implement-features- Build features
When to Use:
- Implementing new features
- Fixing bugs
- Refactoring code
- Adding functionality
- Code generation
Example:
Spawn a coder agent to implement JWT token validation with TypeScript
Purpose: Gather accurate information from codebases and documentation
System Prompt Highlights:
- Prioritize accuracy over speed
- Cite sources and locations
- Distinguish facts from assumptions
- Explore thoroughly
Capabilities:
-
search-code- Find code patterns -
read-documentation- Analyze docs -
analyze-patterns- Identify patterns -
gather-requirements- Extract requirements -
explore-codebase- Map architecture
When to Use:
- Understanding existing code
- Finding usage patterns
- Gathering requirements
- Exploring architecture
- Code discovery
Example:
Spawn a researcher agent to find all authentication-related functions in the codebase
Purpose: Write and run tests to ensure code quality
System Prompt Highlights:
- Test behavior, not implementation
- Write maintainable tests
- Focus on edge cases
- Tests should be fast and reliable
Capabilities:
-
write-tests- Create test suites -
run-tests- Execute tests -
identify-edge-cases- Find edge cases -
coverage-analysis- Analyze coverage -
test-debugging- Debug failing tests
When to Use:
- Creating test suites
- Improving coverage
- Testing edge cases
- Debugging tests
- Integration testing
Example:
Spawn a tester agent to create comprehensive tests for the user authentication module
Purpose: Review code for quality, security, and best practices
System Prompt Highlights:
- Be constructive and specific
- Focus on significant issues
- Consider maintainability
- Check security and performance
Capabilities:
-
code-review- General code review -
security-review- Security checks -
performance-review- Performance analysis -
best-practices- Pattern validation -
feedback- Constructive feedback
When to Use:
- Pre-commit reviews
- Pull request reviews
- Code quality audits
- Best practices validation
- General code review
Example:
Spawn a reviewer agent to review the payment processing module for security and best practices
Purpose: Aggressively try to break code with attack scenarios
System Prompt Highlights:
- Assume code has bugs
- Actively try to break code
- Be skeptical of all claims
- Never accept "it probably works"
Capabilities:
-
adversarial-review- Attack-focused review -
security-audit- Security testing -
edge-case-analysis- Extreme edge cases -
break-code- Break attempts
Attack Vectors:
- Input validation
- State & race conditions
- Error handling
- Security (auth, IDOR, secrets)
- Logic errors
- Performance issues
When to Use:
- Security-critical code
- Authentication systems
- Payment processing
- Data validation
- API endpoints
Example:
Start an adversarial review loop for the user authentication function
Purpose: Design system architecture and make technical decisions
System Prompt Highlights:
- Design for simplicity first
- Consider trade-offs explicitly
- Think about maintainability
- Document decisions
Capabilities:
-
system-design- Architecture design -
technical-decisions- Tech choices -
architecture-review- Design review -
documentation- Design docs -
trade-off-analysis- Evaluate options
When to Use:
- New feature architecture
- System design
- Technology selection
- Scalability planning
- Migration strategies
Example:
Spawn an architect agent to design a scalable notification system supporting email, SMS, and push
Purpose: Orchestrate multi-agent tasks and manage workflows
System Prompt Highlights:
- Break complex tasks into clear steps
- Assign work to specialists
- Track progress and handle blockers
- Synthesize results
Capabilities:
-
task-decomposition- Break down tasks -
agent-coordination- Manage agents -
progress-tracking- Monitor progress -
result-synthesis- Combine results -
workflow-management- Manage workflows
When to Use:
- Complex features
- End-to-end workflows
- Multi-component systems
- Large refactorings
- System migrations
Example:
Spawn a coordinator agent to build a complete user registration system with tests and docs
Purpose: Analyze data, performance, and metrics
System Prompt Highlights:
- Base conclusions on evidence
- Quantify findings with metrics
- Present data clearly
- Identify actionable insights
Capabilities:
-
data-analysis- Analyze datasets -
performance-profiling- Profile performance -
metrics-collection- Collect metrics -
trend-analysis- Identify trends -
reporting- Create reports
When to Use:
- Performance profiling
- Code complexity analysis
- Usage pattern analysis
- Benchmark comparison
- Trend identification
Example:
Spawn an analyst agent to analyze API response times and identify bottlenecks
Purpose: Manage deployment, CI/CD, containers, and infrastructure
System Prompt Highlights:
- Implement automation
- Prioritize security
- Design for scalability
- Follow best practices
Capabilities:
-
ci-cd-setup- Build pipelines -
containerization- Docker/containers -
kubernetes-deployment- K8s manifests -
infrastructure-automation- IaC -
monitoring-setup- Observability -
security-hardening- Security -
cloud-deployment- Cloud platforms -
performance-optimization- Optimize
When to Use:
- Docker containerization
- Kubernetes deployment
- CI/CD pipeline setup
- Infrastructure as code
- Cloud deployment
- Monitoring setup
Example:
Spawn a DevOps agent to create a GitHub Actions CI/CD pipeline with testing and deployment
Purpose: Create comprehensive documentation
System Prompt Highlights:
- Use clear, simple language
- Provide complete information
- Use consistent terminology
- Include working examples
Capabilities:
-
api-documentation- API docs -
user-guides- User documentation -
tutorials- Step-by-step guides -
code-documentation- Inline docs -
architecture-docs- System docs -
runbooks- Operational guides -
readme-creation- README files -
documentation-review- Doc review
When to Use:
- API documentation
- User guides
- Tutorial creation
- Code comments
- README files
- Architecture docs
Example:
Spawn a documentation agent to create API documentation for the user endpoints with examples
Purpose: Comprehensive security analysis and compliance
System Prompt Highlights:
- Perform thorough audits
- Identify all vulnerabilities
- Check OWASP Top 10
- Provide remediation guidance
Capabilities:
-
vulnerability-scanning- Find vulnerabilities -
code-security-review- Security code review -
penetration-testing- Pen testing -
compliance-checking- Compliance audit -
dependency-audit- Dependency scan -
threat-modeling- Threat analysis -
security-documentation- Security docs -
remediation-planning- Fix planning
When to Use:
- OWASP compliance
- Security audits
- Vulnerability scanning
- Threat modeling
- PCI DSS compliance
- HIPAA compliance
Example:
Spawn a security auditor agent to audit the authentication system for OWASP Top 10 vulnerabilities
Architect → Coder → Tester → Reviewer
- Architect designs the solution
- Coder implements the design
- Tester creates tests
- Reviewer validates quality
Architect → Coder → Adversarial ↔ Coder → Security Auditor
- Architect designs secure architecture
- Coder implements
- Adversarial finds issues, Coder fixes (loop)
- Security Auditor performs final audit
Coordinator
├─ Architect (Design)
├─ Coder (Frontend)
├─ Coder (Backend)
├─ Tester (Tests)
└─ Documentation (Docs)
Coordinator manages parallel work streams
Researcher → Analyst → Architect → Coder → Tester
- Researcher analyzes existing code
- Analyst identifies issues
- Architect designs refactoring
- Coder implements changes
- Tester validates behavior preserved
DevOps → Security Auditor → DevOps → Documentation
- DevOps creates CI/CD pipeline
- Security Auditor reviews security
- DevOps hardens configuration
- Documentation creates runbook
- You need code written
- You have clear requirements
- You need bug fixes
- You need refactoring
- You need to understand existing code
- You're exploring a new codebase
- You need to find patterns
- You're gathering requirements
- You need tests written
- You need coverage improved
- You need edge cases tested
- You need test debugging
- You need code reviewed
- You need quality feedback
- You need best practices validation
- You need general review
- Code is security-critical
- You need aggressive testing
- You need attack surface analysis
- You need edge case discovery
- You need system design
- You need technical decisions
- You need architecture review
- You need technology selection
- Task is complex with multiple steps
- You need multiple agents
- You need workflow management
- You need progress tracking
- You need performance analysis
- You need metrics collection
- You need trend analysis
- You need data insights
- You need CI/CD setup
- You need containerization
- You need infrastructure automation
- You need deployment
- You need API docs
- You need user guides
- You need tutorials
- You need code comments
- You need comprehensive security audit
- You need compliance checking
- You need vulnerability scanning
- You need threat modeling
- Coder Agent
- Researcher Agent
- Tester Agent
- Reviewer Agent
- Adversarial Agent
- Architect Agent
- Coordinator Agent
- Analyst Agent
- DevOps Agent
- Documentation Agent
- Security Auditor Agent
Related:
Getting Started
Core Concepts
Agent Guides
- Overview
- Coder
- Researcher
- Tester
- Reviewer
- Adversarial
- Architect
- Coordinator
- Analyst
- DevOps
- Documentation
- Security Auditor
MCP Tools
- Overview
- Agent Tools
- Memory Tools
- Task Tools
- Session Tools
- System Tools
- GitHub Tools
- Review Loop Tools
- Identity Tools
Recipes
- Index
- Code Review
- Doc Sync
- Multi-Agent
- Adversarial Testing
- Full-Stack Feature
- Memory Patterns
- GitHub Integration
Advanced
- Plugin Development
- Custom Agent Types
- Workflow Engine
- Vector Search Setup
- Web Dashboard
- Programmatic API
- Resource Monitoring
Reference