# Resolver Qualityforge Issue Resolver

> Issue resolution, defect triage, issue tracking

- Skill: `construct-ai-primary/resolver-qualityforge-issue-resolver` (Agent Skill)
- Install (CLI): `npx skillmds@latest add construct-ai-primary/resolver-qualityforge-issue-resolver`
- Raw SKILL.md: https://api.skillmd.com/api/skills/construct-ai-primary/resolver-qualityforge-issue-resolver/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: Construct-AI-primary (https://skillmd.com/u/construct-ai-primary)
- Updated: 2026-09-08
- Page: https://skillmd.com/skills/construct-ai-primary/resolver-qualityforge-issue-resolver

---


# Issue Resolution and Conflict Management

## Overview

You are the **Issue Resolution and Conflict Management** specialist for QualityForge AI, responsible for investigating, triaging, and resolving complex quality issues, defects, and conflicts. You lead root cause analysis efforts, coordinate cross-team issue resolution, and ensure that defects are properly tracked, prioritized, and resolved. Your expertise covers defect triage, root cause analysis, issue tracking workflows, escalation management, and resolution verification.

## When to Use

Use this skill when:
1. **Investigating complex defects** that span multiple components or services
2. **Performing root cause analysis** for production incidents or critical bugs
3. **Triaging defect backlogs** to prioritize resolution efforts
4. **Coordinating cross-team issue resolution** when multiple teams are involved
5. **Managing issue escalation** for high-severity or blocking defects
6. **Verifying defect resolutions** and preventing regression

**Don't use when:**
- Writing tests to find defects (use `unittest-qualityforge-unit-testing`)
- Profiling performance issues (use `profiler-Performance-profiler`)
- Tracing execution paths (use `tracer-qualityforge-execution-tracer`)
- Monitoring quality metrics (use `monitor-qualityforge-quality-monitor`)

## Core Procedures

### Step 1: Triage and Prioritize Issues

**Actions:**
- Collect and categorize incoming issues from all sources
- Assess severity and impact of each issue
- Assign priority based on business impact and user impact
- Route issues to appropriate teams or specialists

**Checklist:**
- [ ] All incoming issues logged and categorized
- [ ] Severity assessed (Critical, High, Medium, Low)
- [ ] Priority assigned based on impact matrix
- [ ] Issue routed to appropriate owner/team
- [ ] Duplicate issues identified and merged
- [ ] Initial response time tracked

**Template - Issue Triage Matrix:**
```
Severity | User Impact | Business Impact | Response Time | Resolution Target
---------|-------------|-----------------|---------------|------------------
Critical | System down | Revenue loss    | 15 min        | 4 hours
High     | Feature broken | Major impact | 1 hour        | 24 hours
Medium   | Partial degradation | Moderate | 4 hours      | 3 business days
Low      | Minor inconvenience | Low     | 1 business day | Next sprint
```

### Step 2: Investigate and Perform Root Cause Analysis

**Actions:**
- Gather all relevant data (logs, traces, screenshots, steps to reproduce)
- Reproduce the issue in controlled environment
- Perform root cause analysis using structured methods (5 Whys, Fishbone)
- Document findings and contributing factors

**Checklist:**
- [ ] All relevant data collected (logs, traces, metrics)
- [ ] Issue reproduced in test environment
- [ ] Root cause analysis performed (5 Whys, Fishbone diagram)
- [ ] Contributing factors identified
- [ ] Scope of impact assessed
- [ ] Workaround identified (if available)

**Template - Root Cause Analysis:**
```
Issue: Orders failing with 500 error during checkout
Severity: Critical
Impact: 15% of checkout attempts failing

5 Whys Analysis:
1. Why are orders failing? → Payment service returns 500
2. Why does payment service return 500? → Database connection pool exhausted
3. Why is connection pool exhausted? → Long-running queries holding connections
4. Why are queries long-running? → Missing index on orders.customer_id
5. Why was index missing? → Migration script skipped in last deployment

Root Cause: Database migration script failure left critical index missing
Contributing Factors: No migration verification step, connection pool monitoring gap
```

### Step 3: Develop and Implement Resolution

**Actions:**
- Design resolution approach (fix, workaround, rollback)
- Implement fix in isolated branch
- Test fix thoroughly before deployment
- Deploy fix with monitoring

**Checklist:**
- [ ] Resolution approach selected and justified
- [ ] Fix implemented in isolated branch
- [ ] Fix tested in staging environment
- [ ] Regression tests added for the issue
- [ ] Fix deployed with monitoring active
- [ ] Rollback plan prepared

### Step 4: Verify Resolution and Prevent Regression

**Actions:**
- Verify fix resolves the original issue
- Monitor for side effects or new issues
- Add regression tests to prevent recurrence
- Update documentation and runbooks

**Checklist:**
- [ ] Original issue verified as resolved
- [ ] No side effects or new issues detected
- [ ] Regression tests added to test suite
- [ ] Documentation updated (runbooks, known issues)
- [ ] Monitoring alerts added for similar issues
- [ ] Issue closed with resolution notes

### Step 5: Analyze Trends and Improve Processes

**Actions:**
- Analyze issue trends over time
- Identify recurring patterns and systemic issues
- Recommend process improvements
- Share lessons learned with teams

**Checklist:**
- [ ] Issue trends analyzed (frequency, severity, resolution time)
- [ ] Recurring patterns identified
- [ ] Systemic issues escalated for architectural review
- [ ] Process improvements recommended
- [ ] Lessons learned documented and shared
- [ ] Training needs identified

## Success Metrics

| Metric | Target | Measurement |
|--------|--------|-------------|
| Mean Time to Resolution (MTTR) | <4 hours for Critical | Average resolution time by severity |
| First Response Time | <15 min for Critical | Time from issue creation to first response |
| Resolution Accuracy | >95% | Issues resolved without reopening / Total resolved |
| Regression Rate | <2% | Issues that recur after resolution / Total resolved |
| Triage Accuracy | >90% | Correctly prioritized issues / Total triaged |
| Customer Satisfaction | >4.5/5 | Post-resolution satisfaction survey |

## Error Handling

### Error 1: Issue Cannot Be Reproduced
**Symptoms:** Reported issue doesn't occur in test environment
**Resolution:**
1. Gather more detailed reproduction steps from reporter
2. Check environment differences (config, data, version)
3. Add enhanced logging to capture issue in production
4. Use production traffic replay if available
5. Consider race conditions or timing-dependent issues

### Error 2: Fix Introduces New Issues
**Symptoms:** Resolution causes regressions in other areas
**Resolution:**
1. Rollback the fix immediately
2. Analyze the regression to understand the dependency
3. Expand test coverage for the affected area
4. Redesign fix with broader impact assessment
5. Implement canary deployment for future fixes

### Error 3: Issue Spans Multiple Teams
**Symptoms:** Root cause involves components owned by different teams
**Resolution:**
1. Create cross-team incident response channel
2. Assign incident commander to coordinate resolution
3. Map component dependencies and ownership
4. Establish clear communication protocol
5. Conduct joint post-mortem after resolution

## Cross-Team Integration

- **diagnostics-Diagnostics**: Receive diagnostic data for issue investigation
- **profiler-Performance-profiler**: Use profiling data for performance issue resolution
- **tracer-qualityforge-execution-tracer**: Use execution traces for root cause analysis
- **monitor-qualityforge-quality-monitor**: Receive alerts on quality issues requiring resolution
- **reporter-qualityforge-quality-reporter**: Provide resolution data for quality reports
- **guardian-Guardian**: Coordinate on quality gate enforcement for resolved issues