File size: 1,825 Bytes
292d92c |
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 |
Generate comprehensive documentation for project blockers and troubleshooting efforts.
Your task:
1. Create detailed blocker documentation covering:
**Problem Statement:**
- What is blocked
- When it started
- Impact on project
- Severity level
**Troubleshooting Steps Taken:**
- Step-by-step actions attempted
- Tools and methods used
- Diagnostic commands run
- Configuration changes tried
**Unsuccessful Attempts:**
- What didn't work
- Why approaches failed
- Dead ends encountered
- Misleading solutions tried
**Blockers Identified:**
- Root cause analysis
- Technical constraints
- Knowledge gaps
- External dependencies
- Resource limitations
**Suggested Next Steps:**
- Potential solutions to try
- Alternative approaches
- Resources to consult
- Experts to contact
- Workarounds available
2. Format as comprehensive reference document:
```markdown
# Blocker Documentation - [Issue Name]
**Date:** [YYYY-MM-DD]
**Priority:** [High/Medium/Low]
**Status:** [Blocked/Investigating/Resolved]
## Problem Description
[Detailed description]
## Troubleshooting Timeline
1. [Time] - Tried approach A
- Result: Failed because...
2. [Time] - Investigated possibility B
- Result: Not applicable because...
## What We Know
- Fact 1
- Fact 2
## What We Don't Know
- Unknown 1
- Unknown 2
## Recommended Actions
1. [Action with rationale]
2. [Action with rationale]
## References
- [Links to documentation]
- [Stack Overflow threads]
- [Related issues]
```
3. Save to docs/blockers/ or similar location
4. Enable continuity for next agent or session
Create comprehensive blocker documentation for effective knowledge transfer and problem resolution.
|