Skip to content

Phase 6: Operate

Production operations including bug investigation, incident response, and continuous improvement.

Command: /6-operate

When to use

After successful deployment. This phase stays active for the lifetime of the running application. Return here whenever production issues arise.

What happens

Displays an operations menu with four main capabilities:

1. Bug Investigation (/investigate-bug)

Uses the bugfix-orchestrator to: - Search past solutions in docs/solutions/ first - Reproduce the issue with a minimal case - Analyze git history for related changes - Find root cause and guide the fix - Return to /4-review for fix validation

2. Incident Response (/incident-response)

Uses the incident-orchestrator for emergencies: - Severity assessment (Critical through Low) - Mitigation options (rollback, feature flag, hotfix) - Communication templates for stakeholders - Post-mortem process

3. Continuous Improvement (/compound)

Documents solved problems for future reference: - Adds solutions to docs/solutions/ - Detects patterns (3+ similar issues become critical patterns) - Builds institutional knowledge that all orchestrators consult

4. Knowledge Consolidation (/consolidate)

Synthesizes learnings into permanent documentation: - Updates specs with new architecture insights - Creates ADRs from decisions - Improves PRD based on production learnings

Output

  • Routing to the appropriate operations tool
  • Bug fix guidance with solution documentation
  • Incident response plans with communication templates
  • Updated institutional knowledge

Next step

For new features: return to Phase 2: Plan to start a new cycle.