Files
ForgeLM/.agents/skills/debugging-protocol/assets/debugging-session-template.md
T

83 lines
1.5 KiB
Markdown

# Debugging Session: [Issue Name]
## SYSTEM CONTEXT
[Describe the system components involved, relevant technologies, and the general environment.]
## PROBLEM STATEMENT
**Symptom**:
[Describe the observable issue. What is happening vs what should happen?]
**Hypotheses**:
1. **[Layer/Component] Hypothesis**: [Description of potential cause]
2. **[Layer/Component] Hypothesis**: [Description of potential cause]
## VALIDATION TASKS
### Task 1: [Task Name]
**Objective**: [What specific fact or behavior are we verifying?]
**Steps**:
1. [Step 1]
2. [Step 2]
3. ...
**Required Code Pattern/Command**:
```[language]
[Code or command to execute]
```
**Success Criteria**: [What specific output confirms or denies the hypothesis?]
---
### Task 2: [Task Name]
**Objective**: ...
...
## OUTPUT FORMAT (for each task)
```markdown
### Task N: [Task Name]
**Status**: ✅ VALIDATED / ❌ FAILED / ⚠️ INCONCLUSIVE
**Findings**:
- [Observation 1]
- [Observation 2]
**Evidence**:
[Logs, screenshots, output]
**Conclusion**: [Impact on hypotheses]
```
## FINAL ROOT CAUSE DETERMINATION
```markdown
## ROOT CAUSE ANALYSIS SUMMARY
**Primary Root Cause**: [Component/Reason]
**Confidence Level**: [High / Medium / Low]
**Supporting Evidence**:
1. [Evidence 1]
2. [Evidence 2]
**Recommended Fix Priority**:
1. [Fix A]
2. [Fix B]
**Risks if Wrong**:
- [Risk 1]
```
## EXECUTION GUIDELINES
- Execute tasks in order.
- Document all commands and outputs.
- Adapt the plan if new information invalidates later tasks.