From mk
Analyzes Jira tickets with full context (description, comments, attachments, media, links) and produces structured findings suitable for posting as a Jira comment. Read-only.
How this skill is triggered — by the user, by Claude, or both
Slash command
/mk:jira-analystWhen to use
Use when user wants full ticket context (description + comments + attachments + links + media analysis) consolidated into a structured report. Read-only — user reviews before posting back.
jira-analystThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Forks to the `jira-analyst` agent. Read-only. The agent has Write tool privilege ONLY for persisting the report to `tasks/reports/jira-analyze-*.md` — it never writes to Jira itself.
Forks to the jira-analyst agent. Read-only. The agent has Write tool privilege ONLY for persisting the report to tasks/reports/jira-analyze-*.md — it never writes to Jira itself.
../../agents/jira-analyst.md../jira/references/{install-and-auth,cli-idioms,safety-framework}.mdmk:jira-evaluator (complexity signals), mk:jira-estimator (point estimate)mk:jira-issue (read ticket fields incl. attachments), mk:jira-collaborate (post analysis as comment — see mk:jira-collaborate/references/comment-templates.md)tasks/reports/jira-analyze-*.md consumable by mk:planning-engine and downstream skills.npx claudepluginhub ngocsangyem/meowkit --plugin mkAnalyzes tickets and PRDs for completeness, classifies product area, performs RCA on bugs, and generates structured handoff reports. Works with Jira, Linear, GitHub, Confluence, or manual paste.
Fetches a JIRA issue, distills it into a structured task for Claude Code, analyzes the codebase for missing criteria and risks, and optionally enriches the issue in JIRA.
Summarizes Jira ticket activity and child tickets to detect stale backlog items. Analyzes hierarchy, comments, and changelog to produce a staleness report.