Detects when user reports issues with recently completed work and suggests reopening relevant tasks, user stories, or increments. Auto-activates on keywords: not working, broken, bug, issue, problem, failing, error, crash, regression, still broken, incorrect, missing, wrong. Scans active and recently completed (7 days) work to find related items. Provides smart suggestions with relevance scoring.
Inherits all available tools
Additional assets for this skill
This skill inherits all available tools. When active, it can use any tool Claude has access to.
When you report an issue with recently completed work, I'll automatically:
I automatically activate when you mention these keywords:
User: "The GitHub sync isn't working, it was just completed yesterday"
I'll respond with:
š Scanning recent work...
Found 2 related item(s) in recent work:
š¦ INCREMENT: 0031-external-tool-status-sync
Increment: 0031-external-tool-status-sync
Completed: 2 days ago
Relevance: 15 points
Matched: github, sync
ā TASK: T-003 GitHub Content Sync
Increment: 0031-external-tool-status-sync
Completed: 1 day ago
Relevance: 14 points
Matched: github, sync
š” Suggested action:
/sw:reopen 0031-external-tool-status-sync --reason "GitHub sync not working"
Would you like me to:
1. Reopen the entire increment (checks WIP limits)
2. Reopen just task T-003 (targeted fix)
3. Show me the WIP status first
User: "The authentication is broken after the recent deployment"
I'll respond with:
š Scanning recent work...
Found 3 related item(s) in recent work:
ā TASK: T-012 Authentication Service
Increment: 0025-user-auth
Completed: 3 days ago
Relevance: 10 points
Matched: authentication
ā TASK: T-014 JWT Token Validation
Increment: 0025-user-auth
Completed: 3 days ago
Relevance: 7 points
Matched: authentication
š” Suggested action:
/sw:reopen 0025-user-auth --task T-012 --reason "Authentication broken after deployment"
ā ļø Note: Increment 0025 was completed 3 days ago. Consider checking deployment config first.
User: "The payment flow is not working"
I'll respond with:
š Scanning recent work...
š No related work found in recent activity (last 7 days)
The payment functionality might be:
1. From an older increment (>7 days ago)
2. Not yet implemented
3. Part of external dependencies
Would you like me to:
1. Search all increments (not just recent)
2. Create a new bug increment for investigation
3. Check the backlog for related work
From your message, I extract relevant keywords:
I scan:
I assign relevance scores using:
I provide:
/sw:reopen command# Reopen entire increment
/sw:reopen 0031-external-tool-status-sync --reason "GitHub sync failing"
# Check WIP limits first (recommended)
/sw:status
# Reopen single task (surgical fix)
/sw:reopen 0031 --task T-003 --reason "GitHub API 500 error"
# Reopen multiple related tasks
/sw:reopen 0031 --user-story US-001 --reason "All GitHub features broken"
# Use --force for critical production issues
/sw:reopen 0031 --force --reason "Production down, critical fix needed"
Before suggesting increment reopen, I check:
Example Warning:
ā ļø WIP LIMIT WARNING:
Current active: 2 features
Limit: 2 features
Reopening 0031-external-tool-status-sync will EXCEED the limit!
Options:
1. Pause another feature first: /sw:pause 0030
2. Complete another feature: /sw:done 0029
3. Force reopen (not recommended): --force
I work seamlessly with:
/sw:reopen - Execute reopen action/sw:status - Check WIP limits/sw:progress - See increment progress/sw:pause - Pause another increment to make roomI don't activate for:
/sw:increment)/sw:status)I only activate when you explicitly report something is broken/not working.
Core Logic:
RecentWorkScanner to find matchesSmart Features:
I'm successful when:
Auto-loads when: You report issues with recently completed work
Commands: /sw:reopen, /sw:status
Related Skills: increment-planner, tdd-workflow