mk-jira-lifecycle
Drive JIRA workflow lifecycle via jira-as: transition, assign, resolve, reopen, versions, components. NOT issue CRUD (mk:jira-issue) or bulk transitions (mk:jira-bulk).
- License 许可
- MIT
- 最近更新
- 2026-11-15
- Stars
- ★ 16
- Forks
- 3
01 前言 Front Matter
- name
- mk-jira-lifecycle
- description
- Drive JIRA workflow lifecycle via jira-as: transition, assign, resolve, reopen, versions, components. NOT issue CRUD (mk:jira-issue) or bulk transitions (mk:jira-bulk).
02 资源文件 10
- 参考文档references/patterns/incident-workflow.md3.8 KB
- 参考文档references/patterns/incident-workflow.md.tmp—
- 参考文档references/patterns/jsm-request-workflow.md3.5 KB
- 参考文档references/patterns/jsm-request-workflow.md.tmp—
- 参考文档references/patterns/software-dev-workflow.md3.8 KB
- 参考文档references/patterns/software-dev-workflow.md.tmp—
- 参考文档references/patterns/standard-workflow.md2.5 KB
- 参考文档references/patterns/standard-workflow.md.tmp—
- 参考文档references/workflow-discovery.md6.1 KB
- 参考文档references/workflow-transitions.md2.1 KB
03 SKILL.md 正文
mk:jira-lifecycle
Forks to the jira-lifecycle agent. lifecycle transition takes the issue key positional + a --to "Status Name" flag (or --id <transition_id>).
Workflow discovery is mandatory before suggesting transitions. The agent reads tasks/jira-workflows/ (instance-discovered cache) and runs bash $(git rev-parse --show-toplevel)/.cursor/skills/jira/scripts/fetch-workflow.sh <KEY> if absent. See references/workflow-discovery.md. The references/patterns/*.md files are illustrative concepts only — they are NOT your project's actual workflow.
Triggers
- "transition PROJ-123 to In Progress"
- "mark PROJ-123 as Done with resolution Fixed"
- "assign PROJ-123 to john.doe"
- "reopen PROJ-123"
- "release version v1.0.0 in PROJ"
Examples
- Status change: "move PROJ-123 to In Review with comment 'ready for QA'"
- Resolution-required: "close PROJ-456 with resolution Won't Fix"
- Assignment: "assign all my open PROJ tickets to john.doe" (the agent will refuse — that's bulk; redirect to
mk:jira-bulk)
See also
- Agent:
../../agents/jira-lifecycle.md - Shared:
../jira/references/{install-and-auth,cli-idioms,safety-framework}.md - Authoritative source for THIS project's workflow (discovered, not templated):
references/workflow-discovery.md— discovery + caching protocol (READ FIRST)tasks/jira-workflows/<workflow-slug>.md— discovered workflow definitionstasks/jira-workflows/_schemes/<PROJECT_KEY>.md— project → workflow mapping- Discovery script:
bash $(git rev-parse --show-toplevel)/.cursor/skills/jira/scripts/jira-as.sh ...— wrapped byfetch-workflow.sh
- Domain refs:
references/workflow-transitions.md— common transition idioms + resolution-required patterns
- Educational concept patterns (illustrative shapes, NOT authoritative for your instance — always prefer the discovered cache above):
references/patterns/standard-workflow.md— basic 3-state lifecycle (concept)references/patterns/software-dev-workflow.md— engineering-team flow (concept)references/patterns/jsm-request-workflow.md— JSM ITIL flow (concept)references/patterns/incident-workflow.md— incident handling (concept)
- Peer leaves:
mk:jira-bulk(bulk transition; reads same workflow cache),mk:jira-jsm(JSM-specific transitions),mk:jira-collaborate(transition--commentbody templates)
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.