メニュー
Use when the user mentions Jira, issues, tickets, sprints, work items, or any project management task involving Atlassian. Routes to workflow skills or delegates to jira-agent subagent.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Use when a project's workflow statuses need to be configured for the first time, or refreshed. Triggered automatically by jira-progress when a project is missing from config/workflows.json, or manually via "configure workflow", "set up statuses for X", "refresh workflow for X".
Use when needing to understand a Jira ticket before acting on it — pulling context for an agent, reviewing a ticket's full picture, loading ticket details for decision-making, or when asked to "show me" or "what's in" a ticket.
Use when the user assigns a ticket to the agent, says "work on this ticket", "pick up this item", or wants the agent to claim a ticket and execute against it. Procedural harness that wraps any work with Jira discipline.
Use when the user has a spec, architecture doc, implementation plan, or feature description and wants to break it into Jira tickets for distribution to people or agents. Also triggered by "create tickets from this plan" or "file tickets for this spec".
Use when work on a ticket has reached a stage boundary — started working, sent for review, completed, blocked, or reopened. Handles status transition, comment, and field updates in one pass.
Use acli jira CLI for Jira work item management, project operations, sprint tracking, and board management with JQL search capabilities. Load this skill for ad-hoc Jira operations not covered by workflow skills, or when you need detailed ACLI command reference.
| name | jira |
| description | Use when the user mentions Jira, issues, tickets, sprints, work items, or any project management task involving Atlassian. Routes to workflow skills or delegates to jira-agent subagent. |
Skip this check if the SessionStart hook already confirmed ACLI is installed and authenticated (look for "✅ Jira Plugin: ACLI installed and authenticated" in the session context).
If no session-start confirmation is present, verify manually:
acli jira auth status
Interpreting the output:
acli jira auth login --web --site <site>.atlassian.netbrew tap atlassian/homebrew-acli && brew install acliDo NOT guess the installation status. If the command runs at all, ACLI is installed. Do NOT automate auth — just check and inform.
When the user provides bare numbers (e.g., "3529" instead of "UX-3529"):
config/workflows.json and get the list of configured project keysdefault_project is set → use it as the prefixAlso infer from context: if the user says "set UX-3529 to done and 2692 to in progress", infer "2692" → "UX-2692" from the explicit key in the same message.
Present two options to the user:
Remember the user's choice for the rest of the session. The user can say "switch to direct/subagent" to change mid-session.
| User intent | Skill |
|---|---|
| "Show me ticket X", "pull context for X", "what's in X" | jira-context |
| "Start working on X", "mark X as done", "X is blocked", "send for review" | jira-progress |
| "Break this spec into tickets", "create tickets from this plan" | jira-decompose |
| "Work on X", "pick up X", "agent handle X" | jira-work |
| "Configure workflow for X", "set up statuses", "refresh workflow" | jira-workflow |
| Ad-hoc ACLI operations (create, search, bulk, sprint, board) | acli |
For intents that don't match a workflow (create, search, bulk update, sprint queries, board queries), load the acli skill for the comprehensive command reference, then execute directly.
Quick-reference:
acli jira workitem create --summary "..." --project "PROJ" --type "Task" --yesacli jira workitem search --jql "..." --fields "key,summary,status,assignee" --csvacli jira workitem edit --key "KEY-123" --summary "..." --yesacli jira workitem delete --key "KEY-123" --yesAlways use --yes to skip confirmations and --fields to control output size.
jira-agent via the Task tool with the user's request