| name | debug-workflow |
| description | MUST be activated through cc10x-orchestrator - do not use directly. Orchestrator coordinates this debug workflow with functionality-first approach. First understands what functionality is broken (user flow, admin flow, system flow), then debugs bugs affecting that functionality. Focuses on bugs that affect functionality, not generic debugging. Loads investigation skills and delegates to bug-investigator, code-reviewer, and integration-verifier sequentially. Use when orchestrator detects debug intent. |
| allowed-tools | Read, Grep, Glob, Task, Bash |
Debug Workflow - Functionality First
Functionality First Mandate
BEFORE debugging bugs, understand functionality:
What functionality is broken?
- What are the user flows? (what should happen)
- What are the admin flows? (what should happen)
- What are the system flows? (what should happen)
THEN debug - Debug bugs affecting that functionality
Use systematic approach - Apply debugging process AFTER functionality is understood
Systematic debugging with evidence-first verification, functionality-first approach.
Process
For complete instructions, see plugins/cc10x/skills/cc10x-orchestrator/workflows/debug.md.
Quick Reference
- Intake: confirm repro, errors/logs, recent changes
- Loop: bug-investigator -> code-reviewer -> integration-verifier (sequential)
- Evidence: logs + failing test -> fix -> GREEN; include Verification Summary
Output Format (REQUIRED)
MANDATORY TEMPLATE - Use exact structure from orchestrator:
# Debug Report
## Executive Summary
[2-3 sentences summarizing root cause, fix status, and overall resolution]
## Actions Taken
- Skills loaded: [list]
- Subagents invoked: [list]
- Bugs investigated: [list]
- Tools used: [list]
## Findings / Decisions
### Bug {name}
- **Root Cause**: [what failed and why]
- **Evidence**: [log excerpts, stack traces, code paths]
- **Fix**: [what changed, file:line]
- **Regression Test**: [test name, file:line]
- **Verification**: [command outputs showing RED → GREEN]
### Reproduction
- Steps: [detailed reproduction steps]
- Environment: [OS, dependencies, config]
- Error Messages: [full error messages]
- Logs: [relevant log snippets]
### Investigation Timeline
- [Hypothesis 1]: [result]
- [Hypothesis 2]: [result]
- [Root Cause Found]: [explanation]
### Fix & Regression Test
- Changes: [file:line diffs summary]
- Tests Added: [list]
- GREEN Proof: [command outputs]
### Reviews & Integration
- code-reviewer findings: [resolved/open]
- integration-verifier scenarios: [pass/fail with logs]
## Verification Summary
Scope: <bugs investigated>
Bugs fixed: <list>
Criteria: <what was verified>
Commands:
- <command> -> exit <code>
Evidence:
- <log snippets showing bug>
- <test output showing RED then GREEN>
- <integration test results>
Residual risk: <items to monitor, edge cases not covered>
## Recommendations / Next Steps
[Prioritized: Monitoring setup, additional tests, prevention measures]
## Open Questions / Assumptions
[If escalation needed, external dependencies unavailable, or assumptions made]
Validation Checklist:
- Executive Summary present (2-3 sentences)
- Verification Summary includes commands with exit codes
- Root cause clearly explained with evidence
- Regression test documented with RED → GREEN proof
- Reviews and integration status documented
- Recommendations prioritized
- All subagents/skills documented in Actions Taken