Menu
Prepare Jira create, comment, and safe-update payloads with safe dry-run fallback. Use with /jira-ticket when work tracking is requested.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Use when a user wants to compare an arbitrary skill or path across models, quality, cost, latency, or routing.
Analyze actual local Copilot skill activations without reading conversation content.
Plan work too big for one agent session as a shared map of decision tickets on GitHub Issues or Jira, then resolve them one at a time until the route is clear. Use with /wayfinder when the user says "plan something too big for one session", "chart a map", "wayfind", "work the map", or "decision tickets". Always confirm tracker (GitHub vs Jira) and destination before writing. Adapted from mattpocock/skills wayfinder (MIT).
Create or resume a task handoff so a fresh agent can continue unfinished work. Persist via omp handoff CLI (never write handoff files yourself). Use when the user says /handoff, wants to pause mid-task, or resume prior work.
Single-owner execute-fix-verify loop for one clear task. Use with /ralph when one agent should keep going until evidence or blocker.
Adversarial QA pass that tests behavior, failures, and regressions. Use with /ultraqa after implementation when shallow checks are not enough.
| name | jira-ticket |
| description | Prepare Jira create, comment, and safe-update payloads with safe dry-run fallback. Use with /jira-ticket when work tracking is requested. |
Use /jira-ticket when work tracking is requested.
omp jira render <plan-file> — this never writes to Jira. To create/comment/update, run omp jira apply <plan-file-or-ticket-key>, which defaults to dry-run and only writes when Jira is configured with JIRA_MODE=live, the user has explicitly confirmed, and the CLI has explicit body/field support for the operation you need.omp jira render or omp jira apply … --dry-run (the default); live writes require explicit user confirmation plus CLI support for the exact payload being writtenOperation — create / comment / updateTarget — ticket key or "new"Payload — the Jira-formatted contentHuman action — what the user needs to do (e.g. "paste into Jira" if dry-run)