feat: add oncall mode for structured incident response

Author: saneroen

.roo/commands/k8s-troubleshoot.md

@@ -3,6 +3,6 @@ description: "Run Kubernetes troubleshooting workflow"
 mode: oncall
 ---
 
-Execute the Kubernetes troubleshooting workflow from `.roo/workflows/oncall/k8s-troubleshooting.md`.
+Execute the Kubernetes troubleshooting workflow from `.roo/rules-oncall/k8s-troubleshooting.md`.
 
 Read the workflow file and follow it step-by-step to troubleshoot the Kubernetes issue.

.roo/commands/oncall-workflow.md

@@ -4,11 +4,13 @@ argument-hint: "[workflow-name]"
 mode: oncall
 ---
 
-Execute an oncall workflow. Provide the workflow name as an argument.
+Execute an oncall workflow. The workflow name is provided as an argument.
 
-Examples:
+Read and execute the workflow file from `.roo/rules-oncall/{workflow-name}.md` step-by-step.
+
+If no workflow name is provided, list available workflows in `.roo/rules-oncall/` and ask the user which one to execute.
 
-- `/oncall-workflow k8s-troubleshooting` - Run Kubernetes troubleshooting
-- `/oncall-workflow service-specific/example-service-runbook` - Run service runbook
+Examples:
 
-The workflow will be read from `.roo/workflows/oncall/{workflow-name}.md` and executed step-by-step.
+- `/oncall-workflow k8s-troubleshooting` - Execute `k8s-troubleshooting.md`
+- `/oncall-workflow service-specific/example-service-runbook` - Execute `service-specific/example-service-runbook.md`

.roo/rules-oncall/1_workflow_overview.md

@@ -4,7 +4,7 @@ This directory contains workflow files that are automatically loaded when using
 
 ## Adding Your Workflows
 
-Workflows should be placed in `.roo/workflows/oncall/`. Create markdown files for each workflow you need:
+Workflows should be placed in `.roo/rules-oncall/`. Create markdown files for each workflow you need:
 
 - Incident response procedures
 - Page handling workflows
@@ -26,7 +26,7 @@ Each workflow should follow a clear structure:
 When handling an oncall task:
 
 1. Identify which workflow applies to your situation
-2. Read the workflow file from `.roo/workflows/oncall/`
+2. Read the workflow file from `.roo/rules-oncall/`
 3. Follow the steps sequentially
 4. Use MCP tools as specified in the workflow
 5. Document all actions in incident logs

…/workflows/oncall/k8s-troubleshooting.md .roo/rules-oncall/k8s-troubleshooting.md.roo/workflows/oncall/k8s-troubleshooting.md renamed to .roo/rules-oncall/k8s-troubleshooting.md .roo/workflows/oncall/k8s-troubleshooting.md renamed to .roo/rules-oncall/k8s-troubleshooting.md

@@ -261,8 +261,8 @@ customModes:
     groups:
       - read
       - - edit
-        - fileRegex: (incidents/.*\.md$|logs/.*\.md$|\.roo/workflows/oncall/.*\.md$|\.roo/rules-oncall/.*\.md$)
-          description: Incident logs, log files, workflow files, and oncall documentation
+        - fileRegex: (incidents/.*\.md$|logs/.*\.md$|\.roo/rules-oncall/.*\.md$)
+          description: Incident logs, log files, and oncall workflow files
       - command
       - mcp
     customInstructions: |-
@@ -271,7 +271,7 @@ customModes:
       When handling oncall tasks, follow this structured approach:
 
       1. **Identify the Workflow**
-         - Read the appropriate workflow file from `.roo/workflows/oncall/` or `.roo/rules-oncall/`
+         - Read the appropriate workflow file from `.roo/rules-oncall/`
          - For Kubernetes issues: Use `k8s-troubleshooting.md`
          - For specific services: Check `service-specific/` directory for service runbooks
          - Add your own workflows as needed
@@ -303,13 +303,11 @@ customModes:
 
       ## Available Workflows
 
-      Workflows are stored in `.roo/workflows/oncall/`:
+      Workflows are stored in `.roo/rules-oncall/` and are automatically loaded as context:
       - Example: `k8s-troubleshooting.md` - Kubernetes troubleshooting workflow
       - `service-specific/` - Service-specific runbooks (e.g., `example-service-runbook.md`)
       - Add your own workflow markdown files as needed
 
-      Workflows in `.roo/rules-oncall/` are automatically loaded and available as context.
-
       ## MCP Integration
 
       This mode has access to MCP tools. Use them to: