跳到正文
cccskills
免费在 GitHub 公开

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).

中文简介正在准备中。当前显示原文说明。

集成工具Jira

实测评分 未实测

查看安装方法

包含的文件(3)

  • SKILL.md3.8 KB
  • references/agile-field-reference.md2.1 KB
  • references/sprint-operations.md1.9 KB

SKILL.md(原文)

安装前可以查看交给 AI 代理的指令内容。

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: stop and ask the user in chat "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-state contract is absent OR status: closed → skip the amendment ceremony silently.

sprint close

  1. Read committed_tickets: from newest active sprint-state
  2. Query each via mk:jira-issue get KEY
  3. 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?"
  4. Write closure summary: status: closed, closed_at: <ts>, delivered: [...], carried_over: [...]
  5. Proceed with the underlying jira-as agile sprint close call

Validator scope (sprint-state vs sprint-contract)

mk:sprint-contract/scripts/validate-contract.sh 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.sh on a sprint-state path; it WILL fail (sprint-state lacks contract schema fields by design).

Glob-collision safety verified

ScriptMechanismVerdict
check-contract-signed.shGlobs 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.shTakes single explicit $1 path; no globSAFE

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 patterns
    • references/agile-field-reference.md — agile-specific field IDs (Sprint, Epic Link, Story Points)
  • Peer leaves: mk:jira-fields (../jira-fields/references/agile-field-ids.md is 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)

评价

还没有评价。欢迎分享你的使用感受。

评论

无需登录即可发表。欢迎分享使用感受、提问,或说明在哪些环境下无法运行。

还没有评论。来写第一条吧。

提交后会立即公开。请勿填写邮箱、电话等个人信息。URL 最多 2 个。

0 / 1000 字

此表单受 reCAPTCHA 保护,适用 Google 的隐私权政策和服务条款。

同一仓库的技能

Use this skill to generate well-branded interfaces and assets for MeowKit (AI Agent Toolkit for Claude Code), either for production or throwaway prototypes/mocks/etc. Contains essential design guidelines, colors, type, fonts, assets, and UI kit components for prototyping.

中文简介正在准备中。当前显示原文说明。

ngocsangyem/MeowKit152026年7月28日 更新

mk-advise

免费

Turn a raw idea into ONE honest recommendation: interview one question at a time until confirmed, then give a verdict with trade-offs and a checklist. Not for options or debate.

中文简介正在准备中。当前显示原文说明。

ngocsangyem/MeowKit152026年7月28日 更新

Browser automation CLI for agents: navigate, click/fill, screenshot, extract data, test apps, Electron/Slack, cloud browsers. NOT for the user's real Chrome profile/cookies (mk:chrome-profile).

中文简介正在准备中。当前显示原文说明。

ngocsangyem/MeowKit152026年7月28日 更新

Detects the right agent and complexity tier at Phase 0 orient; runs first in every workflow. NOT for runtime agent routing inside a single skill.

中文简介正在准备中。当前显示原文说明。

ngocsangyem/MeowKit152026年7月28日 更新

Angular v20+ patterns: components, signals, services, forms, routing, HTTP, testing, SSR. Auto-activates on .ts files in Angular projects (angular.json detected).

中文简介正在准备中。当前显示原文说明。

ngocsangyem/MeowKit152026年7月28日 更新

Design and review durable REST, GraphQL, RPC, or event API contracts: shape, compatibility, pagination, error semantics. Discovers existing consumers first. Not implementation, schema, or release.

中文简介正在准备中。当前显示原文说明。

ngocsangyem/MeowKit152026年7月28日 更新

查看 ngocsangyem 的全部技能

报告此技能的问题