mk-jira-agile
JIRA agile via jira-as: epics, sprints, backlog, ranking, story points, velocity. Board ID != project key. NOT issue CRUD (mk:jira-issue) or time tracking (mk:jira-time).
- License 许可
- MIT
- 最近更新
- 2026-11-15
- Stars
- ★ 16
- Forks
- 3
01 前言 Front Matter
- name
- mk-jira-agile
- description
- JIRA agile via jira-as: epics, sprints, backlog, ranking, story points, velocity. Board ID != project key. NOT issue CRUD (mk:jira-issue) or time tracking (mk:jira-time).
02 资源文件 2
- 参考文档references/agile-field-reference.md2.1 KB
- 参考文档references/sprint-operations.md1.9 KB
03 SKILL.md 正文
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)
- Read newest sprint-state file matching the active sprint
- Acquire
flockon the sprint-state file before any read-modify-write. YAML frontmatter append is non-atomic across shells; lock is the only mitigation - Per
agile-sprint-commitment.md2:stop and ask the user in chat"Reason for mid-sprint scope change?" — required free-text - Append
{ ts: <ISO ts>, action: add|remove, ticket: KEY, reason: <text> }toamendments:list - Release lock
- Proceed with the underlying
jira-as agile sprint add|removecall
If sprint-state contract is absent OR status: closed → skip the amendment ceremony silently.
sprint close
- Read
committed_tickets:from newest active sprint-state - Query each via
mk:jira-issue get KEY - For each non-terminal ticket (not Done/Cancelled/Won't-Do),
stop and ask the user in chat: "PROJ-X is in {status}. Carry over to next sprint? Drop? Mark as not delivered?" - Write closure summary:
status: closed,closed_at: <ts>,delivered: [...],carried_over: [...] - Proceed with the underlying
jira-as agile sprint closecall
Validator scope (sprint-state vs sprint-contract)
mk:sprint-contract/scripts/validate-contract.cjs validates per-story sprint-CONTRACT files only (those with contract_schema_version, ### [AC-N] entries). Sprint-STATE files at sprint-state-{date}-sprint-{N}.md use NO validator — YAML is parsed inline by this skill, mk:agent-detector, and mk:sprint-contract sprint-goal. Do not invoke validate-contract.cjs on a sprint-state path; it WILL fail (sprint-state lacks contract schema fields by design).
Wildcard-pattern collision safety verified
| Script | Mechanism | Verdict |
|---|---|---|
check-contract-signed.cjs |
Globs tasks/contracts/*-"$slug"-sprint-*.md (per-task slug between leading * and -sprint-) |
SAFE — sprint-state files have no slug between leading sprint-state- prefix and -sprint- |
validate-contract.cjs |
Takes single explicit $1 path; no glob |
SAFE |
See also
- Agent:
../../agents/jira-agile.md - Shared:
../jira/references/{install-and-auth,cli-idioms,safety-framework}.md - Domain refs:
references/sprint-operations.md— board/sprint/velocity wrapper patternsreferences/agile-field-reference.md— agile-specific field IDs (Sprint, Epic Link, Story Points)
- Peer leaves:
mk:jira-fields(../jira-fields/references/agile-field-ids.mdis the canonical instance-discovery source),mk:jira-time(capacity = velocity ÷ team time),mk:jira-relationships(epic-children outside epic-link via issue links)
Gotchas
- (none yet — grow from observed failures)
04 同仓库更多 Skills
mk-worktree
Manages git worktrees for parallel agent isolation: creates parallel/{name}-{timestamp} branches, merges with conflict detection. NOT for user feature branches (use git worktree directly).
mk-workflow-orchestrator
Auto-invoked 7-phase workflow for complex-feature intent; fasttrack mode for pre-approved specs. NOT for explicit single tasks (mk:cook), green-field builds (mk:autobuild), or simple fixes (mk:fix).
mk-web-to-markdown
Fetch a URL and return clean markdown, for arbitrary external pages (blog, RFC, GitHub issue, vendor doc) not covered by mk:docs-finder. Static-only by default; opt-in JS rendering available.
mk-vulnerability-scanner
Vulnerability analysis: OWASP Top 10, current threat landscape, supply chain security, attack surface mapping, risk prioritization. Use for security audits. NOT for STRIDE/CSO infra audits (mk:cso).
mk-vue
Vue 3 authoring/review: components, composables, reactivity, Pinia, Pinia Colada, file routing, forms. Composition API + script setup. Auto-activates on .vue files. Deep review: mk:vue-best-practices.
mk-vue-testing-best-practices
Vue 3 testing best-practices review: Vitest + Vue Test Utils for components, composables, Pinia, Router, async/Suspense, forms, a11y, plus Playwright E2E strategy. Advisory only.