Jira Sprint Workflow Plugin for Claude Code
A Claude Code plugin that turns a one-line Jira intake ticket into a fully-designed, self-contained set of 15 subtasks that any teammate or sub-agent can execute.
The core discipline: every Jira subtask is self-contained. A teammate picks up a subtask, reads the description, and executes it — no docs folder, no slack thread, no prerequisite context required.
What it does
Four skills covering setup + the full end-to-end flow:
jira-setup — guided first-time configuration
Walks you through Jira Cloud URL, email, API token (opens the Atlassian token page in your browser), project picker, auto-discovered account ID, components, and directories. Validates live against /rest/api/3/myself. Writes config to ~/.claude/settings.json. The other three skills hand off to this automatically if any required config is missing.
Activates on prompts like set up the jira plugin, reconfigure jira plugin, connect jira.
jira-story-design — Phase 1 (design)
Brainstorm → Embed spec in Jira → Implementation plan → Test plan → 15 self-contained subtasks → "is blocked by" chain → Selected for Development
Activates on prompts like let's design WFR-42, brainstorm this and create the tasks, break this into subtasks.
jira-story-execute — Phase 2 (execution)
Pick up Story → Autonomously walk 15-subtask chain → Pause at subtask 10 (sandbox manual test) → Resume → Pause at subtask 12 (merge approval) → Resume → Done
Activates on prompts like pick up WFR-42, execute WFR-42, continue WFR-42.
Sub-agents dispatched by Phase 2 transition their subtask to In Progress and post incremental Progress: comments as they work, so any crashed or paused run resumes cleanly from Jira state alone.
The 15-subtask chain
0. Branch+Worktree
│
├─→ 1. Implement ───┐
│ ↓
└─→ 1b. Test Cases → 2. Code Review → 3. Fix → 4. UI Test → 5. Fix → 6. Local Smoke → 7. Architect Review → 8. Fix → 9. Deploy to Sandbox → 10. Sandbox Manual Test [human ✋] → 11. Fix Sandbox → 12. Merge to Sandbox Branch [human ✋] → 13. Push to Prod (sandbox → main PR) → 14. Prod Sanity
Two human checkpoints:
- Step 10 — Sandbox Manual Test (validate the feature on a real-deployed sandbox env)
- Step 12 — Merge to Sandbox Branch (explicit
Approved — merge to sandbox branch to join the release train)
Everything else runs via sub-agents. Fix loops (2↔3, 4↔5, 7↔8, and 9→10→11) cap at 3 cycles each before escalating.
Release train (sandbox as the integration branch)
feature branch ──(subtask 12, with approval)──→ sandbox ──(subtask 13 PR)──→ main (prod)
The sandbox branch is the integration buffer — multiple features may merge into sandbox before any one of them ships to prod. Subtask 13 opens a sandbox → main PR with a release-train manifest listing every feature included.
Fields set automatically per subtask
- Priority — inherited from parent Task, set explicitly (Jira inheritance for Sub-tasks is unreliable)
- Component — product area from your team's configured components
- Assignee — Sub Agent subtasks are
unassigned (the signal for autonomous execution); subtasks 10 (Sandbox Manual Test) and 12 (Merge to Sandbox Branch) = the Story owner
- "is blocked by" links — wired per the chain diagram, direction verified on creation
Installation
Step 1 — Add the marketplace
From a Claude Code session:
/plugin marketplace add Harsh1210/jira-sprint-workflow
(Or for local development: /plugin marketplace add ./path/to/this/directory)
Step 2 — Install the plugin
/plugin install jira-sprint-workflow
Step 3 — Run the guided setup
After install, in any Claude Code session say:
set up the jira plugin
This triggers the jira-setup skill, which walks you through the whole thing in ~2 minutes:
- Asks for your Jira Cloud URL and email
- Opens
https://id.atlassian.com/manage-profile/security/api-tokens in your browser so you can generate an API token, then validates it with a live call
- Auto-discovers your
accountId via /rest/api/3/myself (no hunting for it in Jira)
- Lists the projects you have access to and lets you pick the target project
- Lists the project's existing Components, offers to add missing ones (creates them via API if you have permission)
- Confirms defaults for
plans_directory (docs/superpowers/plans) and specs_directory (docs/superpowers/specs)
- Validates the full config with a final API round-trip
- Writes everything to
~/.claude/settings.json under pluginConfigs so the three workflow skills pick it up
