Mission: OPTIMIZE ⚡

May 9, 2026 · View on GitHub

Performance Optimization and System Enhancement

Mission Code: OPTIMIZE
Estimated Duration: 3-6 hours
Complexity: Medium to High
Squad Required: Architect, Developer, Analyst

Mission Briefing

Systematically analyze and improve system performance, identifying bottlenecks and implementing targeted optimizations. Transform slow, resource-intensive operations into efficient, scalable solutions.

Required Inputs

  1. Performance Metrics (required) - Current performance data or issues
  2. System/Component Scope (required) - Area of focus for optimization
  3. Performance Goals (optional) - Target metrics or SLA requirements

Mission Phases

Phase 1: Performance Analysis and Profiling (45-60 minutes)

Lead: @analyst
Support: @architect
Objective: Identify performance bottlenecks and optimization opportunities

Tasks:

  • Analyze current performance metrics and baselines
  • Profile system resource usage (CPU, memory, I/O, network)
  • Identify slowest operations and bottlenecks
  • Map user experience impact areas
  • Prioritize optimization opportunities by impact/effort

Success Criteria:

  • Performance bottlenecks identified
  • Resource usage patterns understood
  • Optimization priorities established
  • Baseline metrics documented

Phase 2: Architecture Review and Strategy (45-60 minutes)

Lead: @architect
Support: @analyst, @developer
Objective: Design optimization strategy and architectural improvements

Tasks:

  • Review current architecture for optimization opportunities
  • Design caching strategies and data access patterns
  • Plan database optimization and query improvements
  • Evaluate scaling strategies (horizontal vs vertical)
  • Design monitoring and measurement approach

Success Criteria:

  • Optimization strategy defined
  • Architectural improvements planned
  • Caching strategy designed
  • Scaling approach determined

Phase 3: Database and Query Optimization (60-90 minutes)

Lead: @developer
Support: @architect
Objective: Optimize database performance and data access

Tasks:

  • Analyze and optimize slow database queries
  • Add appropriate database indexes
  • Implement query optimization techniques
  • Optimize data models and relationships
  • Implement connection pooling and caching

Success Criteria:

  • Query performance improved
  • Database indexes optimized
  • Data access patterns efficient
  • Connection handling optimized

Phase 4: Code and Algorithm Optimization (60-120 minutes)

Lead: @developer
Support: @architect
Objective: Optimize application code and algorithms

Tasks:

  • Optimize critical code paths and algorithms
  • Implement efficient data structures
  • Reduce computational complexity
  • Optimize memory usage and garbage collection
  • Implement asynchronous operations where beneficial

Success Criteria:

  • Code performance improved
  • Algorithms more efficient
  • Memory usage optimized
  • Asynchronous operations implemented

Phase 5: Caching and Resource Optimization (45-75 minutes)

Lead: @developer
Support: @architect
Objective: Implement caching strategies and optimize resource usage

Tasks:

  • Implement application-level caching (Redis, Memcached)
  • Add HTTP caching headers and CDN optimization
  • Optimize static asset delivery and compression
  • Implement resource pooling and reuse
  • Optimize API response sizes and formats

Success Criteria:

  • Caching implemented effectively
  • Static assets optimized
  • Resource usage minimized
  • API responses optimized

Phase 6: Testing and Validation (30-45 minutes)

Lead: @analyst
Support: @developer
Objective: Validate optimization results and measure improvements

Tasks:

  • Run performance tests and benchmarks
  • Compare before/after metrics
  • Validate optimization impact on user experience
  • Test system stability under load
  • Document performance improvements

Success Criteria:

  • Performance improvements validated
  • Metrics show significant gains
  • System stability maintained
  • Results documented

Optimization Categories

Frontend Performance

  • JavaScript Optimization: Bundle splitting, lazy loading, tree shaking
  • CSS Optimization: Critical CSS, unused CSS removal
  • Image Optimization: Compression, lazy loading, modern formats
  • Network Optimization: HTTP/2, resource hints, CDN usage

Backend Performance

  • API Optimization: Response time, payload size, caching
  • Database Optimization: Query optimization, indexing, connection pooling
  • Server Optimization: Resource usage, concurrent handling
  • Algorithm Optimization: Time/space complexity improvements

Infrastructure Performance

  • Scaling: Horizontal scaling, load balancing
  • Caching: Multi-level caching strategies
  • CDN: Content delivery optimization
  • Monitoring: Performance tracking and alerting

Common Variations

Database-Heavy Optimization

  • Duration: 4-6 hours
  • Focus: Query optimization, indexing, data modeling
  • Tools: Query analyzers, database profilers

Frontend Performance Focus

  • Duration: 3-5 hours
  • Focus: Bundle optimization, loading performance, UX metrics
  • Tools: Lighthouse, WebPageTest, Bundle analyzers

API Performance Optimization

  • Duration: 2-4 hours
  • Focus: Response times, throughput, caching
  • Tools: Load testing, APM tools, profilers

Infrastructure Scaling

  • Duration: 4-8 hours
  • Focus: Horizontal scaling, load balancing, caching
  • Tools: Load balancers, CDNs, monitoring tools

Success Metrics

Performance Metrics

  • Response Time: 50%+ improvement in critical operations
  • Throughput: Increased requests per second
  • Resource Usage: Reduced CPU/memory consumption
  • Load Time: Faster page/application loading

Business Metrics

  • User Experience: Improved user satisfaction scores
  • Conversion Rate: Better performance leads to higher conversions
  • Cost Efficiency: Reduced infrastructure costs
  • Reliability: Fewer performance-related issues

Tools and Technologies

Profiling Tools

  • Application Profilers: New Relic, DataDog, AppDynamics
  • Database Profilers: Query analyzers, explain plans
  • Frontend Profilers: Chrome DevTools, Lighthouse
  • Custom Profiling: Performance.now(), benchmarking

Testing Tools

  • Load Testing: Artillery, JMeter, k6
  • Frontend Testing: WebPageTest, Lighthouse CI
  • Database Testing: Database-specific load testing
  • Synthetic Monitoring: Pingdom, StatusPage

Optimization Tools

  • Bundlers: Webpack, Rollup, Vite
  • Compressors: Gzip, Brotli, image optimizers
  • CDNs: CloudFlare, AWS CloudFront, Fastly
  • Caching: Redis, Memcached, Varnish

Monitoring and Maintenance

Continuous Monitoring

  • Performance Dashboards: Real-time metrics tracking
  • Alerting: Performance degradation notifications
  • Trend Analysis: Performance trends over time
  • User Experience: Real user monitoring (RUM)

Regular Reviews

  • Monthly: Performance metric reviews
  • Quarterly: Deep performance analysis
  • Release-based: Performance impact assessment
  • Incident-driven: Post-incident optimization

Integration Points

  • Follows: BUILD, MIGRATE, INTEGRATE missions
  • Enables: Better user experience, cost savings
  • Coordinates with: Infrastructure, monitoring systems
  • Requires: Performance baselines, monitoring tools

Mission Command: /coord optimize [performance-metrics] [system-scope] [performance-goals]

"Optimization is not about making things faster; it's about making the right things fast."

Post-Mission Cleanup Decision

After completing this mission, decide on cleanup approach based on project status:

✅ Milestone Transition (Every 2-4 weeks)

When: This mission completes a major project milestone, but more work remains.

Actions (30-60 min):

  1. Extract lessons to lessons/[category]/ from progress.md
  2. Archive milestone-relevant Phase Handoff blocks from agent-context.md if needed
  3. Clean agent-context.md (retain essentials, archive historical details)
  4. Continue using agent-context.md (Phase Handoff blocks accumulate across milestones)
  5. Update project-plan.md with next milestone tasks

See: templates/cleanup-checklist.md Section A for detailed steps

🎯 Project Completion (Mission accomplished!)

When: All project objectives achieved, ready for new mission.

Actions (1-2 hours):

  1. Extract ALL lessons from entire progress.md to lessons/
  2. Create mission archive in archives/missions/mission-[name]-YYYY-MM-DD/
  3. Update CLAUDE.md with system-level learnings
  4. Archive all tracking files (project-plan.md, progress.md, etc.)
  5. Prepare fresh start for next mission

See: templates/cleanup-checklist.md Section B for detailed steps

🔄 Continue Active Work (No cleanup needed)

When: Mission complete but continuing active development in same phase.

Actions: Update progress.md and project-plan.md, continue working.

Reference: See project/field-manual/project-lifecycle-guide.md for complete lifecycle management procedures.