From jira
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".
npx claudepluginhub jackhutson/workflow-toolkit-plugins --plugin jiraThis skill uses the workspace's default tool permissions.
Discovers a project's Jira statuses and maps them to stage names used by jira-progress. Results are cached in `config/workflows.json` so this only runs once per project.
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.
Discovers a project's Jira statuses and maps them to stage names used by jira-progress. Results are cached in config/workflows.json so this only runs once per project.
Present to the user:
Project "PROJECT_KEY" doesn't have workflow statuses configured yet.
I can set this up two ways:
A) Auto-discover — I'll search for statuses in PROJECT_KEY and propose a mapping
B) Rovo prompt — I'll give you a prompt to paste into Rovo for the full workflow definition
Which do you prefer?
acli jira workitem search --jql "project = PROJECT_KEY ORDER BY status" --fields "key,status" --csv
Collect unique status values from the output.
Propose a best-guess mapping using these rules (case-insensitive):
startreviewdoneblockreopenPresent the mapping to the user:
Found these statuses in PROJECT_KEY: Backlog, TODO, IN PROGRESS, VERIFY, DONE, Blocked
Proposed mapping:
start → IN PROGRESS
review → VERIFY
done → DONE
block → Blocked
reopen → TODO
(unmapped: Backlog)
Look right? You can adjust any of these.
config/workflows.json, add the project entry with statuses only (no transitions — auto-discover can't get those), and write the file back.Example entry added:
{
"PROJECT_KEY": {
"statuses": {
"start": "IN PROGRESS",
"review": "VERIFY",
"done": "DONE",
"block": "Blocked",
"reopen": "TODO"
}
}
}
Generate and display this prompt for the user to paste into their Jira Rovo AI chat. Replace PROJECT_KEY and PROJECT_NAME with the actual values (get project name from acli jira project view --key "PROJECT_KEY" --json):
Paste this into Rovo:
---
For project PROJECT_KEY (PROJECT_NAME), give me:
1. The name of the workflow(s) used by this project
2. All statuses in each workflow
3. The valid transitions between statuses — for each status, list which
statuses it can transition to
4. For each status, map it to the closest match from this list:
start, review, done, block, reopen
5. Are any fields required when transitioning to terminal statuses
(e.g., resolution field when moving to Done)?
Format the answer as JSON like this:
{
"workflow_name": "...",
"statuses": {
"start": "STATUS_NAME",
"review": "STATUS_NAME",
"done": "STATUS_NAME",
"block": "STATUS_NAME",
"reopen": "STATUS_NAME"
},
"transitions": {
"STATUS_A": ["STATUS_B", "STATUS_C"],
"STATUS_B": ["STATUS_C", "STATUS_D"]
},
"required_fields": {
"DONE": ["resolution"]
}
}
---
When the user pastes Rovo's response back:
config/workflows.jsonstatuses, transitions, and required_fields (if any)After either path completes:
Workflow configured for PROJECT_KEY. Statuses saved to config/workflows.json.
If this was triggered by jira-progress, tell the agent to resume the original transition.
{"projects": {}} and proceed