القائمة
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 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 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 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 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".
This skill should be used when the user asks to "refresh Todoist", "sync Todoist", "list my projects", "show my labels", "update Todoist structure", "show my Todoist sections", or when a todoist-agent operation fails with a not-found error for a project, label, or section name. Fetches and caches Todoist structure for name-to-ID resolution.
| 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. |
Run via bash:
acli jira auth status
acli jira auth login --web --site <site>.atlassian.netbrew tap atlassian/homebrew-acli && brew install acliPresent 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 |
For intents that don't match a workflow (e.g., "just create a blank ticket", "search for bugs in PROJ", "delete PROJ-99"), handle directly using ACLI:
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