This skill should be used when the user asks to "orchestrate jira", "work on issue", "complete jira ticket", "development workflow", "jira automation", "issue lifecycle", "work on story", "fix bug ticket", or needs guidance on coordinating development work through Jira with multi-agent orchestration patterns.
This skill inherits all available tools. When active, it can use any tool Claude has access to.
Coordinate development work through Jira tickets using the 6-phase orchestration protocol with intelligent agent selection and progress tracking.
Activate this skill when:
Execute all Jira-related development work through this mandatory protocol:
EXPLORE → PLAN → CODE → TEST → FIX → COMMIT
Objective: Understand the issue, gather context, identify dependencies.
Activities:
Agent Selection:
code-analyst - Analyze affected codebase areasrequirements-analyzer - Parse acceptance criteria and requirementsdependency-mapper - Identify dependencies and blockersOutputs:
Jira Updates:
Objective: Create implementation strategy and task breakdown.
Activities:
Agent Selection (based on issue type):
critical-bug-analyzer, root-cause-investigatorfeature-architect, code-architecttechnical-planner, implementation-strategistepic-decomposer, strategic-plannerOutputs:
Jira Updates:
Objective: Implement the planned solution with parallel execution.
Activities:
Agent Selection (based on technology):
backend-developer, api-specialist, database-expertfrontend-developer, ui-specialist, component-builderinfra-engineer, deployment-specialist, config-managerOutputs:
Jira Updates:
Objective: Validate implementation meets acceptance criteria.
Activities:
Agent Selection:
test-engineer - Write and execute testsqa-specialist - Validate acceptance criteriaintegration-tester - Test cross-system interactionsOutputs:
Jira Updates:
Failure Handling:
Objective: Address test failures and code review feedback.
Activities:
Agent Selection:
debugger - Fix test failurescode-reviewer - Self-review changesrefactoring-specialist - Improve code qualityOutputs:
Jira Updates:
Loop Condition:
Objective: Create PR, link to Jira, prepare for review.
Activities:
Agent Selection:
git-specialist - Handle git operationspr-creator - Create well-formatted PRsdocumentation-writer - Update docsOutputs:
Commit Message Format:
[ISSUE-KEY] Brief description of change
Detailed explanation of what was changed and why.
Changes:
- Change 1
- Change 2
Resolves: ISSUE-KEY
PR Description Format:
## Summary
Brief summary of changes
## Related Jira Issue
[ISSUE-KEY](link-to-jira-issue)
## Changes Made
- Change 1
- Change 2
## Testing
- [ ] Unit tests pass
- [ ] Integration tests pass
- [ ] Manual testing complete
## Screenshots (if applicable)
Add screenshots
## Checklist
- [ ] Code follows project standards
- [ ] Tests added/updated
- [ ] Documentation updated
- [ ] No breaking changes (or documented)
Jira Updates:
Choose agents based on issue characteristics:
| Issue Type | Primary Agents | Secondary Agents |
|---|---|---|
| Bug | critical-bug-analyzer, debugger | root-cause-investigator, test-engineer |
| Story | feature-architect, code-architect | frontend-developer, backend-developer |
| Task | technical-planner, implementation-strategist | Technology-specific agents |
| Epic | epic-decomposer, strategic-planner | Break into Stories first |
| Spike | research-specialist, poc-developer | Domain experts |
| Stack | Agent Categories |
|---|---|
| Frontend | react-specialist, ui-developer, component-builder |
| Backend | api-specialist, database-expert, service-developer |
| DevOps | infra-engineer, k8s-specialist, cicd-expert |
| Full-stack | Combination of above |
| Mobile | mobile-developer, native-specialist |
| Priority | Considerations |
|---|---|
| Blocker | Use critical-bug-analyzer, escalate quickly, involve humans early |
| Critical | Use senior agents, enable extended thinking, parallel execution |
| High | Standard agent selection, follow all phases |
| Medium | Standard workflow, optimize for efficiency |
| Low | Simpler agents, batch with similar work |
Mark as blocker when:
Immediate Actions:
Create Blocker Report:
## Blocker Identified
**Type:** [Missing Requirement | Dependency | Technical | Security]
**Description:**
Detailed description of blocker
**Impact:**
How this blocks progress
**Proposed Resolution:**
Suggested way to unblock
**Requires Action From:**
@stakeholder-name
**Estimated Unblock Time:**
X hours/days
Escalate to humans when:
Always involve humans for:
Optional human involvement:
## Review Request: [ISSUE-KEY]
**Issue Type:** Bug/Story/Task
**Priority:** High/Medium/Low
**Complexity:** High/Medium/Low
**Summary:**
Brief description of changes
**Changes Made:**
- List of changes
**Testing:**
- Test results
- Coverage: X%
**Review Focus Areas:**
- Area 1 to review carefully
- Area 2 to review carefully
**Timeline:**
Needs review by: [date]
**AI Confidence:**
High/Medium/Low confidence in solution
Update Jira automatically at:
Track metrics:
Add structured comments:
## Progress Update - Phase: CODE
**Completed:**
- ✅ Task 1
- ✅ Task 2
**In Progress:**
- 🔄 Task 3 (60% complete)
**Blocked:**
- ❌ Task 4 (waiting on API access)
**Next Steps:**
- Continue Task 3
- Start Task 5 after Task 3
**Time Spent:** 2h 30m
**Estimated Remaining:** 1h 30m
[ISSUE-KEY] Brief description
Examples:
[PROJ-123] Fix authentication bug in login flow
[PROJ-456] Add user profile management feature
[PROJ-789] Update documentation for API endpoints
In Commit Messages:
[PROJ-123] Implement user authentication
- Add JWT token generation
- Implement login endpoint
- Add password hashing
Resolves: PROJ-123
In PR Description:
Use Jira smart commits for automation:
[PROJ-123] #comment Added authentication tests
[PROJ-123] #time 2h 30m Work on authentication
[PROJ-123] #transition In Review
[type]/[issue-key]-[short-description]
Examples:
feature/PROJ-123-user-authentication
bugfix/PROJ-456-login-timeout
hotfix/PROJ-789-security-patch
Pass all gates before completion:
1. EXPLORE: Reproduce bug, identify root cause
2. PLAN: Design fix, avoid regressions
3. CODE: Implement fix
4. TEST: Verify fix, add regression test
5. FIX: Address edge cases
6. COMMIT: Create hotfix PR
Special Considerations:
1. EXPLORE: Understand requirements, review designs
2. PLAN: Break into subtasks, design architecture
3. CODE: Implement feature components
4. TEST: Validate all acceptance criteria
5. FIX: Refine based on feedback
6. COMMIT: Create feature PR with docs
Special Considerations:
1. EXPLORE: Decompose into Stories
2. Create Stories: Break epic into manageable stories
3. For each Story: Run standard Story workflow
4. Integration: Ensure stories work together
5. COMMIT: Create integration PR
Special Considerations:
# Issue: PROJ-123 "Login timeout after 5 minutes"
# Phase 1: EXPLORE
Agents: [code-analyst, security-specialist]
- Analyzed authentication code
- Identified JWT token expiry issue
- Found session cleanup bug
# Phase 2: PLAN
Agent: [critical-bug-analyzer]
- Extend token expiry to 60 minutes
- Fix session cleanup logic
- Add token refresh mechanism
# Phase 3: CODE
Agents: [backend-developer, security-specialist]
- Updated JWT config
- Fixed session cleanup
- Implemented token refresh
# Phase 4: TEST
Agents: [test-engineer, qa-specialist]
- Unit tests: ✅ Pass
- Integration tests: ✅ Pass
- Manual testing: ✅ Pass
# Phase 5: FIX
- No fixes needed
# Phase 6: COMMIT
Agent: [git-specialist]
- Created PR: "Fix login timeout issue"
- Linked to PROJ-123
- Requested review
# Issue: PROJ-456 "Add user profile editing"
# Phase 1: EXPLORE
Agents: [requirements-analyzer, ui-specialist]
- Reviewed designs
- Identified API changes needed
- Analyzed existing profile code
# Phase 2: PLAN
Agents: [feature-architect, code-architect]
- Design profile update API
- Plan frontend form components
- Define validation rules
# Phase 3: CODE
Agents: [backend-developer, frontend-developer, test-engineer]
- Created profile update endpoint (parallel)
- Built profile edit form (parallel)
- Added validation (parallel)
# Phase 4: TEST
Agents: [test-engineer, qa-specialist]
- Unit tests: ✅ Pass
- E2E tests: ✅ Pass
- Accessibility: ✅ Pass
# Phase 5: FIX
Agent: [refactoring-specialist]
- Improved form validation UX
- Added loading states
# Phase 6: COMMIT
Agents: [git-specialist, documentation-writer]
- Created feature PR
- Updated API documentation
- Added user guide section
For deeper implementation details, see:
references/phase-guides/ - Detailed guides for each phasereferences/agent-selection.md - Comprehensive agent selection criteriareferences/jira-api.md - Jira API integration patternsreferences/escalation-playbook.md - Detailed escalation proceduresThis skill works best when combined with: