Automatically manage the pain points tracking system by capturing new pain points, updating existing ones, archiving resolved items, and extracting patterns.
## Weekly Pain Point Review - YYYY-MM-DD
### Current State
- **Total Pain Points**: X
- **New This Week**: X
- **Resolved This Week**: X
### Focus Areas
**Quick Wins** (High Impact, Low Effort):
1. [PAIN-XXXX]: Description
**Strategic Investments** (High Impact, High Effort):
1. [PAIN-XXXX]: Description
### Next Steps
1. Approve focus areas
2. Create tasks for priorities
3. Next review: YYYY-MM-DD
4. Archive Resolved Items
Items >30 days old in "Recently Resolved" move to archive
Generate archival summary with resolution details
Track biggest wins and common themes
Priority Scoring
Calculate: (Impact x Frequency) + Urgency Modifier
Impact Score (1-10):
10: All deployments/team blocked
7-9: Major feature or multiple people affected
4-6: Single feature or occasional impact
1-3: Individual developer, specific scenario
Frequency Score (1-10):
10: Multiple times per day
7-9: Daily
4-6: Weekly
1-3: Monthly or less
Auto-Prioritization:
Score 15+: Critical
Score 10-14: High
Score 5-9: Medium
Score <5: Low
Best Practices
1. Be Proactive
Listen for friction language and offer to capture without being asked.
2. Be Specific
Don't accept "deployment is slow" - require measurable details.