Initial commit

2025-11-29 18:34:16 +08:00
commit da72d02770
12 changed files with 3947 additions and 0 deletions
--- a/commands/code-migrate.md
+++ b/commands/code-migrate.md
--- a/commands/deps-upgrade.md
+++ b/commands/deps-upgrade.md
@@ -0,0 +1,751 @@
+# Dependency Upgrade Strategy
+
+You are a dependency management expert specializing in safe, incremental upgrades of project dependencies. Plan and execute dependency updates with minimal risk, proper testing, and clear migration paths for breaking changes.
+
+## Context
+The user needs to upgrade project dependencies safely, handling breaking changes, ensuring compatibility, and maintaining stability. Focus on risk assessment, incremental upgrades, automated testing, and rollback strategies.
+
+## Requirements
+$ARGUMENTS
+
+## Instructions
+
+### 1. Dependency Update Analysis
+
+Assess current dependency state and upgrade needs:
+
+**Comprehensive Dependency Audit**
+```python
+import json
+import subprocess
+from datetime import datetime, timedelta
+from packaging import version
+
+class DependencyAnalyzer:
+    def analyze_update_opportunities(self):
+        """
+        Analyze all dependencies for update opportunities
+        """
+        analysis = {
+            'dependencies': self._analyze_dependencies(),
+            'update_strategy': self._determine_strategy(),
+            'risk_assessment': self._assess_risks(),
+            'priority_order': self._prioritize_updates()
+        }
+        
+        return analysis
+    
+    def _analyze_dependencies(self):
+        """Analyze each dependency"""
+        deps = {}
+        
+        # NPM analysis
+        if self._has_npm():
+            npm_output = subprocess.run(
+                ['npm', 'outdated', '--json'],
+                capture_output=True,
+                text=True
+            )
+            if npm_output.stdout:
+                npm_data = json.loads(npm_output.stdout)
+                for pkg, info in npm_data.items():
+                    deps[pkg] = {
+                        'current': info['current'],
+                        'wanted': info['wanted'],
+                        'latest': info['latest'],
+                        'type': info.get('type', 'dependencies'),
+                        'ecosystem': 'npm',
+                        'update_type': self._categorize_update(
+                            info['current'], 
+                            info['latest']
+                        )
+                    }
+        
+        # Python analysis
+        if self._has_python():
+            pip_output = subprocess.run(
+                ['pip', 'list', '--outdated', '--format=json'],
+                capture_output=True,
+                text=True
+            )
+            if pip_output.stdout:
+                pip_data = json.loads(pip_output.stdout)
+                for pkg_info in pip_data:
+                    deps[pkg_info['name']] = {
+                        'current': pkg_info['version'],
+                        'latest': pkg_info['latest_version'],
+                        'ecosystem': 'pip',
+                        'update_type': self._categorize_update(
+                            pkg_info['version'],
+                            pkg_info['latest_version']
+                        )
+                    }
+        
+        return deps
+    
+    def _categorize_update(self, current_ver, latest_ver):
+        """Categorize update by semver"""
+        try:
+            current = version.parse(current_ver)
+            latest = version.parse(latest_ver)
+            
+            if latest.major > current.major:
+                return 'major'
+            elif latest.minor > current.minor:
+                return 'minor'
+            elif latest.micro > current.micro:
+                return 'patch'
+            else:
+                return 'none'
+        except:
+            return 'unknown'
+```
+
+### 2. Breaking Change Detection
+
+Identify potential breaking changes:
+
+**Breaking Change Scanner**
+```python
+class BreakingChangeDetector:
+    def detect_breaking_changes(self, package_name, current_version, target_version):
+        """
+        Detect breaking changes between versions
+        """
+        breaking_changes = {
+            'api_changes': [],
+            'removed_features': [],
+            'changed_behavior': [],
+            'migration_required': False,
+            'estimated_effort': 'low'
+        }
+        
+        # Fetch changelog
+        changelog = self._fetch_changelog(package_name, current_version, target_version)
+        
+        # Parse for breaking changes
+        breaking_patterns = [
+            r'BREAKING CHANGE:',
+            r'BREAKING:',
+            r'removed',
+            r'deprecated',
+            r'no longer',
+            r'renamed',
+            r'moved to',
+            r'replaced by'
+        ]
+        
+        for pattern in breaking_patterns:
+            matches = re.finditer(pattern, changelog, re.IGNORECASE)
+            for match in matches:
+                context = self._extract_context(changelog, match.start())
+                breaking_changes['api_changes'].append(context)
+        
+        # Check for specific patterns
+        if package_name == 'react':
+            breaking_changes.update(self._check_react_breaking_changes(
+                current_version, target_version
+            ))
+        elif package_name == 'webpack':
+            breaking_changes.update(self._check_webpack_breaking_changes(
+                current_version, target_version
+            ))
+        
+        # Estimate migration effort
+        breaking_changes['estimated_effort'] = self._estimate_effort(breaking_changes)
+        
+        return breaking_changes
+    
+    def _check_react_breaking_changes(self, current, target):
+        """React-specific breaking changes"""
+        changes = {
+            'api_changes': [],
+            'migration_required': False
+        }
+        
+        # React 15 to 16
+        if current.startswith('15') and target.startswith('16'):
+            changes['api_changes'].extend([
+                'PropTypes moved to separate package',
+                'React.createClass deprecated',
+                'String refs deprecated'
+            ])
+            changes['migration_required'] = True
+        
+        # React 16 to 17
+        elif current.startswith('16') and target.startswith('17'):
+            changes['api_changes'].extend([
+                'Event delegation changes',
+                'No event pooling',
+                'useEffect cleanup timing changes'
+            ])
+        
+        # React 17 to 18
+        elif current.startswith('17') and target.startswith('18'):
+            changes['api_changes'].extend([
+                'Automatic batching',
+                'Stricter StrictMode',
+                'Suspense changes',
+                'New root API'
+            ])
+            changes['migration_required'] = True
+        
+        return changes
+```
+
+### 3. Migration Guide Generation
+
+Create detailed migration guides:
+
+**Migration Guide Generator**
+```python
+def generate_migration_guide(package_name, current_version, target_version, breaking_changes):
+    """
+    Generate step-by-step migration guide
+    """
+    guide = f"""
+# Migration Guide: {package_name} {current_version} → {target_version}
+
+## Overview
+This guide will help you upgrade {package_name} from version {current_version} to {target_version}.
+
+**Estimated time**: {estimate_migration_time(breaking_changes)}
+**Risk level**: {assess_risk_level(breaking_changes)}
+**Breaking changes**: {len(breaking_changes['api_changes'])}
+
+## Pre-Migration Checklist
+
+- [ ] Current test suite passing
+- [ ] Backup created / Git commit point marked
+- [ ] Dependencies compatibility checked
+- [ ] Team notified of upgrade
+
+## Migration Steps
+
+### Step 1: Update Dependencies
+
+```bash
+# Create a new branch
+git checkout -b upgrade/{package_name}-{target_version}
+
+# Update package
+npm install {package_name}@{target_version}
+
+# Update peer dependencies if needed
+{generate_peer_deps_commands(package_name, target_version)}
+```
+
+### Step 2: Address Breaking Changes
+
+{generate_breaking_change_fixes(breaking_changes)}
+
+### Step 3: Update Code Patterns
+
+{generate_code_updates(package_name, current_version, target_version)}
+
+### Step 4: Run Codemods (if available)
+
+{generate_codemod_commands(package_name, target_version)}
+
+### Step 5: Test & Verify
+
+```bash
+# Run linter to catch issues
+npm run lint
+
+# Run tests
+npm test
+
+# Run type checking
+npm run type-check
+
+# Manual testing checklist
+```
+
+{generate_test_checklist(package_name, breaking_changes)}
+
+### Step 6: Performance Validation
+
+{generate_performance_checks(package_name)}
+
+## Rollback Plan
+
+If issues arise, follow these steps to rollback:
+
+```bash
+# Revert package version
+git checkout package.json package-lock.json
+npm install
+
+# Or use the backup branch
+git checkout main
+git branch -D upgrade/{package_name}-{target_version}
+```
+
+## Common Issues & Solutions
+
+{generate_common_issues(package_name, target_version)}
+
+## Resources
+
+- [Official Migration Guide]({get_official_guide_url(package_name, target_version)})
+- [Changelog]({get_changelog_url(package_name, target_version)})
+- [Community Discussions]({get_community_url(package_name)})
+"""
+    
+    return guide
+```
+
+### 4. Incremental Upgrade Strategy
+
+Plan safe incremental upgrades:
+
+**Incremental Upgrade Planner**
+```python
+class IncrementalUpgrader:
+    def plan_incremental_upgrade(self, package_name, current, target):
+        """
+        Plan incremental upgrade path
+        """
+        # Get all versions between current and target
+        all_versions = self._get_versions_between(package_name, current, target)
+        
+        # Identify safe stopping points
+        safe_versions = self._identify_safe_versions(all_versions)
+        
+        # Create upgrade path
+        upgrade_path = self._create_upgrade_path(current, target, safe_versions)
+        
+        plan = f"""
+## Incremental Upgrade Plan: {package_name}
+
+### Current State
+- Version: {current}
+- Target: {target}
+- Total steps: {len(upgrade_path)}
+
+### Upgrade Path
+
+"""
+        for i, step in enumerate(upgrade_path, 1):
+            plan += f"""
+#### Step {i}: Upgrade to {step['version']}
+
+**Risk Level**: {step['risk_level']}
+**Breaking Changes**: {step['breaking_changes']}
+
+```bash
+# Upgrade command
+npm install {package_name}@{step['version']}
+
+# Test command
+npm test -- --updateSnapshot
+
+# Verification
+npm run integration-tests
+```
+
+**Key Changes**:
+{self._summarize_changes(step)}
+
+**Testing Focus**:
+{self._get_test_focus(step)}
+
+---
+"""
+        
+        return plan
+    
+    def _identify_safe_versions(self, versions):
+        """Identify safe intermediate versions"""
+        safe_versions = []
+        
+        for v in versions:
+            # Safe versions are typically:
+            # - Last patch of each minor version
+            # - Versions with long stability period
+            # - Versions before major API changes
+            if (self._is_last_patch(v, versions) or 
+                self._has_stability_period(v) or
+                self._is_pre_breaking_change(v)):
+                safe_versions.append(v)
+        
+        return safe_versions
+```
+
+### 5. Automated Testing Strategy
+
+Ensure upgrades don't break functionality:
+
+**Upgrade Test Suite**
+```javascript
+// upgrade-tests.js
+const { runUpgradeTests } = require('./upgrade-test-framework');
+
+async function testDependencyUpgrade(packageName, targetVersion) {
+    const testSuite = {
+        preUpgrade: async () => {
+            // Capture baseline
+            const baseline = {
+                unitTests: await runTests('unit'),
+                integrationTests: await runTests('integration'),
+                e2eTests: await runTests('e2e'),
+                performance: await capturePerformanceMetrics(),
+                bundleSize: await measureBundleSize()
+            };
+            
+            return baseline;
+        },
+        
+        postUpgrade: async (baseline) => {
+            // Run same tests after upgrade
+            const results = {
+                unitTests: await runTests('unit'),
+                integrationTests: await runTests('integration'),
+                e2eTests: await runTests('e2e'),
+                performance: await capturePerformanceMetrics(),
+                bundleSize: await measureBundleSize()
+            };
+            
+            // Compare results
+            const comparison = compareResults(baseline, results);
+            
+            return {
+                passed: comparison.passed,
+                failures: comparison.failures,
+                regressions: comparison.regressions,
+                improvements: comparison.improvements
+            };
+        },
+        
+        smokeTests: [
+            async () => {
+                // Critical path testing
+                await testCriticalUserFlows();
+            },
+            async () => {
+                // API compatibility
+                await testAPICompatibility();
+            },
+            async () => {
+                // Build process
+                await testBuildProcess();
+            }
+        ]
+    };
+    
+    return runUpgradeTests(testSuite);
+}
+```
+
+### 6. Compatibility Matrix
+
+Check compatibility across dependencies:
+
+**Compatibility Checker**
+```python
+def generate_compatibility_matrix(dependencies):
+    """
+    Generate compatibility matrix for dependencies
+    """
+    matrix = {}
+    
+    for dep_name, dep_info in dependencies.items():
+        matrix[dep_name] = {
+            'current': dep_info['current'],
+            'target': dep_info['latest'],
+            'compatible_with': check_compatibility(dep_name, dep_info['latest']),
+            'conflicts': find_conflicts(dep_name, dep_info['latest']),
+            'peer_requirements': get_peer_requirements(dep_name, dep_info['latest'])
+        }
+    
+    # Generate report
+    report = """
+## Dependency Compatibility Matrix
+
+| Package | Current | Target | Compatible With | Conflicts | Action Required |
+|---------|---------|--------|-----------------|-----------|-----------------|
+"""
+    
+    for pkg, info in matrix.items():
+        compatible = '✅' if not info['conflicts'] else '⚠️'
+        conflicts = ', '.join(info['conflicts']) if info['conflicts'] else 'None'
+        action = 'Safe to upgrade' if not info['conflicts'] else 'Resolve conflicts first'
+        
+        report += f"| {pkg} | {info['current']} | {info['target']} | {compatible} | {conflicts} | {action} |\n"
+    
+    return report
+
+def check_compatibility(package_name, version):
+    """Check what this package is compatible with"""
+    # Check package.json or requirements.txt
+    peer_deps = get_peer_dependencies(package_name, version)
+    compatible_packages = []
+    
+    for peer_pkg, peer_version_range in peer_deps.items():
+        if is_installed(peer_pkg):
+            current_peer_version = get_installed_version(peer_pkg)
+            if satisfies_version_range(current_peer_version, peer_version_range):
+                compatible_packages.append(f"{peer_pkg}@{current_peer_version}")
+    
+    return compatible_packages
+```
+
+### 7. Rollback Strategy
+
+Implement safe rollback procedures:
+
+**Rollback Manager**
+```bash
+#!/bin/bash
+# rollback-dependencies.sh
+
+# Create rollback point
+create_rollback_point() {
+    echo "📌 Creating rollback point..."
+    
+    # Save current state
+    cp package.json package.json.backup
+    cp package-lock.json package-lock.json.backup
+    
+    # Git tag
+    git tag -a "pre-upgrade-$(date +%Y%m%d-%H%M%S)" -m "Pre-upgrade snapshot"
+    
+    # Database snapshot if needed
+    if [ -f "database-backup.sh" ]; then
+        ./database-backup.sh
+    fi
+    
+    echo "✅ Rollback point created"
+}
+
+# Perform rollback
+rollback() {
+    echo "🔄 Performing rollback..."
+    
+    # Restore package files
+    mv package.json.backup package.json
+    mv package-lock.json.backup package-lock.json
+    
+    # Reinstall dependencies
+    rm -rf node_modules
+    npm ci
+    
+    # Run post-rollback tests
+    npm test
+    
+    echo "✅ Rollback complete"
+}
+
+# Verify rollback
+verify_rollback() {
+    echo "🔍 Verifying rollback..."
+    
+    # Check critical functionality
+    npm run test:critical
+    
+    # Check service health
+    curl -f http://localhost:3000/health || exit 1
+    
+    echo "✅ Rollback verified"
+}
+```
+
+### 8. Batch Update Strategy
+
+Handle multiple updates efficiently:
+
+**Batch Update Planner**
+```python
+def plan_batch_updates(dependencies):
+    """
+    Plan efficient batch updates
+    """
+    # Group by update type
+    groups = {
+        'patch': [],
+        'minor': [],
+        'major': [],
+        'security': []
+    }
+    
+    for dep, info in dependencies.items():
+        if info.get('has_security_vulnerability'):
+            groups['security'].append(dep)
+        else:
+            groups[info['update_type']].append(dep)
+    
+    # Create update batches
+    batches = []
+    
+    # Batch 1: Security updates (immediate)
+    if groups['security']:
+        batches.append({
+            'priority': 'CRITICAL',
+            'name': 'Security Updates',
+            'packages': groups['security'],
+            'strategy': 'immediate',
+            'testing': 'full'
+        })
+    
+    # Batch 2: Patch updates (safe)
+    if groups['patch']:
+        batches.append({
+            'priority': 'HIGH',
+            'name': 'Patch Updates',
+            'packages': groups['patch'],
+            'strategy': 'grouped',
+            'testing': 'smoke'
+        })
+    
+    # Batch 3: Minor updates (careful)
+    if groups['minor']:
+        batches.append({
+            'priority': 'MEDIUM',
+            'name': 'Minor Updates',
+            'packages': groups['minor'],
+            'strategy': 'incremental',
+            'testing': 'regression'
+        })
+    
+    # Batch 4: Major updates (planned)
+    if groups['major']:
+        batches.append({
+            'priority': 'LOW',
+            'name': 'Major Updates',
+            'packages': groups['major'],
+            'strategy': 'individual',
+            'testing': 'comprehensive'
+        })
+    
+    return generate_batch_plan(batches)
+```
+
+### 9. Framework-Specific Upgrades
+
+Handle framework upgrades:
+
+**Framework Upgrade Guides**
+```python
+framework_upgrades = {
+    'angular': {
+        'upgrade_command': 'ng update',
+        'pre_checks': [
+            'ng update @angular/core@{version} --dry-run',
+            'npm audit',
+            'ng lint'
+        ],
+        'post_upgrade': [
+            'ng update @angular/cli',
+            'npm run test',
+            'npm run e2e'
+        ],
+        'common_issues': {
+            'ivy_renderer': 'Enable Ivy in tsconfig.json',
+            'strict_mode': 'Update TypeScript configurations',
+            'deprecated_apis': 'Use Angular migration schematics'
+        }
+    },
+    'react': {
+        'upgrade_command': 'npm install react@{version} react-dom@{version}',
+        'codemods': [
+            'npx react-codemod rename-unsafe-lifecycles',
+            'npx react-codemod error-boundaries'
+        ],
+        'verification': [
+            'npm run build',
+            'npm test -- --coverage',
+            'npm run analyze-bundle'
+        ]
+    },
+    'vue': {
+        'upgrade_command': 'npm install vue@{version}',
+        'migration_tool': 'npx @vue/migration-tool',
+        'breaking_changes': {
+            '2_to_3': [
+                'Composition API',
+                'Multiple root elements',
+                'Teleport component',
+                'Fragments'
+            ]
+        }
+    }
+}
+```
+
+### 10. Post-Upgrade Monitoring
+
+Monitor application after upgrades:
+
+```javascript
+// post-upgrade-monitoring.js
+const monitoring = {
+    metrics: {
+        performance: {
+            'page_load_time': { threshold: 3000, unit: 'ms' },
+            'api_response_time': { threshold: 500, unit: 'ms' },
+            'memory_usage': { threshold: 512, unit: 'MB' }
+        },
+        errors: {
+            'error_rate': { threshold: 0.01, unit: '%' },
+            'console_errors': { threshold: 0, unit: 'count' }
+        },
+        bundle: {
+            'size': { threshold: 5, unit: 'MB' },
+            'gzip_size': { threshold: 1.5, unit: 'MB' }
+        }
+    },
+    
+    checkHealth: async function() {
+        const results = {};
+        
+        for (const [category, metrics] of Object.entries(this.metrics)) {
+            results[category] = {};
+            
+            for (const [metric, config] of Object.entries(metrics)) {
+                const value = await this.measureMetric(metric);
+                results[category][metric] = {
+                    value,
+                    threshold: config.threshold,
+                    unit: config.unit,
+                    status: value <= config.threshold ? 'PASS' : 'FAIL'
+                };
+            }
+        }
+        
+        return results;
+    },
+    
+    generateReport: function(results) {
+        let report = '## Post-Upgrade Health Check\n\n';
+        
+        for (const [category, metrics] of Object.entries(results)) {
+            report += `### ${category}\n\n`;
+            report += '| Metric | Value | Threshold | Status |\n';
+            report += '|--------|-------|-----------|--------|\n';
+            
+            for (const [metric, data] of Object.entries(metrics)) {
+                const status = data.status === 'PASS' ? '✅' : '❌';
+                report += `| ${metric} | ${data.value}${data.unit} | ${data.threshold}${data.unit} | ${status} |\n`;
+            }
+            
+            report += '\n';
+        }
+        
+        return report;
+    }
+};
+```
+
+## Output Format
+
+1. **Upgrade Overview**: Summary of available updates with risk assessment
+2. **Priority Matrix**: Ordered list of updates by importance and safety
+3. **Migration Guides**: Step-by-step guides for each major upgrade
+4. **Compatibility Report**: Dependency compatibility analysis
+5. **Test Strategy**: Automated tests for validating upgrades
+6. **Rollback Plan**: Clear procedures for reverting if needed
+7. **Monitoring Dashboard**: Post-upgrade health metrics
+8. **Timeline**: Realistic schedule for implementing upgrades
+
+Focus on safe, incremental upgrades that maintain system stability while keeping dependencies current and secure.
--- a/commands/legacy-modernize.md
+++ b/commands/legacy-modernize.md
@@ -0,0 +1,110 @@
+# Legacy Code Modernization Workflow
+
+Orchestrate a comprehensive legacy system modernization using the strangler fig pattern, enabling gradual replacement of outdated components while maintaining continuous business operations through expert agent coordination.
+
+[Extended thinking: The strangler fig pattern, named after the tropical fig tree that gradually envelops and replaces its host, represents the gold standard for risk-managed legacy modernization. This workflow implements a systematic approach where new functionality gradually replaces legacy components, allowing both systems to coexist during transition. By orchestrating specialized agents for assessment, testing, security, and implementation, we ensure each migration phase is validated before proceeding, minimizing disruption while maximizing modernization velocity.]
+
+## Phase 1: Legacy Assessment and Risk Analysis
+
+### 1. Comprehensive Legacy System Analysis
+- Use Task tool with subagent_type="legacy-modernizer"
+- Prompt: "Analyze the legacy codebase at $ARGUMENTS. Document technical debt inventory including: outdated dependencies, deprecated APIs, security vulnerabilities, performance bottlenecks, and architectural anti-patterns. Generate a modernization readiness report with component complexity scores (1-10), dependency mapping, and database coupling analysis. Identify quick wins vs complex refactoring targets."
+- Expected output: Detailed assessment report with risk matrix and modernization priorities
+
+### 2. Dependency and Integration Mapping
+- Use Task tool with subagent_type="architect-review"
+- Prompt: "Based on the legacy assessment report, create a comprehensive dependency graph showing: internal module dependencies, external service integrations, shared database schemas, and cross-system data flows. Identify integration points that will require facade patterns or adapter layers during migration. Highlight circular dependencies and tight coupling that need resolution."
+- Context from previous: Legacy assessment report, component complexity scores
+- Expected output: Visual dependency map and integration point catalog
+
+### 3. Business Impact and Risk Assessment
+- Use Task tool with subagent_type="business-analytics::business-analyst"
+- Prompt: "Evaluate business impact of modernizing each component identified. Create risk assessment matrix considering: business criticality (revenue impact), user traffic patterns, data sensitivity, regulatory requirements, and fallback complexity. Prioritize components using a weighted scoring system: (Business Value × 0.4) + (Technical Risk × 0.3) + (Quick Win Potential × 0.3). Define rollback strategies for each component."
+- Context from previous: Component inventory, dependency mapping
+- Expected output: Prioritized migration roadmap with risk mitigation strategies
+
+## Phase 2: Test Coverage Establishment
+
+### 1. Legacy Code Test Coverage Analysis
+- Use Task tool with subagent_type="unit-testing::test-automator"
+- Prompt: "Analyze existing test coverage for legacy components at $ARGUMENTS. Use coverage tools to identify untested code paths, missing integration tests, and absent end-to-end scenarios. For components with <40% coverage, generate characterization tests that capture current behavior without modifying functionality. Create test harness for safe refactoring."
+- Expected output: Test coverage report and characterization test suite
+
+### 2. Contract Testing Implementation
+- Use Task tool with subagent_type="unit-testing::test-automator"
+- Prompt: "Implement contract tests for all integration points identified in dependency mapping. Create consumer-driven contracts for APIs, message queue interactions, and database schemas. Set up contract verification in CI/CD pipeline. Generate performance baselines for response times and throughput to validate modernized components maintain SLAs."
+- Context from previous: Integration point catalog, existing test coverage
+- Expected output: Contract test suite with performance baselines
+
+### 3. Test Data Management Strategy
+- Use Task tool with subagent_type="data-engineering::data-engineer"
+- Prompt: "Design test data management strategy for parallel system operation. Create data generation scripts for edge cases, implement data masking for sensitive information, and establish test database refresh procedures. Set up monitoring for data consistency between legacy and modernized components during migration."
+- Context from previous: Database schemas, test requirements
+- Expected output: Test data pipeline and consistency monitoring
+
+## Phase 3: Incremental Migration Implementation
+
+### 1. Strangler Fig Infrastructure Setup
+- Use Task tool with subagent_type="backend-development::backend-architect"
+- Prompt: "Implement strangler fig infrastructure with API gateway for traffic routing. Configure feature flags for gradual rollout using environment variables or feature management service. Set up proxy layer with request routing rules based on: URL patterns, headers, or user segments. Implement circuit breakers and fallback mechanisms for resilience. Create observability dashboard for dual-system monitoring."
+- Expected output: API gateway configuration, feature flag system, monitoring dashboard
+
+### 2. Component Modernization - First Wave
+- Use Task tool with subagent_type="python-development::python-pro" or "golang-pro" (based on target stack)
+- Prompt: "Modernize first-wave components (quick wins identified in assessment). For each component: extract business logic from legacy code, implement using modern patterns (dependency injection, SOLID principles), ensure backward compatibility through adapter patterns, maintain data consistency with event sourcing or dual writes. Follow 12-factor app principles. Components to modernize: [list from prioritized roadmap]"
+- Context from previous: Characterization tests, contract tests, infrastructure setup
+- Expected output: Modernized components with adapters
+
+### 3. Security Hardening
+- Use Task tool with subagent_type="security-scanning::security-auditor"
+- Prompt: "Audit modernized components for security vulnerabilities. Implement security improvements including: OAuth 2.0/JWT authentication, role-based access control, input validation and sanitization, SQL injection prevention, XSS protection, and secrets management. Verify OWASP top 10 compliance. Configure security headers and implement rate limiting."
+- Context from previous: Modernized component code
+- Expected output: Security audit report and hardened components
+
+## Phase 4: Performance Validation and Optimization
+
+### 1. Performance Testing and Optimization
+- Use Task tool with subagent_type="application-performance::performance-engineer"
+- Prompt: "Conduct performance testing comparing legacy vs modernized components. Run load tests simulating production traffic patterns, measure response times, throughput, and resource utilization. Identify performance regressions and optimize: database queries with indexing, caching strategies (Redis/Memcached), connection pooling, and async processing where applicable. Validate against SLA requirements."
+- Context from previous: Performance baselines, modernized components
+- Expected output: Performance test results and optimization recommendations
+
+### 2. Progressive Rollout and Monitoring
+- Use Task tool with subagent_type="deployment-strategies::deployment-engineer"
+- Prompt: "Implement progressive rollout strategy using feature flags. Start with 5% traffic to modernized components, monitor error rates, latency, and business metrics. Define automatic rollback triggers: error rate >1%, latency >2x baseline, or business metric degradation. Create runbook for traffic shifting: 5% → 25% → 50% → 100% with 24-hour observation periods."
+- Context from previous: Feature flag configuration, monitoring dashboard
+- Expected output: Rollout plan with automated safeguards
+
+## Phase 5: Migration Completion and Documentation
+
+### 1. Legacy Component Decommissioning
+- Use Task tool with subagent_type="legacy-modernizer"
+- Prompt: "Plan safe decommissioning of replaced legacy components. Verify no remaining dependencies through traffic analysis (minimum 30 days at 0% traffic). Archive legacy code with documentation of original functionality. Update CI/CD pipelines to remove legacy builds. Clean up unused database tables and remove deprecated API endpoints. Document any retained legacy components with sunset timeline."
+- Context from previous: Traffic routing data, modernization status
+- Expected output: Decommissioning checklist and timeline
+
+### 2. Documentation and Knowledge Transfer
+- Use Task tool with subagent_type="documentation-generation::docs-architect"
+- Prompt: "Create comprehensive modernization documentation including: architectural diagrams (before/after), API documentation with migration guides, runbooks for dual-system operation, troubleshooting guides for common issues, and lessons learned report. Generate developer onboarding guide for modernized system. Document technical decisions and trade-offs made during migration."
+- Context from previous: All migration artifacts and decisions
+- Expected output: Complete modernization documentation package
+
+## Configuration Options
+
+- **--parallel-systems**: Keep both systems running indefinitely (for gradual migration)
+- **--big-bang**: Full cutover after validation (higher risk, faster completion)
+- **--by-feature**: Migrate complete features rather than technical components
+- **--database-first**: Prioritize database modernization before application layer
+- **--api-first**: Modernize API layer while maintaining legacy backend
+
+## Success Criteria
+
+- All high-priority components modernized with >80% test coverage
+- Zero unplanned downtime during migration
+- Performance metrics maintained or improved (P95 latency within 110% of baseline)
+- Security vulnerabilities reduced by >90%
+- Technical debt score improved by >60%
+- Successful operation for 30 days post-migration without rollbacks
+- Complete documentation enabling new developer onboarding in <1 week
+
+Target: $ARGUMENTS