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.
Executes a 6-phase protocol (Explore→Plan→Code→Test→Fix→Commit) to orchestrate Jira development workflows. Triggered when users request to "work on issue," "complete jira ticket," or "orchestrate jira" for bugs, stories, or tasks.
/plugin marketplace add Lobbi-Docs/claude/plugin install jira-orchestrator@claude-orchestrationThis skill inherits all available tools. When active, it can use any tool Claude has access to.
Execute 6-phase protocol for coordinating Jira-based development work with multi-agent orchestration.
EXPLORE → PLAN → CODE → TEST → FIX → COMMIT
Each phase must complete validation gates before proceeding.
[ISSUE-KEY] description\n\nResolves: ISSUE-KEY| Issue Type | Primary | Secondary |
|---|---|---|
| Bug | critical-bug-analyzer, debugger | root-cause-investigator, test-engineer |
| Story | feature-architect, code-architect | frontend/backend-developer |
| Task | technical-planner | technology-specific |
| Epic | epic-decomposer | split into stories first |
| Spike | research-specialist, poc-developer | domain experts |
By Technology: Frontend→react-specialist; Backend→api-specialist; DevOps→infra-engineer; Mobile→mobile-developer
By Priority: Blocker→critical-bug-analyzer + escalate; Critical→senior agents + extended thinking; High→standard selection; Medium/Low→optimize for efficiency
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".
Always required: Security changes, breaking API/DB changes, infrastructure, customer-facing features, compliance.
Optional (post-review): Bug fixes, docs, tests, refactoring.
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).
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 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
Issue: PROJ-123 "Login timeout after 5 minutes"
| Phase | Activity | Agents |
|---|---|---|
| EXPLORE | Analyze auth code, identify JWT expiry | code-analyst, security-specialist |
| PLAN | Design fix: extend expiry, fix cleanup | critical-bug-analyzer |
| CODE | Update JWT config, implement refresh | backend-developer, security-specialist |
| TEST | Unit/integration/manual tests | test-engineer, qa-specialist |
| FIX | No fixes needed | - |
| COMMIT | Create PR, link to PROJ-123 | git-specialist |
Works with: jira (API), git-workflows (branches/PRs), orchestration-patterns (agent coordination), testing (test execution), debugging (root cause analysis).
Creating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems. Create original algorithmic art rather than copying existing artists' work to avoid copyright violations.
Applies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.
Create beautiful visual art in .png and .pdf documents using design philosophy. You should use this skill when the user asks to create a poster, piece of art, design, or other static piece. Create original visual designs, never copying existing artists' work to avoid copyright violations.