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
2025-10-13 19:15:30 -04:00
parent 9b64821cc9
commit 492adf9353
15 changed files with 126 additions and 126 deletions

View File

@@ -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:**