Jira Orchestration Workflow
Execute 6-phase protocol for coordinating Jira-based development work with multi-agent orchestration.
When to Use
- Starting work on Jira issues (Bug, Story, Task, Epic)
- Automating development workflows
- Tracking progress and linking commits/PRs
- Coordinating multi-agent work
The 6-Phase Protocol
EXPLORE → PLAN → CODE → TEST → FIX → COMMIT
Each phase must complete validation gates before proceeding.
Phase 1: EXPLORE
- Fetch issue details, acceptance criteria, linked issues
- Analyze affected codebase areas and dependencies
- Agents: requirements-analyzer, dependency-mapper
- Outputs: Issue analysis, affected files, dependency map, risk assessment
- Jira: Transition to "In Progress", add analysis comment, log effort
Phase 2: PLAN
- Design solution, break into subtasks, create task DAG
- Plan file changes, define success criteria
- Agents (by type): Bug→triage-agent; Story→requirements-analyzer; Task→task-enricher; Epic→epic-decomposer
- Outputs: Implementation plan, test plan, rollback strategy
- Jira: Create sub-tasks, add plan comment, update estimate
Phase 3: CODE
- Execute DAG tasks in parallel
- Implement changes, add docs and error handling
- Agents (by tech): Frontend→requirements-analyzer; Backend→requirements-analyzer; DevOps→infrastructure-orchestrator
- Outputs: Code changes, configs, migration scripts
- Jira: Add progress comments, log time spent, flag blockers
Phase 4: TEST
- Run unit/integration/E2E tests, verify acceptance criteria
- Agents: test-strategist, qa-ticket-reviewer, test-strategist
- Outputs: Test results, coverage, performance metrics
- Jira: Add test results, attach reports
- Failure: Return to FIX, do NOT complete issue
Phase 5: FIX
- Debug failures, address code review feedback
- Re-run tests until passing (max 3 iterations before escalation)
- Agents: hypothesis-debugger, review-orchestrator, code-quality-enforcer
- Loop: Return to TEST after fixes
Phase 6: COMMIT
- Create PR with issue key, link to Jira, request review
- Format:
[ISSUE-KEY] description\n\nResolves: ISSUE-KEY
- Agents: commit-orchestrator, pr-creator, documentation-hub
- Jira: Add PR link, transition to "In Review"
Agent Selection
| Issue Type |
Primary |
Secondary |
| Bug |
triage-agent, hypothesis-debugger |
root-cause-analyzer, test-strategist |
| Story |
requirements-analyzer, code-architect |
requirements-analyzer |
| Task |
task-enricher |
technology-specific |
| Epic |
epic-decomposer |
split into stories first |
| Spike |
requirements-analyzer, requirements-analyzer |
domain experts |
By Technology: Frontend→react-specialist; Backend→api-specialist; DevOps→infrastructure-orchestrator; Mobile→mobile-developer
By Priority: Blocker→triage-agent + escalate; Critical→senior agents + extended thinking; High→standard selection; Medium/Low→optimize for efficiency
Blocker Handling
Mark blocker when: Missing requirements, dependencies, technical limits, security concerns, breaking changes.
Immediate: Add "Blocked" label, create detailed comment, link blocking issue, notify stakeholders.
Escalate when: Persists >4 hours, beyond agent authority, security vulnerability, breaking changes, customer impact, legal/compliance questions.
Process: Pause, document context, create Jira comment, tag humans, transition to "Waiting for Support".
Human Involvement
Always required: Security changes, breaking API/DB changes, infrastructure, customer-facing features, compliance.
Optional (post-review): Bug fixes, docs, tests, refactoring.
Progress Tracking
Update Jira at: Phase transitions, blockers, test failures, PR creation, hourly.
Status format:
## Progress - Phase: [NAME]
- Completed: [items]
- In Progress: [items] (X%)
- Blocked: [items] ([reason])
- Next: [steps]
- Time Spent: Xh Ym
Metrics: Velocity (story points/sprint), Cycle Time (In Progress→Done), Lead Time (creation→completion), Work Log (time/phase).
Best Practices
- Never skip phases (critical validations at each)
- Checkpoint between phases for recovery
- Run independent tasks in parallel
- Use 3-5 agents minimum, 13 maximum
- Frequent Jira updates: comments, work logs, links, labels, components
- Quality gates: All tests passing, >80% coverage, no vulnerabilities, docs updated, human review
Workflows by Issue Type
Bug: EXPLORE (reproduce)→PLAN (fix design)→CODE→TEST (add regression)→FIX→COMMIT
Story: EXPLORE→PLAN (subtasks)→CODE (parallel)→TEST (E2E)→FIX→COMMIT
Epic: Decompose into Stories, execute each Story workflow, integrate results
PR/Commit Format
PR Title: [ISSUE-KEY] Brief description
Commit:
[ISSUE-KEY] description
Changes:
- item1
- item2
Resolves: ISSUE-KEY
Branch: [type]/[issue-key]-[description] (e.g., feature/PROJ-123-auth)
Smart commits: [ISSUE-KEY] #comment text | #time 2h 30m | #transition In Review
Quality Gates
Example: Bug Fix
Issue: PROJ-123 "Login timeout after 5 minutes"
| Phase |
Activity |
Agents |
| EXPLORE |
Analyze auth code, identify JWT expiry |
requirements-analyzer, security-specialist |
| PLAN |
Design fix: extend expiry, fix cleanup |
triage-agent |
| CODE |
Update JWT config, implement refresh |
requirements-analyzer, security-specialist |
| TEST |
Unit/integration/manual tests |
test-strategist, qa-ticket-reviewer |
| FIX |
No fixes needed |
- |
| COMMIT |
Create PR, link to PROJ-123 |
commit-orchestrator |
Integration
Works with: jira (API), git-workflows (branches/PRs), orchestration-patterns (agent coordination), testing (test execution), debugging (root cause analysis).
1---2name: jira-orchestration-workflow3description: 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.4---5
6# Jira Orchestration Workflow
7
8Execute 6-phase protocol for coordinating Jira-based development work with multi-agent orchestration.
9
10## When to Use
11
12- Starting work on Jira issues (Bug, Story, Task, Epic)
13- Automating development workflows
14- Tracking progress and linking commits/PRs
15- Coordinating multi-agent work
16
17## The 6-Phase Protocol
18
19**EXPLORE → PLAN → CODE → TEST → FIX → COMMIT**
20
21Each phase must complete validation gates before proceeding.
22
23### Phase 1: EXPLORE
24- Fetch issue details, acceptance criteria, linked issues
25- Analyze affected codebase areas and dependencies
26- Agents: requirements-analyzer, dependency-mapper
27- Outputs: Issue analysis, affected files, dependency map, risk assessment
28- Jira: Transition to "In Progress", add analysis comment, log effort
29
30### Phase 2: PLAN
31- Design solution, break into subtasks, create task DAG
32- Plan file changes, define success criteria
33- Agents (by type): Bug→triage-agent; Story→requirements-analyzer; Task→task-enricher; Epic→epic-decomposer
34- Outputs: Implementation plan, test plan, rollback strategy
35- Jira: Create sub-tasks, add plan comment, update estimate
36
37### Phase 3: CODE
38- Execute DAG tasks in parallel
39- Implement changes, add docs and error handling
40- Agents (by tech): Frontend→requirements-analyzer; Backend→requirements-analyzer; DevOps→infrastructure-orchestrator
41- Outputs: Code changes, configs, migration scripts
42- Jira: Add progress comments, log time spent, flag blockers
43
44### Phase 4: TEST
45- Run unit/integration/E2E tests, verify acceptance criteria
46- Agents: test-strategist, qa-ticket-reviewer, test-strategist
47- Outputs: Test results, coverage, performance metrics
48- Jira: Add test results, attach reports
49- Failure: Return to FIX, do NOT complete issue
50
51### Phase 5: FIX
52- Debug failures, address code review feedback
53- Re-run tests until passing (max 3 iterations before escalation)
54- Agents: hypothesis-debugger, review-orchestrator, code-quality-enforcer
55- Loop: Return to TEST after fixes
56
57### Phase 6: COMMIT
58- Create PR with issue key, link to Jira, request review
59- Format: `[ISSUE-KEY] description\n\nResolves: ISSUE-KEY`
60- Agents: commit-orchestrator, pr-creator, documentation-hub
61- Jira: Add PR link, transition to "In Review"
62
63## Agent Selection
64
65| Issue Type | Primary | Secondary |
66|-----------|---------|-----------|
67| Bug | triage-agent, hypothesis-debugger | root-cause-analyzer, test-strategist |
68| Story | requirements-analyzer, code-architect | requirements-analyzer |
69| Task | task-enricher | technology-specific |
70| Epic | epic-decomposer | split into stories first |
71| Spike | requirements-analyzer, requirements-analyzer | domain experts |
72
73By Technology: Frontend→react-specialist; Backend→api-specialist; DevOps→infrastructure-orchestrator; Mobile→mobile-developer
74
75By Priority: Blocker→triage-agent + escalate; Critical→senior agents + extended thinking; High→standard selection; Medium/Low→optimize for efficiency
76
77## Blocker Handling
78
79**Mark blocker when:** Missing requirements, dependencies, technical limits, security concerns, breaking changes.
80
81**Immediate:** Add "Blocked" label, create detailed comment, link blocking issue, notify stakeholders.
82
83**Escalate when:** Persists >4 hours, beyond agent authority, security vulnerability, breaking changes, customer impact, legal/compliance questions.
84
85**Process:** Pause, document context, create Jira comment, tag humans, transition to "Waiting for Support".
86
87## Human Involvement
88
89**Always required:** Security changes, breaking API/DB changes, infrastructure, customer-facing features, compliance.
90
91**Optional (post-review):** Bug fixes, docs, tests, refactoring.
92
93## Progress Tracking
94
95**Update Jira at:** Phase transitions, blockers, test failures, PR creation, hourly.
96
97**Status format:**
98```
99## Progress - Phase: [NAME]
100- Completed: [items]
101- In Progress: [items] (X%)
102- Blocked: [items] ([reason])
103- Next: [steps]
104- Time Spent: Xh Ym
105```
106
107**Metrics:** Velocity (story points/sprint), Cycle Time (In Progress→Done), Lead Time (creation→completion), Work Log (time/phase).
108
109## Best Practices
110
111- Never skip phases (critical validations at each)
112- Checkpoint between phases for recovery
113- Run independent tasks in parallel
114- Use 3-5 agents minimum, 13 maximum
115- Frequent Jira updates: comments, work logs, links, labels, components
116- Quality gates: All tests passing, >80% coverage, no vulnerabilities, docs updated, human review
117
118## Workflows by Issue Type
119
120**Bug:** EXPLORE (reproduce)→PLAN (fix design)→CODE→TEST (add regression)→FIX→COMMIT
121**Story:** EXPLORE→PLAN (subtasks)→CODE (parallel)→TEST (E2E)→FIX→COMMIT
122**Epic:** Decompose into Stories, execute each Story workflow, integrate results
123
124## PR/Commit Format
125
126**PR Title:** `[ISSUE-KEY] Brief description`
127
128**Commit:**
129```
130[ISSUE-KEY] description
131
132Changes:
133- item1
134- item2
135
136Resolves: ISSUE-KEY
137```
138
139**Branch:** `[type]/[issue-key]-[description]` (e.g., feature/PROJ-123-auth)
140
141**Smart commits:** `[ISSUE-KEY] #comment text` | `#time 2h 30m` | `#transition In Review`
142
143## Quality Gates
144
145- [ ] All tests passing (unit, integration, E2E)
146- [ ] Coverage >80%
147- [ ] No security vulnerabilities
148- [ ] No breaking changes (or documented)
149- [ ] Documentation updated
150- [ ] PR created and linked
151- [ ] Human review requested
152- [ ] Acceptance criteria met
153
154## Example: Bug Fix
155
156**Issue:** PROJ-123 "Login timeout after 5 minutes"
157
158| Phase | Activity | Agents |
159|-------|----------|--------|
160| EXPLORE | Analyze auth code, identify JWT expiry | requirements-analyzer, security-specialist |
161| PLAN | Design fix: extend expiry, fix cleanup | triage-agent |
162| CODE | Update JWT config, implement refresh | requirements-analyzer, security-specialist |
163| TEST | Unit/integration/manual tests | test-strategist, qa-ticket-reviewer |
164| FIX | No fixes needed | - |
165| COMMIT | Create PR, link to PROJ-123 | commit-orchestrator |
166
167## Integration
168
169Works with: jira (API), git-workflows (branches/PRs), orchestration-patterns (agent coordination), testing (test execution), debugging (root cause analysis).
thelobbi