Stats
Actions
Tags
'%20stop-opacity%3D'0.16'%2F%3E%3Cstop%20offset%3D'1'%20stop-color%3D'rgb(200%2C90%2C60)'%20stop-opacity%3D'0.03'%2F%3E%3C%2FlinearGradient%3E%3C%2Fdefs%3E%3Crect%20width%3D'320'%20height%3D'200'%20fill%3D'url(%23g)'%2F%3E%3Ccircle%20cx%3D'250'%20cy%3D'56'%20r%3D'92'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.06'%2F%3E%3Ccircle%20cx%3D'64'%20cy%3D'172'%20r%3D'58'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.05'%2F%3E%3C%2Fsvg%3E)
From mk
Transitions Jira issues through workflow states, assigns users, resolves, reopens, and manages versions/components. Not for issue CRUD or bulk transitions.
How this skill is triggered — by the user, by Claude, or both
Slash command
/mk:jira-lifecycleWhen to use
Use to change a Jira issue's status, assignee, or resolution, or to manage project versions/components. NOT for bulk operations.
jira-lifecycleThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Forks to the `jira-lifecycle` agent. `lifecycle transition` takes the issue key positional + a `--to "Status Name"` flag (or `--id <transition_id>`).
references/patterns/incident-workflow.mdreferences/patterns/incident-workflow.md.tmpreferences/patterns/jsm-request-workflow.mdreferences/patterns/jsm-request-workflow.md.tmpreferences/patterns/software-dev-workflow.mdreferences/patterns/software-dev-workflow.md.tmpreferences/patterns/standard-workflow.mdreferences/patterns/standard-workflow.md.tmpreferences/workflow-discovery.mdreferences/workflow-transitions.mdForks to the jira-lifecycle agent. lifecycle transition takes the issue key positional + a --to "Status Name" flag (or --id <transition_id>).
Workflow discovery is mandatory before suggesting transitions. The agent reads tasks/jira-workflows/ (instance-discovered cache) and runs bash $CLAUDE_PROJECT_DIR/.claude/skills/jira/scripts/fetch-workflow.sh <KEY> if absent. See references/workflow-discovery.md. The references/patterns/*.md files are illustrative concepts only — they are NOT your project's actual workflow.
mk:jira-bulk)../../agents/jira-lifecycle.md../jira/references/{install-and-auth,cli-idioms,safety-framework}.mdreferences/workflow-discovery.md — discovery + caching protocol (READ FIRST)tasks/jira-workflows/<workflow-slug>.md — discovered workflow definitionstasks/jira-workflows/_schemes/<PROJECT_KEY>.md — project → workflow mappingbash $CLAUDE_PROJECT_DIR/.claude/skills/jira/scripts/jira-as.sh ... — wrapped by fetch-workflow.shreferences/workflow-transitions.md — common transition idioms + resolution-required patternsreferences/patterns/standard-workflow.md — basic 3-state lifecycle (concept)references/patterns/software-dev-workflow.md — engineering-team flow (concept)references/patterns/jsm-request-workflow.md — JSM ITIL flow (concept)references/patterns/incident-workflow.md — incident handling (concept)mk:jira-bulk (bulk transition; reads same workflow cache), mk:jira-jsm (JSM-specific transitions), mk:jira-collaborate (transition --comment body templates)npx claudepluginhub ngocsangyem/meowkit --plugin mkManages Jira issue lifecycles via CLI: transitions workflows and statuses, assigns/unassigns owners, resolves/reopens issues, handles versions and components.
Transitions Jira issues to new workflow states using jirac CLI, either directly by target status or via interactive picker. Useful for terminal-based Jira workflow updates.
Views Jira issues, generates branch names from tickets, creates tickets, and transitions status via Atlassian MCP. Activates on ticket key mentions or /jira command.