做什么
将Jira项目管理工作流程、短跑规划、问题跟踪和报告自动化
技能库 智客分类:Agent 工作流 Jira Automation
将Jira项目管理工作流程、短跑规划、问题跟踪和报告自动化
官方网址:skills.sh
先看中文介绍;官方 description 原文单独保留,不改写 SKILL.md。
将Jira项目管理工作流程、短跑规划、问题跟踪和报告自动化
官方 description 未单独写出 Use when。按规范,代理会在用户任务与这段 description 的关键词匹配时激活本技能。
按 Agent Skills 渐进披露:启动时只加载 name 与 description(约 100 token);任务匹配后才读入整份 SKILL.md 正文;scripts/、references/、assets/ 仅在需要时再读。 本文件正文结构:Jira Automation、Core Workflows、1. Issue Management Pipeline、2. Automation Rules、Sprint Management、Sprint Planning Template。 其中含规范建议的小节:分步指令。
文件分析:这是一份仅含 SKILL.md 的指令型技能,代理激活后整份正文进入上下文。
Automate Jira project management workflows, sprint planning, issue tracking, and reporting
Jira AutomationCore Workflows1. Issue Management Pipeline2. Automation RulesSprint ManagementSprint Planning TemplateSprint Board ConfigurationIssue TemplatesBug ReportFeature RequestEpic StructureJQL Queries Library
来源分类:skills.sh agent-skill
nameJira Automationdescription具体调用语法与可用工具以目标 Agent 客户端为准。 查看调用机制说明 ↗
先选择目标 Agent 和安装范围,保留技能包的附属文件,安装后检查客户端能否发现该技能。
复制安装指令给支持 Agent Skills 的代理,确认其中的目标目录与客户端匹配。
把 Agent Skill「Jira Automation」安装到我的项目:SKILL.md 原文与官方 description 见 https://zicq.com/zh/skills/skl-b023bab9274aa372-Jira-%E8%87%AA%E5%8A%A8%E5%8C%96.html 请存为 .cursor/skills/jira-automation/SKILL.md 或 .claude/skills/jira-automation/SKILL.md,frontmatter 的 name 与 description 保持原样,不要改写。
需要 Node.js 与 npx。先查看仓库技能列表,确认实际名称。
npx skills add 'https://github.com/claude-office-skills/skills' --list
CLI 会交互选择目标 Agent,默认安装到项目;用户级安装使用 -g。先通过查看命令核对仓库内容,再用 npx skills list 检查已安装技能。
name: Jira Automation description: Automate Jira project management workflows, sprint planning, issue tracking, and reporting version: 1.0.0 author: Claude Office Skills category: project-management tags:
Comprehensive skill for automating Jira project management and agile workflows.
ISSUE LIFECYCLE:
┌─────────────────┐
│ Backlog │
└────────┬────────┘
▼
┌─────────────────┐
│ To Do │──────┐
└────────┬────────┘ │
▼ │
┌─────────────────┐ │ Blocked
│ In Progress │◄─────┘
└────────┬────────┘
▼
┌─────────────────┐
│ In Review │
└────────┬────────┘
▼
┌─────────────────┐
│ Done │
└─────────────────┘
automation_rules:
- name: auto_assign_on_transition
trigger:
type: issue_transitioned
to_status: "In Progress"
condition:
assignee: unassigned
action:
assign_to: trigger_user
- name: add_label_on_priority
trigger:
type: issue_created
priority: highest
action:
- add_label: "urgent"
- send_slack: "#dev-alerts"
- name: auto_close_subtasks
trigger:
type: issue_transitioned
to_status: "Done"
issue_type: Story
action:
transition_subtasks: "Done"
- name: sla_warning
trigger:
type: scheduled
cron: "0 9 * * 1-5"
condition:
jql: "status = 'In Progress' AND updated < -3d"
action:
- add_comment: "@assignee Please update this issue"
- send_notification: assignee
sprint_planning:
name: "Sprint {{sprint_number}}"
duration: 14 # days
capacity_planning:
team_size: 6
hours_per_day: 6
total_capacity: 504 # hours
story_points:
target: 42
buffer: 10% # for unplanned work
ceremonies:
- name: Sprint Planning
day: 1
duration: 2h
- name: Daily Standup
day: "daily"
duration: 15m
- name: Sprint Review
day: 14
duration: 1h
- name: Retrospective
day: 14
duration: 1h
board_config:
type: scrum
columns:
- name: Backlog
statuses: ["Backlog"]
- name: To Do
statuses: ["To Do", "Selected for Development"]
wip_limit: null
- name: In Progress
statuses: ["In Progress"]
wip_limit: 6
- name: In Review
statuses: ["Code Review", "QA"]
wip_limit: 4
- name: Done
statuses: ["Done"]
swimlanes:
type: assignee
show_epics: true
bug_template:
project: DEV
issue_type: Bug
fields:
summary: "[BUG] {{title}}"
description: |
## Description
{{description}}
## Steps to Reproduce
1. {{step1}}
2. {{step2}}
3. {{step3}}
## Expected Behavior
{{expected}}
## Actual Behavior
{{actual}}
## Environment
- Browser: {{browser}}
- OS: {{os}}
- Version: {{app_version}}
## Screenshots
{{attachments}}
priority: {{severity}}
labels: ["bug", "needs-triage"]
components: ["{{component}}"]
feature_template:
project: DEV
issue_type: Story
fields:
summary: "[FEATURE] {{title}}"
description: |
## User Story
As a {{user_type}}, I want to {{action}} so that {{benefit}}.
## Acceptance Criteria
- [ ] {{criteria1}}
- [ ] {{criteria2}}
- [ ] {{criteria3}}
## Technical Notes
{{tech_notes}}
## Design Mockups
{{mockups}}
labels: ["feature", "needs-refinement"]
story_points: null # To be estimated
epic_template:
project: DEV
issue_type: Epic
fields:
summary: "{{epic_name}}"
description: |
## Overview
{{overview}}
## Goals
- {{goal1}}
- {{goal2}}
## Success Metrics
| Metric | Current | Target |
|--------|---------|--------|
| {{metric1}} | {{current1}} | {{target1}} |
## Timeline
Start: {{start_date}}
Target Completion: {{end_date}}
## Dependencies
{{dependencies}}
child_issues:
- type: Story
count: "auto"
# My open issues
assignee = currentUser() AND resolution = Unresolved ORDER BY priority DESC
# Sprint progress
project = DEV AND Sprint = "Sprint 15" ORDER BY status
# Bugs by severity
project = DEV AND type = Bug AND resolution = Unresolved
ORDER BY priority DESC, created ASC
# Stale issues
project = DEV AND status = "In Progress" AND updated < -7d
# Ready for review
project = DEV AND status = "Code Review" AND "Code Reviewer" is EMPTY
# Release scope
fixVersion = "v2.5.0" AND resolution = Unresolved
# Team velocity
project = DEV AND type = Story AND Sprint in closedSprints()
AND resolved >= -90d
# Blockers
project = DEV AND (priority = Blocker OR labels = blocked)
AND resolution = Unresolved
SPRINT 15 DASHBOARD
═══════════════════════════════════════
Progress:
Day 8 of 14 │ ████████░░░░░░ 57%
Story Points:
Committed: 42
Completed: 24 │ ████████████░░░░░░░░ 57%
Remaining: 18
Burndown:
│ 42 ┤ ▪
│ │ ▪▪
│ │ ▪▪
│ │ ▪▪▪
│ 21 ┤ ▪ ← Ideal
│ │ ▪▪
│ │ ▪▪
│ │ ▪▪
│ 0 ┤ ▪
└────┴────────────────────
Day 1 Day 14
Issue Status:
To Do ███░░░░░░░ 6
In Progress █████░░░░░ 8
In Review ████░░░░░░ 5
Done █████████░ 12
TEAM VELOCITY (Last 6 Sprints)
═══════════════════════════════════════
│ 50 ┤
│ │ ▓▓
│ 40 ┤ ▓▓ ▓▓ ▓▓ ▓▓
│ │ ▓▓ ▓▓ ▓▓ ▓▓ ▓▓ ▓▓
│ 30 ┤ ▓▓ ▓▓ ▓▓ ▓▓ ▓▓ ▓▓ ▓▓ ▓▓
│ │ ▓▓ ▓▓ ▓▓ ▓▓ ▓▓ ▓▓ ▓▓ ▓▓
│ 20 ┤ ▓▓ ▓▓ ▓▓ ▓▓ ▓▓ ▓▓ ▓▓ ▓▓
│ │ ▓▓ ▓▓ ▓▓ ▓▓ ▓▓ ▓▓ ▓▓ ▓▓
│ 10 ┤ ▓▓ ▓▓ ▓▓ ▓▓ ▓▓ ▓▓ ▓▓ ▓▓
│ │ ▓▓ ▓▓ ▓▓ ▓▓ ▓▓ ▓▓ ▓▓ ▓▓
│ 0 ┴─────────────────────────────
S10 S11 S12 S13 S14 S15
Average: 38 points | Trend: +5%
github_integration:
branch_creation:
trigger: issue_transitioned_to_in_progress
pattern: "{{issue_type}}/{{issue_key}}-{{summary_slug}}"
commit_linking:
patterns:
- "{{issue_key}}"
- "#{{issue_key}}"
action: add_comment_with_link
pr_automation:
on_pr_open:
- transition_issue: "Code Review"
- add_pr_link_to_issue
on_pr_merge:
- transition_issue: "Done"
- add_comment: "Merged in {{pr_url}}"
slack_integration:
channels:
dev_updates: "#dev-updates"
alerts: "#dev-alerts"
notifications:
- event: blocker_created
channel: alerts
message: "🚨 Blocker: {{issue.key}} - {{issue.summary}}"
- event: sprint_started
channel: dev_updates
message: "🏃 Sprint {{sprint.name}} has started! Goal: {{sprint.goal}}"
- event: release_completed
channel: dev_updates
message: "🚀 Release {{version}} is live!"
workflow:
name: Development Workflow
statuses:
- Backlog
- Ready for Dev
- In Progress
- Code Review
- QA
- Ready for Release
- Done
transitions:
- from: Backlog
to: Ready for Dev
name: "Refine"
conditions:
- story_points_set
- from: Ready for Dev
to: In Progress
name: "Start Work"
post_functions:
- assign_to_current_user
- from: In Progress
to: Code Review
name: "Submit for Review"
validators:
- has_linked_pr
- from: Code Review
to: QA
name: "Pass Review"
conditions:
- all_reviewers_approved
- from: QA
to: Done
name: "Pass QA"
post_functions:
- resolve_issue
Agent 工作流
创造有效技能指南。 当用户想创造出新的技能(或更新现有的技能),以专业知识,工作流程,或工具集成来扩展克洛德的能力时,应该使用这种技能.
Agent 工作流
使用ClawdHub CLI搜索,安装,更新并发布从taladhub.com的代理技能. 需要获取苍蝇上的新技能时使用,将安装的技能同步到最新版本或特定版本,或者发布 npm-instainddhub CLI 的新/更新的技能文件夹.
Agent 工作流
管弦乐团多代理团队,任务设定周期,交接协议,审查工作流程. 使用时间: (1)建立2+特派员队伍,具有不同专业,(2)确定任务路线和生命周期(收录框_ spec_建设_审查_完成),(3)在特派员之间制定交接协议,(4)建立审查和质量关口,(5)管理特派员之间的交流和文物共享.
Agent 工作流
Spec-first,TDD,子代理驱动的软件开发工作流程. 当:(1)构建任何新功能或应用——触发脑暴_计划_子代理执行回路,(2)调试出一个bug或测试失败——触发系统性的根起过程,(3)用户说"让我们构建","帮助我计划","我想添加X",或"这个被打破",(4)完成一个功…