mkjira-agile

Solid

JIRA agile via the jira-as wrapper: epics, sprints, backlog, ranking, story points, subtasks, velocity. Triggers: 'create sprint', 'add KEY to sprint', 'set story points on KEY', 'rank KEY before KEY', 'velocity for board', 'epic add'. Board ID ≠ project key. NOT for issue CRUD (mk:jira-issue); NOT for time tracking (mk:jira-time).

AI & Automation 15 stars 2 forks Updated today MIT

Install

View on GitHub

Quality Score: 86/100

Stars 20%

Recency 20%

100

Frontmatter 20%

Documentation 15%

100

Issue Health 10%

License 10%

100

Description 5%

100

Skill Content

# mk:jira-agile Forks to the `jira-agile` agent. Sprint operations require a numeric `--board-id`, not the project key. The agent resolves project name → board ID via `agile board list --name "..."` first. ## Triggers - "list sprints on board 'Team Alpha'" - "add PROJ-123, PROJ-124 to sprint 42" - "set 5 story points on PROJ-123" - "rank PROJ-123 before PROJ-456 in backlog" - "velocity for board 42" - "create epic 'Auth Rewrite' in PROJ" ## Examples - Sprint create: "create sprint 'Sprint 21' on board 'Team Alpha' from 2026-05-13 to 2026-05-27" - Epic populate: "add PROJ-123, PROJ-124, PROJ-125 to epic EPIC-1" - Subtask: "create subtask of PROJ-123 — 'write integration test'" ## Sprint commitment hooks (Agile-context-only — gated by `agile-sprint-commitment.md` 2/3 when loaded) When `tasks/contracts/sprint-state-{date}-sprint-{N}.md` exists with `status: active`, wrap these operations: ### `sprint add KEY` and `sprint remove KEY` (post-start) 1. Read newest sprint-state file matching the active sprint 2. **Acquire `flock` on the sprint-state file before any read-modify-write.** YAML frontmatter append is non-atomic across shells; lock is the only mitigation 3. Per `agile-sprint-commitment.md` 2: `AskUserQuestion` "Reason for mid-sprint scope change?" — required free-text 4. Append `{ ts: <ISO ts>, action: add|remove, ticket: KEY, reason: <text> }` to `amendments:` list 5. Release lock 6. Proceed with the underlying `jira-as agile sprint add|remove` call If sprint-st...

Details

Author: ngocsangyem
Repository: ngocsangyem/MeowKit
Created: 4 months ago
Last Updated: today
Language: TypeScript
License: MIT

Integrates with

Jira · Productivity

Bundled in these plugins

MeowKit

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Solid

mkjira-bulk

Bulk JIRA operations on 10+ issues via the jira-as wrapper: bulk transition / assign / set-priority / clone / delete. Dry-run is MANDATORY first. Triggers: 'bulk update N issues', 'mass transition', 'transition 50+ issues to Done', 'bulk-clone', 'bulk-delete'. NOT for single-issue ops (mk:jira-issue / mk:jira-lifecycle).

15 Updated today

ngocsangyem

Code & Development Solid

jira

Manage Jira issues, sprints, and epics with the jira CLI (ankitpokhrel/jira-cli). Trigger on: jira, jira-cli, ticket, issue key (e.g. PROJ-123), epic, sprint, transition/move ticket, comment on ticket, assign ticket, JQL, create bug/story, "what's on my board", "my open issues". Use when the user wants to find, read, create, update, transition, comment on, assign, or link Jira work items — or list sprints/epics — via CLI. Do not use for Todoist, GitHub Issues, Linear, or generic project planning with no Jira involvement.

1 Updated 2 days ago

tkolleh

AI & Automation Solid

mkjira-admin

JIRA project / user / group / scheme / automation administration via the jira-as wrapper (11 sub-domains, ~65 verbs). Triggers: 'create JIRA project', 'list users', 'delete user USERNAME', 'list permission schemes', 'create group NAME'. Requires admin role. Destructive ops (project/user/group delete) require 2-step token confirmation. NOT for per-issue ops (mk:jira-issue / mk:jira-lifecycle); NOT for JSM admin (mk:jira-jsm).

15 Updated today

ngocsangyem