mirror of
https://github.com/wshobson/agents.git
synced 2026-03-18 09:37:15 +00:00
fix: resolve agent namespace issues across 11 plugins
Fixed 109 agent namespace issues where external agent references were missing proper namespace prefixes (plugin-name::agent-name format). Affected plugins (bumped to v1.2.1): - tdd-workflows: Fixed 12 references in tdd-cycle, tdd-green, tdd-red - incident-response: Fixed 29 references in incident-response, smart-fix - data-engineering: Fixed 12 references in data-driven-feature - backend-development: Fixed 11 references in feature-development - framework-migration: Fixed 10 references in legacy-modernize - git-pr-workflows: Fixed 7 references in git-workflow - security-scanning: Fixed 7 references in security-hardening - full-stack-orchestration: Fixed 6 references in full-stack-feature - application-performance: Fixed 5 references in performance-optimization - comprehensive-review: Fixed 5 references in full-review - multi-platform-apps: Fixed 5 references in multi-platform Changes: - Added namespace prefixes for all external agent references - Replaced 14 missing agents with appropriate equivalents - Updated marketplace.json to bump affected plugin versions Closes #95
This commit is contained in:
Seth Hobson
@@ -27,7 +27,7 @@ Orchestrate multi-agent incident response with modern SRE practices for rapid re
|
||||
- Context: Initial alerts, monitoring dashboards, recent changes
|
||||
|
||||
### 2. Observability Analysis
|
||||
- Use Task tool with subagent_type="observability-engineer"
|
||||
- Use Task tool with subagent_type="observability-monitoring::observability-engineer"
|
||||
- Prompt: "Perform rapid observability sweep for incident: $ARGUMENTS. Query: 1) Distributed tracing (OpenTelemetry/Jaeger), 2) Metrics correlation (Prometheus/Grafana/DataDog), 3) Log aggregation (ELK/Splunk), 4) APM data, 5) Real User Monitoring. Identify anomalies, error patterns, and service degradation points."
|
||||
- Output: Observability findings, anomaly detection, service health matrix, trace analysis
|
||||
- Context: Severity level from step 1, affected services
|
||||
@@ -41,19 +41,19 @@ Orchestrate multi-agent incident response with modern SRE practices for rapid re
|
||||
## Phase 2: Investigation & Root Cause Analysis
|
||||
|
||||
### 4. Deep System Debugging
|
||||
- Use Task tool with subagent_type="debugger"
|
||||
- Use Task tool with subagent_type="error-debugging::debugger"
|
||||
- Prompt: "Conduct deep debugging for incident: $ARGUMENTS using observability data. Investigate: 1) Stack traces and error logs, 2) Database query performance and locks, 3) Network latency and timeouts, 4) Memory leaks and CPU spikes, 5) Dependency failures and cascading errors. Apply Five Whys analysis."
|
||||
- Output: Root cause identification, contributing factors, dependency impact map
|
||||
- Context: Observability analysis, mitigation status
|
||||
|
||||
### 5. Security Assessment
|
||||
- Use Task tool with subagent_type="security-auditor"
|
||||
- Use Task tool with subagent_type="security-scanning::security-auditor"
|
||||
- Prompt: "Assess security implications of incident: $ARGUMENTS. Check: 1) DDoS attack indicators, 2) Authentication/authorization failures, 3) Data exposure risks, 4) Certificate issues, 5) Suspicious access patterns. Review WAF logs, security groups, and audit trails."
|
||||
- Output: Security assessment, breach analysis, vulnerability identification
|
||||
- Context: Root cause findings, system logs
|
||||
|
||||
### 6. Performance Engineering Analysis
|
||||
- Use Task tool with subagent_type="performance-engineer"
|
||||
- Use Task tool with subagent_type="application-performance::performance-engineer"
|
||||
- Prompt: "Analyze performance aspects of incident: $ARGUMENTS. Examine: 1) Resource utilization patterns, 2) Query optimization opportunities, 3) Caching effectiveness, 4) Load balancer health, 5) CDN performance, 6) Autoscaling triggers. Identify bottlenecks and capacity issues."
|
||||
- Output: Performance bottlenecks, resource recommendations, optimization opportunities
|
||||
- Context: Debug findings, current mitigation state
|
||||
@@ -61,13 +61,13 @@ Orchestrate multi-agent incident response with modern SRE practices for rapid re
|
||||
## Phase 3: Resolution & Recovery
|
||||
|
||||
### 7. Fix Implementation
|
||||
- Use Task tool with subagent_type="backend-architect"
|
||||
- Use Task tool with subagent_type="backend-development::backend-architect"
|
||||
- Prompt: "Design and implement production fix for incident: $ARGUMENTS based on root cause. Requirements: 1) Minimal viable fix for rapid deployment, 2) Risk assessment and rollback capability, 3) Staged rollout plan with monitoring, 4) Validation criteria and health checks. Consider both immediate fix and long-term solution."
|
||||
- Output: Fix implementation, deployment strategy, validation plan, rollback procedures
|
||||
- Context: Root cause analysis, performance findings, security assessment
|
||||
|
||||
### 8. Deployment and Validation
|
||||
- Use Task tool with subagent_type="deployment-engineer"
|
||||
- Use Task tool with subagent_type="deployment-strategies::deployment-engineer"
|
||||
- Prompt: "Execute emergency deployment for incident fix: $ARGUMENTS. Process: 1) Blue-green or canary deployment, 2) Progressive rollout with monitoring, 3) Health check validation at each stage, 4) Rollback triggers configured, 5) Real-time monitoring during deployment. Coordinate with incident command."
|
||||
- Output: Deployment status, validation results, monitoring dashboard, rollback readiness
|
||||
- Context: Fix implementation, current system state
|
||||
@@ -75,7 +75,7 @@ Orchestrate multi-agent incident response with modern SRE practices for rapid re
|
||||
## Phase 4: Communication & Coordination
|
||||
|
||||
### 9. Stakeholder Communication
|
||||
- Use Task tool with subagent_type="content-marketer"
|
||||
- Use Task tool with subagent_type="content-marketing::content-marketer"
|
||||
- Prompt: "Manage incident communication for: $ARGUMENTS. Create: 1) Status page updates (public-facing), 2) Internal engineering updates (technical details), 3) Executive summary (business impact/ETA), 4) Customer support briefing (talking points), 5) Timeline documentation with key decisions. Update every 15-30 minutes based on severity."
|
||||
- Output: Communication artifacts, status updates, stakeholder briefings, timeline log
|
||||
- Context: All previous phases, current resolution status
|
||||
@@ -89,19 +89,19 @@ Orchestrate multi-agent incident response with modern SRE practices for rapid re
|
||||
## Phase 5: Postmortem & Prevention
|
||||
|
||||
### 11. Blameless Postmortem
|
||||
- Use Task tool with subagent_type="docs-architect"
|
||||
- Use Task tool with subagent_type="documentation-generation::docs-architect"
|
||||
- Prompt: "Conduct blameless postmortem for incident: $ARGUMENTS. Document: 1) Complete incident timeline with decisions, 2) Root cause and contributing factors (systems focus), 3) What went well in response, 4) What could improve, 5) Action items with owners and deadlines, 6) Lessons learned for team education. Follow SRE postmortem best practices."
|
||||
- Output: Postmortem document, action items list, process improvements, training needs
|
||||
- Context: Complete incident history, all agent outputs
|
||||
|
||||
### 12. Monitoring and Alert Enhancement
|
||||
- Use Task tool with subagent_type="observability-engineer"
|
||||
- Use Task tool with subagent_type="observability-monitoring::observability-engineer"
|
||||
- Prompt: "Enhance monitoring to prevent recurrence of: $ARGUMENTS. Implement: 1) New alerts for early detection, 2) SLI/SLO adjustments if needed, 3) Dashboard improvements for visibility, 4) Runbook automation opportunities, 5) Chaos engineering scenarios for testing. Ensure alerts are actionable and reduce noise."
|
||||
- Output: New monitoring configuration, alert rules, dashboard updates, runbook automation
|
||||
- Context: Postmortem findings, root cause analysis
|
||||
|
||||
### 13. System Hardening
|
||||
- Use Task tool with subagent_type="backend-architect"
|
||||
- Use Task tool with subagent_type="backend-development::backend-architect"
|
||||
- Prompt: "Design system improvements to prevent incident: $ARGUMENTS. Propose: 1) Architecture changes for resilience (circuit breakers, bulkheads), 2) Graceful degradation strategies, 3) Capacity planning adjustments, 4) Technical debt prioritization, 5) Dependency reduction opportunities. Create implementation roadmap."
|
||||
- Output: Architecture improvements, resilience patterns, technical debt items, roadmap
|
||||
- Context: Postmortem action items, performance analysis
|
||||
|
||||
@@ -4,7 +4,7 @@
|
||||
|
||||
## Phase 1: Issue Analysis - Error Detection and Context Gathering
|
||||
|
||||
Use Task tool with subagent_type="error-detective" followed by subagent_type="debugger":
|
||||
Use Task tool with subagent_type="error-debugging::error-detective" followed by subagent_type="error-debugging::debugger":
|
||||
|
||||
**First: Error-Detective Analysis**
|
||||
|
||||
@@ -89,7 +89,7 @@ TESTING_REQUIREMENTS: [scenarios that must be covered]
|
||||
|
||||
## Phase 2: Root Cause Investigation - Deep Code Analysis
|
||||
|
||||
Use Task tool with subagent_type="debugger" and subagent_type="code-reviewer" for systematic investigation:
|
||||
Use Task tool with subagent_type="error-debugging::debugger" and subagent_type="comprehensive-review::code-reviewer" for systematic investigation:
|
||||
|
||||
**First: Debugger Code Analysis**
|
||||
|
||||
@@ -181,13 +181,13 @@ ARCHITECTURAL_CONCERNS: {if systemic issues exist}
|
||||
Based on Phase 2 output, route to appropriate domain agent using Task tool:
|
||||
|
||||
**Routing Logic:**
|
||||
- Python issues → subagent_type="python-pro"
|
||||
- TypeScript/JavaScript → subagent_type="typescript-pro"
|
||||
- Go → subagent_type="go-expert"
|
||||
- Rust → subagent_type="rust-expert"
|
||||
- SQL/Database → subagent_type="database-optimizer"
|
||||
- Performance → subagent_type="performance-engineer"
|
||||
- Security → subagent_type="security-specialist"
|
||||
- Python issues → subagent_type="python-development::python-pro"
|
||||
- TypeScript/JavaScript → subagent_type="javascript-typescript::typescript-pro"
|
||||
- Go → subagent_type="systems-programming::golang-pro"
|
||||
- Rust → subagent_type="systems-programming::rust-pro"
|
||||
- SQL/Database → subagent_type="database-cloud-optimization::database-optimizer"
|
||||
- Performance → subagent_type="application-performance::performance-engineer"
|
||||
- Security → subagent_type="security-scanning::security-auditor"
|
||||
|
||||
**Prompt Template (adapt for language):**
|
||||
```
|
||||
@@ -265,7 +265,7 @@ BACKWARD_COMPATIBILITY: {maintained | breaking with mitigation}
|
||||
|
||||
## Phase 4: Verification - Automated Testing and Performance Validation
|
||||
|
||||
Use Task tool with subagent_type="test-automator" and subagent_type="performance-engineer":
|
||||
Use Task tool with subagent_type="unit-testing::test-automator" and subagent_type="application-performance::performance-engineer":
|
||||
|
||||
**First: Test-Automator Regression Suite**
|
||||
|
||||
@@ -493,7 +493,7 @@ FINAL_VERDICT: {
|
||||
|
||||
## Phase 5: Documentation and Prevention - Long-term Resilience
|
||||
|
||||
Use Task tool with subagent_type="code-reviewer" for prevention strategies:
|
||||
Use Task tool with subagent_type="comprehensive-review::code-reviewer" for prevention strategies:
|
||||
|
||||
**Prompt:**
|
||||
```
|
||||
@@ -609,13 +609,13 @@ For issues spanning multiple domains, orchestrate specialized agents sequentiall
|
||||
|
||||
**Sequence:**
|
||||
1. **Phase 1-2**: error-detective + debugger identify slow database queries
|
||||
2. **Phase 3a**: Task(subagent_type="database-optimizer")
|
||||
2. **Phase 3a**: Task(subagent_type="database-cloud-optimization::database-optimizer")
|
||||
- Optimize query with proper indexes
|
||||
- Context: "Query execution taking 5s, missing index on user_id column, N+1 query pattern detected"
|
||||
3. **Phase 3b**: Task(subagent_type="performance-engineer")
|
||||
3. **Phase 3b**: Task(subagent_type="application-performance::performance-engineer")
|
||||
- Add caching layer for frequently accessed data
|
||||
- Context: "Database query optimized from 5s to 50ms by adding index on user_id column. Application still experiencing 2s response times due to N+1 query pattern loading 100+ user records per request. Add Redis caching with 5-minute TTL for user profiles."
|
||||
4. **Phase 3c**: Task(subagent_type="devops-troubleshooter")
|
||||
4. **Phase 3c**: Task(subagent_type="incident-response::devops-troubleshooter")
|
||||
- Configure monitoring for query performance and cache hit rates
|
||||
- Context: "Cache layer added with Redis. Need monitoring for: query p95 latency (threshold: 100ms), cache hit rate (threshold: >80%), cache memory usage (alert at 80%)."
|
||||
|
||||
@@ -626,11 +626,11 @@ For issues spanning multiple domains, orchestrate specialized agents sequentiall
|
||||
- Context: "TypeError: Cannot read property 'map' of undefined, 500+ occurrences in last hour, affects Safari users on iOS 14"
|
||||
2. **Phase 2**: debugger + code-reviewer investigate
|
||||
- Context: "API response sometimes returns null instead of empty array when no results. Frontend assumes array."
|
||||
3. **Phase 3a**: Task(subagent_type="typescript-pro")
|
||||
3. **Phase 3a**: Task(subagent_type="javascript-typescript::typescript-pro")
|
||||
- Fix frontend with proper null checks
|
||||
- Add type guards
|
||||
- Context: "Backend API /api/users endpoint returning null instead of [] when no results. Fix frontend to handle both. Add TypeScript strict null checks."
|
||||
4. **Phase 3b**: Task(subagent_type="backend-expert")
|
||||
4. **Phase 3b**: Task(subagent_type="backend-development::backend-architect")
|
||||
- Fix backend to always return array
|
||||
- Update API contract
|
||||
- Context: "Frontend now handles null, but API should follow contract and return [] not null. Update OpenAPI spec to document this."
|
||||
@@ -642,9 +642,9 @@ For issues spanning multiple domains, orchestrate specialized agents sequentiall
|
||||
**Sequence:**
|
||||
1. **Phase 1**: error-detective reviews security scan report
|
||||
- Context: "SQL injection vulnerability in login endpoint, Snyk severity: HIGH"
|
||||
2. **Phase 2**: debugger + security-specialist investigate
|
||||
2. **Phase 2**: debugger + security-auditor investigate
|
||||
- Context: "User input not sanitized in SQL WHERE clause, allows authentication bypass"
|
||||
3. **Phase 3**: Task(subagent_type="security-specialist")
|
||||
3. **Phase 3**: Task(subagent_type="security-scanning::security-auditor")
|
||||
- Implement parameterized queries
|
||||
- Add input validation
|
||||
- Add rate limiting
|
||||
@@ -652,7 +652,7 @@ For issues spanning multiple domains, orchestrate specialized agents sequentiall
|
||||
4. **Phase 4a**: test-automator adds security tests
|
||||
- SQL injection attempts
|
||||
- Brute force scenarios
|
||||
5. **Phase 4b**: security-specialist performs penetration testing
|
||||
5. **Phase 4b**: security-auditor performs penetration testing
|
||||
6. **Phase 5**: code-reviewer documents security improvements and creates postmortem
|
||||
|
||||
**Context Passing Template:**
|
||||
|
||||
Reference in New Issue
Block a user