From jira
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.
npx claudepluginhub jackhutson/workflow-toolkit-plugins --plugin jiraThis skill uses the workspace's default tool permissions.
Transitions a ticket's status and adds a meaningful comment describing what happened — all in one pass. The comment is the valuable part; a bare status change is cheap.
Generates design tokens/docs from CSS/Tailwind/styled-components codebases, audits visual consistency across 10 dimensions, detects AI slop in UI.
Records polished WebM UI demo videos of web apps using Playwright with cursor overlay, natural pacing, and three-phase scripting. Activates for demo, walkthrough, screen recording, or tutorial requests.
Delivers idiomatic Kotlin patterns for null safety, immutability, sealed classes, coroutines, Flows, extensions, DSL builders, and Gradle DSL. Use when writing, reviewing, refactoring, or designing Kotlin code.
Transitions a ticket's status and adds a meaningful comment describing what happened — all in one pass. The comment is the valuable part; a bare status change is cheap.
| Stage | User says | Comment guidance |
|---|---|---|
start | "start working on", "pick up" | What you're about to do |
review | "send for review", "ready for review" | What was done, what to review |
done | "mark as done", "complete", "finished" | Summary of what was accomplished |
block | "blocked on", "stuck" | What the blocker is and who can unblock |
reopen | "reopen", "needs more work" | Why it's being reopened |
PL-3718 → PL)config/workflows.json:
config/workflows.json (relative to the plugin root)projects.PROJECT_KEY existsjira-workflow skill for this project. After it completes, re-read the config and continue.projects.PROJECT_KEY.statuses.STAGEtransitions is configured for this project):
acli jira workitem view KEY-123 --fields "status" --jsonacli jira workitem transition --key "KEY-123" --status "RESOLVED_STATUS" --yes
acli jira workitem comment-create --key "KEY-123" --body "Started work on the API refactor — focusing on the auth endpoints first"
start):acli jira workitem edit --key "KEY-123" --assignee "user@email.com" --yes
KEY-123: PREVIOUS_STATUS → RESOLVED_STATUS | Comment addedIf ACLI returns exit code != 0:
acli jira auth login --web --site <site>.atlassian.netbrew tap atlassian/homebrew-acli && brew install aclijira-workflow with the Rovo path to capture the full transition graph.