ngocsangyem mk:jira — Routing Skill
This skill is a pure routing layer. Its sole purpose: identify the right mk:jira-* leaf for the user's Jira task, then point at it. No execution.
Routing Table
| User intent | Leaf skill |
|---|---|
| Get/create/update/delete a single issue | mk:jira-issue |
| Find issues by criteria; export; filters | mk:jira-search |
| Transition through workflow; assign; resolve | mk:jira-lifecycle |
| Comments, attachments, watchers, notify | mk:jira-collaborate |
| Issue links, blockers, dependencies | mk:jira-relationships |
| Worklogs, time tracking, time reports | mk:jira-time |
| Epics, sprints, backlog, story points | mk:jira-agile |
| Custom field discovery + configuration | mk:jira-fields |
| Bulk ops (10+ issues, dry-run mandatory) | mk:jira-bulk |
| Service Management (queues, SLAs, customers) | mk:jira-jsm |
| Project/user/group/scheme administration | mk:jira-admin |
| Git/PR/branch-name integration | mk:jira-dev |
| Cache + project-context discovery | mk:jira-ops |
| Evaluate ticket complexity + inconsistencies | mk:jira-evaluator |
| Estimate story points (heuristic) | mk:jira-estimator |
| Analyze ticket context + media; RCA | mk:jira-analyst |
Setup
See references/install-and-auth.md for one-time setup (.claude/scripts/bin/setup-workflow installs jira-as into .claude/skills/.venv; populate .meowkit/.env with the 3 MEOW_JIRA_* vars).
Shared Resources (used by leaves)
scripts/jira-as.sh— env-translating wrapper (MEOW_JIRA_*→JIRA_*, setsJIRA_OUTPUT=json)scripts/jql-sanitize.sh— JQL escaping for user-derived termsscripts/requirements.txt— pip dependency manifest auto-discovered by.claude/scripts/bin/setup-workflowreferences/install-and-auth.md— setup, exit codes, DC/mTLS caveatsreferences/cli-idioms.md— verified jira-as syntax +jqprojection rulesreferences/safety-framework.md— 4-tier safety modelreferences/evaluation-rubric.md— used bymk:jira-evaluatorreferences/estimation-guide.md— used bymk:jira-estimator../jira-fields/references/field-discovery.md— used bymk:jira-fields(moved fromjira/references/)
Handoff
mk:intake→ recommendsmk:jira-*leaf based on triagemk:cook(build pipeline) → may invokemk:jira-issueto create implementation ticketsmk:ship(ship pipeline) → may invokemk:jira-devfor branch-name + PR-descriptionmk:planning-engine→ consumes Jira tickets via this hub for sprint planning analysis (mk:jira-evaluator/mk:jira-estimatoroutputs enrich the planning report)mk:confluence→ sister hub for Confluence Cloud;mk:planning-engineaccepts both Jira tickets (--tickets) and Confluence specs (--spec <report-path>) as input
Gotchas
- mk:jira itself never executes; if you're in this skill thinking about jira-as commands, you're in the wrong place — forward to a leaf.
- Escape hatch: if jira-as is unusable (mTLS, multi-profile), users may invoke Atlassian MCP directly per
references/install-and-auth.md. The router does NOT auto-fallback.