bug-coordinator
Orchestrates the complete bug-fixing workflow from Jira ticket to implementation. Use when starting to fix a bug, managing the bug-fixing pipeline, or checking workflow progress.
When & Why to Use This Skill
The Bug Coordinator is a sophisticated Claude skill designed to automate and orchestrate the end-to-end bug-resolution lifecycle. By integrating directly with Jira and managing a pipeline of specialized AI agents, it streamlines the transition from issue identification to verified implementation. It ensures technical accuracy through multi-stage research, root cause analysis (RCA), and mandatory human checkpoints, making it an essential tool for maintaining high-quality codebases with minimal manual overhead.
Use Cases
- Automated Bug-Fixing Pipeline: Initiate a complete resolution workflow by simply providing a Jira ticket ID, allowing the agent to fetch context, conduct research, and propose fixes autonomously.
- Multi-Agent Orchestration: Coordinate specialized sub-agents for deep-dive codebase research, RCA verification, and implementation planning to ensure rigorous analysis before code changes.
- Workflow Continuity: Resume interrupted debugging sessions by referencing existing artifact directories, ensuring no context is lost during complex, long-running fixes.
- Quality-Controlled Implementation: Utilize built-in human-in-the-loop checkpoints to review root cause reports and implementation plans before any code is executed, balancing automation with safety.
| name | bug-coordinator |
|---|---|
| description | Orchestrates the complete bug-fixing workflow from Jira ticket to implementation. Use when starting to fix a bug, managing the bug-fixing pipeline, or checking workflow progress. |
| license | MIT |
| compatibility | Requires VS Code Insiders with GitHub Copilot and Atlassian MCP |
| author | accruent |
| version | "1.0" |
Bug Coordinator
This skill provides workflow orchestration for the multi-agent bug-fixing pipeline.
When to Use
- User wants to start fixing a bug
- User provides a Jira ticket key
- User asks about bug-fixing workflow progress
- User wants to resume an in-progress bug fix
Workflow Overview
┌──────────┐ ┌──────────┐ ┌─────────┐ ┌─────────┐ ┌──────────────────┐
│ FETCH │ → │ RESEARCH │ → │ VERIFY │ → │ RCA │ → │ PLAN & IMPLEMENT │
│ (Jira) │ │(Codebase)│ │(Research)│ │(Analysis)│ │ (Fix Bug) │
└──────────┘ └──────────┘ └─────────┘ └─────────┘ └──────────────────┘
│ │ │ │ │
▼ ▼ ▼ ▼ ▼
bug-context.md research/ verified- rca-report.md impl-plan.md
*.md research.md + code changes
Specialized Agents
The coordinator delegates to these specialized agents:
| Agent | Phase | Purpose |
|---|---|---|
| Bug Researcher | 2 | Research codebase context |
| Research Verifier | 3 | Verify research accuracy |
| RCA Analyst | 4 | Root cause analysis |
| RCA Verifier | 5 | Verify RCA accuracy |
| Bug Planner | 6 | Create implementation plan |
| Bug Implementer | 7 | Execute the fix |
Artifact Directory Structure
context/bugs/{TICKET-ID}/
├── bug-context.md
├── research/
│ ├── hypothesis.md
│ ├── codebase-research.md
│ └── verified-research.md
├── rca-report.md
├── verified-rca.md
├── implementation-plan.md
└── fix-summary.md
Entry Points
Start New Bug Fix
@Bug Coordinator EMS-1234
Resume Existing Workflow
@Bug Coordinator context/bugs/EMS-1234/bug-context.md
Using Prompt Shortcut
/start-bug-workflow EMS-1234
Prerequisites
VS Code Setting Enabled:
"chat.customAgentInSubagent.enabled": trueAtlassian MCP Connected (for Jira integration)
All Bug-Fixing Agents Installed:
- Bug Researcher
- Research Verifier
- RCA Analyst
- RCA Verifier
- Bug Planner
- Bug Implementer
Human Checkpoints
The workflow requires human approval at critical phases:
- Before Planning (Phase 6): User reviews verified RCA
- Before Implementation (Phase 7): User approves implementation plan
These checkpoints ensure the analysis is correct before investing in fix development.
Error Handling
See the Bug Coordinator agent for detailed error handling patterns for:
- Jira ticket not found
- Missing prerequisite artifacts
- Agent handoff failures