@ngxtm/devkit 3.19.0 → 3.21.0

package/merged-commands/application-performance-performance-optimization.md

@@ -38,21 +38,21 @@ Optimize application performance end-to-end using specialized performance and op
 
 ### 1. Comprehensive Performance Profiling
 
-- Use Task tool with subagent_type="performance-engineer"
+- Use Task tool with subagent_type="general-purpose"
 - Prompt: "Profile application performance comprehensively for: $ARGUMENTS. Generate flame graphs for CPU usage, heap dumps for memory analysis, trace I/O operations, and identify hot paths. Use APM tools like DataDog or New Relic if available. Include database query profiling, API response times, and frontend rendering metrics. Establish performance baselines for all critical user journeys."
 - Context: Initial performance investigation
 - Output: Detailed performance profile with flame graphs, memory analysis, bottleneck identification, baseline metrics
 
 ### 2. Observability Stack Assessment
 
-- Use Task tool with subagent_type="observability-engineer"
+- Use Task tool with subagent_type="general-purpose"
 - Prompt: "Assess current observability setup for: $ARGUMENTS. Review existing monitoring, distributed tracing with OpenTelemetry, log aggregation, and metrics collection. Identify gaps in visibility, missing metrics, and areas needing better instrumentation. Recommend APM tool integration and custom metrics for business-critical operations."
 - Context: Performance profile from step 1
 - Output: Observability assessment report, instrumentation gaps, monitoring recommendations
 
 ### 3. User Experience Analysis
 
-- Use Task tool with subagent_type="performance-engineer"
+- Use Task tool with subagent_type="general-purpose"
 - Prompt: "Analyze user experience metrics for: $ARGUMENTS. Measure Core Web Vitals (LCP, FID, CLS), page load times, time to interactive, and perceived performance. Use Real User Monitoring (RUM) data if available. Identify user journeys with poor performance and their business impact."
 - Context: Performance baselines from step 1
 - Output: UX performance report, Core Web Vitals analysis, user impact assessment
@@ -61,21 +61,21 @@ Optimize application performance end-to-end using specialized performance and op
 
 ### 4. Database Performance Optimization
 
-- Use Task tool with subagent_type="database-cloud-optimization::database-optimizer"
+- Use Task tool with subagent_type="general-purpose"
 - Prompt: "Optimize database performance for: $ARGUMENTS based on profiling data: {context_from_phase_1}. Analyze slow query logs, create missing indexes, optimize execution plans, implement query result caching with Redis/Memcached. Review connection pooling, prepared statements, and batch processing opportunities. Consider read replicas and database sharding if needed."
 - Context: Performance bottlenecks from phase 1
 - Output: Optimized queries, new indexes, caching strategy, connection pool configuration
 
 ### 5. Backend Code & API Optimization
 
-- Use Task tool with subagent_type="backend-development::backend-architect"
+- Use Task tool with subagent_type="general-purpose"
 - Prompt: "Optimize backend services for: $ARGUMENTS targeting bottlenecks: {context_from_phase_1}. Implement efficient algorithms, add application-level caching, optimize N+1 queries, use async/await patterns effectively. Implement pagination, response compression, GraphQL query optimization, and batch API operations. Add circuit breakers and bulkheads for resilience."
 - Context: Database optimizations from step 4, profiling data from phase 1
 - Output: Optimized backend code, caching implementation, API improvements, resilience patterns
 
 ### 6. Microservices & Distributed System Optimization
 
-- Use Task tool with subagent_type="performance-engineer"
+- Use Task tool with subagent_type="general-purpose"
 - Prompt: "Optimize distributed system performance for: $ARGUMENTS. Analyze service-to-service communication, implement service mesh optimizations, optimize message queue performance (Kafka/RabbitMQ), reduce network hops. Implement distributed caching strategies and optimize serialization/deserialization."
 - Context: Backend optimizations from step 5
 - Output: Service communication improvements, message queue optimization, distributed caching setup
@@ -84,21 +84,21 @@ Optimize application performance end-to-end using specialized performance and op
 
 ### 7. Frontend Bundle & Loading Optimization
 
-- Use Task tool with subagent_type="frontend-developer"
+- Use Task tool with subagent_type="general-purpose"
 - Prompt: "Optimize frontend performance for: $ARGUMENTS targeting Core Web Vitals: {context_from_phase_1}. Implement code splitting, tree shaking, lazy loading, and dynamic imports. Optimize bundle sizes with webpack/rollup analysis. Implement resource hints (prefetch, preconnect, preload). Optimize critical rendering path and eliminate render-blocking resources."
 - Context: UX analysis from phase 1, backend optimizations from phase 2
 - Output: Optimized bundles, lazy loading implementation, improved Core Web Vitals
 
 ### 8. CDN & Edge Optimization
 
-- Use Task tool with subagent_type="cloud-infrastructure::cloud-architect"
+- Use Task tool with subagent_type="general-purpose"
 - Prompt: "Optimize CDN and edge performance for: $ARGUMENTS. Configure CloudFlare/CloudFront for optimal caching, implement edge functions for dynamic content, set up image optimization with responsive images and WebP/AVIF formats. Configure HTTP/2 and HTTP/3, implement Brotli compression. Set up geographic distribution for global users."
 - Context: Frontend optimizations from step 7
 - Output: CDN configuration, edge caching rules, compression setup, geographic optimization
 
 ### 9. Mobile & Progressive Web App Optimization
 
-- Use Task tool with subagent_type="frontend-mobile-development::mobile-developer"
+- Use Task tool with subagent_type="general-purpose"
 - Prompt: "Optimize mobile experience for: $ARGUMENTS. Implement service workers for offline functionality, optimize for slow networks with adaptive loading. Reduce JavaScript execution time for mobile CPUs. Implement virtual scrolling for long lists. Optimize touch responsiveness and smooth animations. Consider React Native/Flutter specific optimizations if applicable."
 - Context: Frontend optimizations from steps 7-8
 - Output: Mobile-optimized code, PWA implementation, offline functionality
@@ -107,14 +107,14 @@ Optimize application performance end-to-end using specialized performance and op
 
 ### 10. Comprehensive Load Testing
 
-- Use Task tool with subagent_type="performance-engineer"
+- Use Task tool with subagent_type="general-purpose"
 - Prompt: "Conduct comprehensive load testing for: $ARGUMENTS using k6/Gatling/Artillery. Design realistic load scenarios based on production traffic patterns. Test normal load, peak load, and stress scenarios. Include API testing, browser-based testing, and WebSocket testing if applicable. Measure response times, throughput, error rates, and resource utilization at various load levels."
 - Context: All optimizations from phases 1-3
 - Output: Load test results, performance under load, breaking points, scalability analysis
 
 ### 11. Performance Regression Testing
 
-- Use Task tool with subagent_type="performance-testing-review::test-automator"
+- Use Task tool with subagent_type="general-purpose"
 - Prompt: "Create automated performance regression tests for: $ARGUMENTS. Set up performance budgets for key metrics, integrate with CI/CD pipeline using GitHub Actions or similar. Create Lighthouse CI tests for frontend, API performance tests with Artillery, and database performance benchmarks. Implement automatic rollback triggers for performance regressions."
 - Context: Load test results from step 10, baseline metrics from phase 1
 - Output: Performance test suite, CI/CD integration, regression prevention system
@@ -123,14 +123,14 @@ Optimize application performance end-to-end using specialized performance and op
 
 ### 12. Production Monitoring Setup
 
-- Use Task tool with subagent_type="observability-engineer"
+- Use Task tool with subagent_type="general-purpose"
 - Prompt: "Implement production performance monitoring for: $ARGUMENTS. Set up APM with DataDog/New Relic/Dynatrace, configure distributed tracing with OpenTelemetry, implement custom business metrics. Create Grafana dashboards for key metrics, set up PagerDuty alerts for performance degradation. Define SLIs/SLOs for critical services with error budgets."
 - Context: Performance improvements from all previous phases
 - Output: Monitoring dashboards, alert rules, SLI/SLO definitions, runbooks
 
 ### 13. Continuous Performance Optimization
 
-- Use Task tool with subagent_type="performance-engineer"
+- Use Task tool with subagent_type="general-purpose"
 - Prompt: "Establish continuous optimization process for: $ARGUMENTS. Create performance budget tracking, implement A/B testing for performance changes, set up continuous profiling in production. Document optimization opportunities backlog, create capacity planning models, and establish regular performance review cycles."
 - Context: Monitoring setup from step 12, all previous optimization work
 - Output: Performance budget tracking, optimization backlog, capacity planning, review process

package/merged-commands/ask/fast.md

@@ -1,5 +1,5 @@
 ---
-description: ⚡ Quick Answer — Direct response from codebase context
+description: Quick Answer — Direct response from codebase context
 version: "1.0"
 category: knowledge
 execution-mode: execute
@@ -13,58 +13,22 @@ execution-mode: execute
 
 ---
 
-## 🛑 PRE-FLIGHT (DO FIRST — BLOCKS PHASE 1)
+## Execution
 
-**LOAD now** (in order; path `./rules/` or `~/.{TOOL}/skills/agent-assistant/rules/`):
-
-1. ORCHESTRATION-LAWS.md
-2. ADAPTIVE-EXECUTION.md
-3. EXECUTION-PROTOCOL.md
-
-**⛔ Do not run Phase 1 until all are loaded.** Follow **all** rules in those files; they override any conflicting instructions in this file.
+One phase at a time, sequential. Each phase must complete before next begins.
 
 ---
 
-## 🔀 TIERED EXECUTION PROTOCOL (MANDATORY)
-
-> **Reference**: `{RULES_PATH}/ADAPTIVE-EXECUTION.md`
-
-```yaml
-tiered_execution:
-  principle: "Sub-agent FIRST (Tier 1). EMBODY ONLY on system failure (Tier 2)."
-  for_each_phase:
-    TIER_1_MANDATORY: "IF tool exists → MUST use SUB_AGENT_DELEGATION"
-    TIER_2_FALLBACK: "ONLY on system error—NOT complexity/preference/speed"
-  anti_lazy_fallback:
-    - ❌ NEVER use Tier 2 when Tier 1 tool is available
-    - ✅ ALWAYS attempt Tier 1 first when tool exists
-```
-
----
-
-## ⛔ INCREMENTAL EXECUTION (MANDATORY)
-
-One phase at a time, each phase independent: Phase 1 → then Phase 2 → … in one reply. No batching (load only what each phase needs). **Within each phase:** when doing a part, output it in format so user sees what’s happening (announce before doing).
-
----
-
-## 🎭 Phase 1: CONTEXT GATHERING
+## Phase 1: CONTEXT GATHERING
 
 | Attribute | Value                                |
 | --------- | ------------------------------------ |
-| **Agent** | `scouter`                            |
+| **Role**  | `scouter`                            |
 | **Goal**  | Find relevant code and documentation |
 
-### ⚡ TIERED EXECUTION
-
-**TIER 1 (MANDATORY when tool exists):**
-
-> Invoke runSubagent for `scouter`. Context: ISOLATED.
+### Delegation
 
-**TIER 2 (FALLBACK on system error only):**
-
-> Load `{AGENTS_PATH}/scouter.md`
-> EMBODY [scouter] — Requires logged system error justification.
+> Task(subagent_type="general-purpose", prompt="You are a scouter. Find relevant code and documentation for the given question. Exit when: relevant files identified, context gathered, information sufficient.", description="scouter: Find relevant code and documentation")
 
 **Exit Criteria:**
 
@@ -74,23 +38,16 @@ One phase at a time, each phase independent: Phase 1 → then Phase 2 → … in
 
 ---
 
-## 🎭 Phase 2: ANSWER FORMULATION
+## Phase 2: ANSWER FORMULATION
 
 | Attribute | Value                            |
 | --------- | -------------------------------- |
-| **Agent** | `researcher`                     |
+| **Role**  | `researcher`                     |
 | **Goal**  | Formulate clear, accurate answer |
 
-### ⚡ TIERED EXECUTION
-
-**TIER 1 (MANDATORY when tool exists):**
-
-> Invoke runSubagent for `researcher`. Context: ISOLATED.
-
-**TIER 2 (FALLBACK on system error only):**
+### Delegation
 
-> Load `{AGENTS_PATH}/researcher.md`
-> EMBODY [researcher] — Requires logged system error justification.
+> Task(subagent_type="general-purpose", prompt="You are a researcher. Formulate a clear, accurate answer based on the gathered context. Exit when: answer formulated, sources cited, confidence level noted.", description="researcher: Formulate clear, accurate answer")
 
 **Exit Criteria:**
 
@@ -114,6 +71,6 @@ One phase at a time, each phase independent: Phase 1 → then Phase 2 → … in
 
 Present answer with:
 
-1. ✅ **Answered** — Question resolved
-2. 🔬 **Deep Dive** → `/ask:hard` for more detail
-3. 💻 **Implement** → Route to implementation workflow
+1. **Answered** — Question resolved
+2. **Deep Dive** → `/ask:hard` for more detail
+3. **Implement** → Route to implementation workflow

package/merged-commands/ask/hard.md

@@ -1,5 +1,5 @@
 ---
-description: ⚡⚡⚡ Research Answer — External research with comprehensive analysis
+description: Research Answer — External research with comprehensive analysis
 version: "1.0"
 category: knowledge
 execution-mode: execute
@@ -13,58 +13,22 @@ execution-mode: execute
 
 ---
 
-## 🛑 PRE-FLIGHT (DO FIRST — BLOCKS PHASE 1)
+## Execution
 
-**LOAD now** (in order; path `./rules/` or `~/.{TOOL}/skills/agent-assistant/rules/`):
-
-1. ORCHESTRATION-LAWS.md
-2. ADAPTIVE-EXECUTION.md
-3. EXECUTION-PROTOCOL.md
-
-**⛔ Do not run Phase 1 until all are loaded.** Follow **all** rules in those files; they override any conflicting instructions in this file.
-
----
-
-## 🔀 TIERED EXECUTION PROTOCOL (MANDATORY)
-
-> **Reference**: `{RULES_PATH}/ADAPTIVE-EXECUTION.md`
-
-```yaml
-tiered_execution:
-  principle: "Sub-agent FIRST (Tier 1). EMBODY ONLY on system failure (Tier 2)."
-  for_each_phase:
-    TIER_1_MANDATORY: "IF tool exists → MUST use SUB_AGENT_DELEGATION"
-    TIER_2_FALLBACK: "ONLY on system error—NOT complexity/preference/speed"
-  anti_lazy_fallback:
-    - ❌ NEVER use Tier 2 when Tier 1 tool is available
-    - ✅ ALWAYS attempt Tier 1 first when tool exists
-```
-
----
-
-## ⛔ INCREMENTAL EXECUTION (MANDATORY)
-
-One phase at a time, each phase independent: Phase 1 → then Phase 2 → … in one reply. No batching (load only what each phase needs). **Within each phase:** when doing a part, output it in format so user sees what’s happening (announce before doing).
+One phase at a time, sequential. Each phase must complete before next begins.
 
 ---
 
-## 🎭 Phase 1: QUESTION ANALYSIS
+## Phase 1: QUESTION ANALYSIS
 
 | Attribute | Value                                       |
 | --------- | ------------------------------------------- |
-| **Agent** | `brainstormer`                              |
+| **Role**  | `brainstormer`                              |
 | **Goal**  | Decompose question into research components |
 
-### ⚡ TIERED EXECUTION
-
-**TIER 1 (MANDATORY when tool exists):**
+### Delegation
 
-> Invoke runSubagent for `brainstormer`. Context: ISOLATED.
-
-**TIER 2 (FALLBACK on system error only):**
-
-> Load `{AGENTS_PATH}/brainstormer.md`
-> EMBODY [brainstormer] — Requires logged system error justification.
+> Task(subagent_type="general-purpose", prompt="You are a brainstormer. Decompose the question into research components. Exit when: question scope defined, research areas identified, success criteria established.", description="brainstormer: Decompose question into research components")
 
 **Exit Criteria:**
 
@@ -74,23 +38,16 @@ One phase at a time, each phase independent: Phase 1 → then Phase 2 → … in
 
 ---
 
-## 🎭 Phase 2: CODEBASE ANALYSIS
+## Phase 2: CODEBASE ANALYSIS
 
 | Attribute | Value                         |
 | --------- | ----------------------------- |
-| **Agent** | `scouter`                     |
+| **Role**  | `scouter`                     |
 | **Goal**  | Map relevant codebase context |
 
-### ⚡ TIERED EXECUTION
-
-**TIER 1 (MANDATORY when tool exists):**
+### Delegation
 
-> Invoke runSubagent for `scouter`. Context: ISOLATED.
-
-**TIER 2 (FALLBACK on system error only):**
-
-> Load `{AGENTS_PATH}/scouter.md`
-> EMBODY [scouter] — Requires logged system error justification.
+> Task(subagent_type="general-purpose", prompt="You are a scouter. Map relevant codebase context for the question. Exit when: relevant code found, patterns documented, internal context complete.", description="scouter: Map relevant codebase context")
 
 **Exit Criteria:**
 
@@ -100,23 +57,16 @@ One phase at a time, each phase independent: Phase 1 → then Phase 2 → … in
 
 ---
 
-## 🎭 Phase 3: EXTERNAL RESEARCH
+## Phase 3: EXTERNAL RESEARCH
 
 | Attribute | Value                                        |
 | --------- | -------------------------------------------- |
-| **Agent** | `researcher`                                 |
+| **Role**  | `researcher`                                 |
 | **Goal**  | Research external sources and best practices |
 
-### ⚡ TIERED EXECUTION
-
-**TIER 1 (MANDATORY when tool exists):**
+### Delegation
 
-> Invoke runSubagent for `researcher`. Context: ISOLATED.
-
-**TIER 2 (FALLBACK on system error only):**
-
-> Load `{AGENTS_PATH}/researcher.md`
-> EMBODY [researcher] — Requires logged system error justification.
+> Task(subagent_type="general-purpose", prompt="You are a researcher. Research external sources and best practices relevant to the question. Exit when: external sources consulted, best practices identified, sources documented.", description="researcher: Research external sources and best practices")
 
 **Exit Criteria:**
 
@@ -126,23 +76,16 @@ One phase at a time, each phase independent: Phase 1 → then Phase 2 → … in
 
 ---
 
-## 🎭 Phase 4: SYNTHESIS
+## Phase 4: SYNTHESIS
 
 | Attribute | Value                           |
 | --------- | ------------------------------- |
-| **Agent** | `researcher`                    |
+| **Role**  | `researcher`                    |
 | **Goal**  | Synthesize comprehensive answer |
 
-### ⚡ TIERED EXECUTION
-
-**TIER 1 (MANDATORY when tool exists):**
-
-> Invoke runSubagent for `researcher`. Context: ISOLATED.
-
-**TIER 2 (FALLBACK on system error only):**
+### Delegation
 
-> Load `{AGENTS_PATH}/researcher.md`
-> EMBODY [researcher] — Requires logged system error justification.
+> Task(subagent_type="general-purpose", prompt="You are a researcher. Synthesize all gathered information into a comprehensive answer. Exit when: all sources synthesized, answer comprehensive, actionable recommendations included.", description="researcher: Synthesize comprehensive answer")
 
 **Exit Criteria:**
 
@@ -156,6 +99,6 @@ One phase at a time, each phase independent: Phase 1 → then Phase 2 → … in
 
 Present research report with:
 
-1. ✅ **Answered** — Question resolved
-2. 📋 **Plan** → `/plan:hard` if implementation needed
-3. 💻 **Implement** → `/code:hard` for complex implementation
+1. **Answered** — Question resolved
+2. **Plan** → `/plan:hard` if implementation needed
+3. **Implement** → `/code:hard` for complex implementation

package/merged-commands/auto.md

@@ -13,17 +13,6 @@ execution-mode: router
 
 ---
 
-## 🛑 PRE-FLIGHT (DO FIRST — BLOCKS EXECUTION)
-
-**LOAD now** (in order; path `./rules/` or `~/.{TOOL}/skills/agent-assistant/rules/`):
-1. ORCHESTRATION-LAWS.md  
-2. ADAPTIVE-EXECUTION.md  
-3. EXECUTION-PROTOCOL.md  
-
-**⛔ Do not run any workflow phase until all are loaded.** Follow **all** rules in those files. Then run this file's ROUTING LOGIC, LOAD the chosen variant workflow, and execute it.
-
----
-
 ## ROUTING LOGIC
 
 ```
@@ -35,27 +24,16 @@ execution-mode: router
 
 ---
 
-## ⛔ INCREMENTAL EXECUTION (MANDATORY)
-
-One phase at a time, each phase independent: Phase 1 → then Phase 2 → … in one reply. No batching (load only what each phase needs). **Within each phase:** when doing a part, output it in format so user sees what’s happening (announce before doing).
-
----
-
 ## 🎭 Phase 1: TASK ANALYSIS
 
 | Attribute | Value |
 |-----------|-------|
-| **Agent** | `tech-lead` |
+| **Role** | `tech-lead` |
 | **Goal** | Classify task and select workflow |
 
-### ⚡ ADAPTIVE EXECUTION
+### Delegation
 
-**IF platform supports subagents:**
-> Delegate to `tech-lead` subagent. Do NOT read agent file directly.
-
-**ELSE (EMBODY fallback):**
-> Load `{AGENTS_PATH}/tech-lead.md`
-> EMBODY [tech-lead] — Apply methodology from agent file.
+> Task(subagent_type="general-purpose", prompt="You are a tech-lead. Classify task and select workflow. [See exit criteria below]", description="tech-lead")
 
 **Exit Criteria:**
 
@@ -83,17 +61,12 @@ Execute selected workflow phases without pause:
 
 | Attribute | Value |
 |-----------|-------|
-| **Agent** | `tech-lead` |
+| **Role** | `tech-lead` |
 | **Goal** | Synthesize results and present summary |
 
-### ⚡ ADAPTIVE EXECUTION
-
-**IF platform supports subagents:**
-> Delegate to `tech-lead` subagent. Do NOT read agent file directly.
+### Delegation
 
-**ELSE (EMBODY fallback):**
-> Load `{AGENTS_PATH}/tech-lead.md`
-> EMBODY [tech-lead] — Apply methodology from agent file.
+> Task(subagent_type="general-purpose", prompt="You are a tech-lead. Synthesize results and present summary. [See exit criteria below]", description="tech-lead")
 
 **Exit Criteria:**
 

package/merged-commands/backend-development-feature-development.md

@@ -61,19 +61,19 @@ Orchestrate end-to-end feature development from requirements to production deplo
 ## Phase 1: Discovery & Requirements Planning
 
 1. **Business Analysis & Requirements**
-   - Use Task tool with subagent_type="business-analytics::business-analyst"
+   - Use Task tool with subagent_type="general-purpose"
    - Prompt: "Analyze feature requirements for: $ARGUMENTS. Define user stories, acceptance criteria, success metrics, and business value. Identify stakeholders, dependencies, and risks. Create feature specification document with clear scope boundaries."
    - Expected output: Requirements document with user stories, success metrics, risk assessment
    - Context: Initial feature request and business context
 
 2. **Technical Architecture Design**
-   - Use Task tool with subagent_type="comprehensive-review::architect-review"
+   - Use Task tool with subagent_type="general-purpose"
    - Prompt: "Design technical architecture for feature: $ARGUMENTS. Using requirements: [include business analysis from step 1]. Define service boundaries, API contracts, data models, integration points, and technology stack. Consider scalability, performance, and security requirements."
    - Expected output: Technical design document with architecture diagrams, API specifications, data models
    - Context: Business requirements, existing system architecture
 
 3. **Feasibility & Risk Assessment**
-   - Use Task tool with subagent_type="security-scanning::security-auditor"
+   - Use Task tool with subagent_type="general-purpose"
    - Prompt: "Assess security implications and risks for feature: $ARGUMENTS. Review architecture: [include technical design from step 2]. Identify security requirements, compliance needs, data privacy concerns, and potential vulnerabilities."
    - Expected output: Security assessment with risk matrix, compliance checklist, mitigation strategies
    - Context: Technical design, regulatory requirements
@@ -81,19 +81,19 @@ Orchestrate end-to-end feature development from requirements to production deplo
 ## Phase 2: Implementation & Development
 
 4. **Backend Services Implementation**
-   - Use Task tool with subagent_type="backend-architect"
+   - Use Task tool with subagent_type="general-purpose"
    - Prompt: "Implement backend services for: $ARGUMENTS. Follow technical design: [include architecture from step 2]. Build RESTful/GraphQL APIs, implement business logic, integrate with data layer, add resilience patterns (circuit breakers, retries), implement caching strategies. Include feature flags for gradual rollout."
    - Expected output: Backend services with APIs, business logic, database integration, feature flags
    - Context: Technical design, API contracts, data models
 
 5. **Frontend Implementation**
-   - Use Task tool with subagent_type="frontend-mobile-development::frontend-developer"
+   - Use Task tool with subagent_type="general-purpose"
    - Prompt: "Build frontend components for: $ARGUMENTS. Integrate with backend APIs: [include API endpoints from step 4]. Implement responsive UI, state management, error handling, loading states, and analytics tracking. Add feature flag integration for A/B testing capabilities."
    - Expected output: Frontend components with API integration, state management, analytics
    - Context: Backend APIs, UI/UX designs, user stories
 
 6. **Data Pipeline & Integration**
-   - Use Task tool with subagent_type="data-engineering::data-engineer"
+   - Use Task tool with subagent_type="general-purpose"
    - Prompt: "Build data pipelines for: $ARGUMENTS. Design ETL/ELT processes, implement data validation, create analytics events, set up data quality monitoring. Integrate with product analytics platforms for feature usage tracking."
    - Expected output: Data pipelines, analytics events, data quality checks
    - Context: Data requirements, analytics needs, existing data infrastructure
@@ -101,19 +101,19 @@ Orchestrate end-to-end feature development from requirements to production deplo
 ## Phase 3: Testing & Quality Assurance
 
 7. **Automated Test Suite**
-   - Use Task tool with subagent_type="unit-testing::test-automator"
+   - Use Task tool with subagent_type="general-purpose"
    - Prompt: "Create comprehensive test suite for: $ARGUMENTS. Write unit tests for backend: [from step 4] and frontend: [from step 5]. Add integration tests for API endpoints, E2E tests for critical user journeys, performance tests for scalability validation. Ensure minimum 80% code coverage."
    - Expected output: Test suites with unit, integration, E2E, and performance tests
    - Context: Implementation code, acceptance criteria, test requirements
 
 8. **Security Validation**
-   - Use Task tool with subagent_type="security-scanning::security-auditor"
+   - Use Task tool with subagent_type="general-purpose"
    - Prompt: "Perform security testing for: $ARGUMENTS. Review implementation: [include backend and frontend from steps 4-5]. Run OWASP checks, penetration testing, dependency scanning, and compliance validation. Verify data encryption, authentication, and authorization."
    - Expected output: Security test results, vulnerability report, remediation actions
    - Context: Implementation code, security requirements
 
 9. **Performance Optimization**
-   - Use Task tool with subagent_type="application-performance::performance-engineer"
+   - Use Task tool with subagent_type="general-purpose"
    - Prompt: "Optimize performance for: $ARGUMENTS. Analyze backend services: [from step 4] and frontend: [from step 5]. Profile code, optimize queries, implement caching, reduce bundle sizes, improve load times. Set up performance budgets and monitoring."
    - Expected output: Performance improvements, optimization report, performance metrics
    - Context: Implementation code, performance requirements
@@ -121,19 +121,19 @@ Orchestrate end-to-end feature development from requirements to production deplo
 ## Phase 4: Deployment & Monitoring
 
 10. **Deployment Strategy & Pipeline**
-    - Use Task tool with subagent_type="deployment-strategies::deployment-engineer"
+    - Use Task tool with subagent_type="general-purpose"
     - Prompt: "Prepare deployment for: $ARGUMENTS. Create CI/CD pipeline with automated tests: [from step 7]. Configure feature flags for gradual rollout, implement blue-green deployment, set up rollback procedures. Create deployment runbook and rollback plan."
     - Expected output: CI/CD pipeline, deployment configuration, rollback procedures
     - Context: Test suites, infrastructure requirements, deployment strategy
 
 11. **Observability & Monitoring**
-    - Use Task tool with subagent_type="observability-monitoring::observability-engineer"
+    - Use Task tool with subagent_type="general-purpose"
     - Prompt: "Set up observability for: $ARGUMENTS. Implement distributed tracing, custom metrics, error tracking, and alerting. Create dashboards for feature usage, performance metrics, error rates, and business KPIs. Set up SLOs/SLIs with automated alerts."
     - Expected output: Monitoring dashboards, alerts, SLO definitions, observability infrastructure
     - Context: Feature implementation, success metrics, operational requirements
 
 12. **Documentation & Knowledge Transfer**
-    - Use Task tool with subagent_type="documentation-generation::docs-architect"
+    - Use Task tool with subagent_type="general-purpose"
     - Prompt: "Generate comprehensive documentation for: $ARGUMENTS. Create API documentation, user guides, deployment guides, troubleshooting runbooks. Include architecture diagrams, data flow diagrams, and integration guides. Generate automated changelog from commits."
     - Expected output: API docs, user guides, runbooks, architecture documentation
     - Context: All previous phases' outputs