pain-point-manager
Automatically capture, update, and manage development pain points. Use when user mentions friction, blockers, workarounds, or wants to track development obstacles.
When & Why to Use This Skill
The Pain Point Manager is a proactive Claude skill designed to optimize the software development lifecycle by automatically identifying, documenting, and prioritizing technical friction. It transforms casual mentions of frustration or blockers into a structured tracking system, helping engineering teams eliminate bottlenecks and improve Developer Experience (DX). By utilizing a data-driven scoring model and automated weekly reviews, it ensures that technical debt and workflow inefficiencies are systematically addressed rather than forgotten.
Use Cases
- Automated Friction Logging: Instantly capture and document recurring environment issues or 'annoying' manual workarounds mentioned during coding sessions to ensure they are tracked for future resolution.
- Data-Driven Prioritization: Use the built-in scoring system (Impact x Frequency) to objectively identify which development blockers are causing the most significant delays across the team.
- Weekly Retrospective Support: Generate automated summaries of resolved pain points and new obstacles to provide actionable insights for sprint planning and team retrospectives.
- Contextual Knowledge Retention: Maintain a living archive of technical debt, linking specific file paths and temporary workarounds to unique IDs to prevent the loss of institutional knowledge.
| name | Pain Point Manager |
|---|---|
| description | Automatically capture, update, and manage development pain points. Use when user mentions friction, blockers, workarounds, or wants to track development obstacles. |
| allowed-tools | Read, Write, Edit, Grep |
Pain Point Manager Skill
Purpose
Automatically manage the pain points tracking system by capturing new pain points, updating existing ones, archiving resolved items, and extracting patterns.
Auto-Activation Triggers
This skill activates when the user:
- Mentions "pain point", "friction", "blocker", "workaround"
- Says "that was frustrating" or similar sentiment
- Describes manual workarounds or repetitive tasks
- Mentions "we should fix this" or "this is annoying"
- Asks to add/update pain points
- Requests weekly pain point review
Core Operations
1. Capture New Pain Point
Trigger phrases:
- "This is a pain point"
- "Add this to pain points"
- "This keeps causing issues"
Workflow:
- Read
.claude/pain-points/active-pain-points.md - Determine next available PAIN-ID
- Gather context automatically (file paths, frequency, impact)
- Classify priority:
- Critical: "blocking", "can't deploy", "broken"
- High: "daily", "multiple times", "significant delay"
- Medium: "weekly", "annoying", "workaround exists"
- Low: "occasionally", "nice to have"
- Add new entry with complete metadata
- Confirm capture with ID reference
Template:
### [PAIN-XXXX] Brief action-oriented description
- **Impact**: Specific scope
- **Frequency**: Daily/Weekly/Occasional
- **First Noted**: YYYY-MM-DD
- **Context**: File paths, scenarios
- **Workaround**: Current approach
- **Potential Solution**: Ideas if discussed
2. Update Existing Pain Point
Update Types:
- Frequency increase
- Priority change
- Status change (resolved)
- Context addition
- Solution progress
3. Weekly Review Workflow
Steps:
- Load active pain points
- Check recent work for friction mentions
- Update frequency counts
- Generate focus areas
- Recommend top 2-3 priorities
Review Output:
## 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.
3. Keep It Current
Weekly reviews, monthly archival, quarterly pattern analysis.
4. Link Evidence
File paths, task IDs, commits that show the pain.
5. Focus on Actionability
Every pain point needs clear description, measurable impact, and potential solution path.
Integration
With Git Commits
Reference in commit messages: "Fix: [description] (PAIN-XXXX)"
With Memory System
- Episodic memory feeds discovery
- Pain point patterns update procedural memory
Skill Metadata
Version: 1.0.0 Category: Development Experience & Quality Maintenance: Weekly active use, Monthly archival