JIRA Story Point Estimator by openshift-hyperfleet/hyperfleet-claude-plugins
npx skills add https://github.com/openshift-hyperfleet/hyperfleet-claude-plugins --skill 'JIRA Story Point Estimator'当用户出现以下情况时,激活此技能:
HyperFleet 使用修改后的斐波那契数列作为故事点:
| 点数 | 含义 | 典型范围 | 备注 |
|---|---|---|---|
| 0 | 仅用于跟踪 | 快速/简单的任务,具有利益相关者价值 | 很少使用。用于值得跟踪但与 1 点任务相比工作量可忽略不计的任务 |
| 1 | 微不足道 | 单行更改,极其简单的任务 | 可能的最小问题 - 其他一切都以此为基准。无风险,工作量极低,复杂度极低 |
| 3 | 简单直接 | 耗时但相当直接的工作 | 不一定复杂,但通常耗时。可能存在小风险 |
| 5 | 中等 |
广告位招租
在这里展示您的产品或服务
触达数万 AI 开发者,精准高效
| 需要调查、设计、协作 |
| 可能需要与他人讨论。可能相当耗时或复杂。涉及风险 |
| 8 | 大型 | 需要调查和设计的大任务 | 需要与他人协作。解决方案可能相当具有挑战性。预期存在风险。需要设计文档 |
| 13 | 过于庞大 | 应拆分为更小的故事 | 理想情况下不应使用此点数。如果遇到如此大的问题,必须进行拆分 |
jira issue view TICKET-KEY --plain 2>/dev/null
范围指标(检查描述和验收标准):
复杂度指标:
风险指标:
搜索可比较的已完成的工单:
jira issue list -q"project = HYPERFLEET AND status = Done AND type = Story" --plain 2>/dev/null | head -20
jira issue list -q"project = HYPERFLEET AND status = Done AND 'Story Points' is not EMPTY AND type = Story" --plain 2>/dev/null | head -20
摘要: [工单标题] 类型: [Story/Task/Bug]
| 因素 | 评估 | 影响 |
|---|---|---|
| 范围 | [小/中/大] | [描述] |
| 技术复杂度 | [低/中/高] | [原因] |
| 依赖关系 | [无/少/多] | [如有,请列出] |
| 测试工作量 | [最小/中等/大量] | [原因] |
| 风险/不确定性 | [低/中/高] | [原因] |
建议故事点数:X
置信度: [高/中/低]
推理依据:
| 工单 | 摘要 | 点数 | 相似度 |
|---|---|---|---|
| TICKET-A | [摘要] | 5 | 高 - 范围相似 |
| TICKET-B | [摘要] | 3 | 中 - 更简单的版本 |
一旦达成一致,使用以下命令设置故事点:
jira issue edit TICKET-KEY --custom story-points=X --no-input
或者对于故事点估算字段(Next-gen 项目):
jira issue edit TICKET-KEY --custom story-point-estimate=X --no-input
估算时,请考虑:
每周安装次数
–
代码仓库
GitHub 星标数
5
首次出现时间
–
安全审计
Activate this skill when the user:
HyperFleet uses a modified Fibonacci sequence for story points:
| Points | Meaning | Typical Scope | Notes |
|---|---|---|---|
| 0 | Tracking Only | Quick/easy task with stakeholder value | Rarely used. For tasks worth tracking but with negligible effort compared to a 1-pointer |
| 1 | Trivial | One-line change, extremely simple task | The smallest issue possible - everything scales from here. No risk, very low effort, very low complexity |
| 3 | Straightforward | Time consuming but fairly straightforward work | Doesn't have to be complex, but usually time consuming. Minor risks possible |
| 5 | Medium | Requires investigation, design, collaboration | Probably needs discussion with others. Can be quite time consuming or complex. Risks involved |
| 8 | Large | Big task requiring investigation and design | Requires collaboration with others. Solution can be quite challenging. Risks are expected. Design doc required |
| 13 | Too Large | Should be split into smaller stories | Ideally, this shouldn't be used. If you see an issue this big, it must be broken down |
jira issue view TICKET-KEY --plain 2>/dev/null
Scope Indicators (examine description and acceptance criteria):
Complexity Indicators:
Risk Indicators:
Search for comparable completed tickets:
jira issue list -q"project = HYPERFLEET AND status = Done AND type = Story" --plain 2>/dev/null | head -20
jira issue list -q"project = HYPERFLEET AND status = Done AND 'Story Points' is not EMPTY AND type = Story" --plain 2>/dev/null | head -20
Summary: [Ticket title] Type: [Story/Task/Bug]
| Factor | Assessment | Impact |
|---|---|---|
| Scope | [Small/Medium/Large] | [Description] |
| Technical Complexity | [Low/Medium/High] | [Why] |
| Dependencies | [None/Few/Many] | [List if any] |
| Testing Effort | [Minimal/Moderate/Extensive] | [Why] |
| Risk/Uncertainty | [Low/Medium/High] | [Why] |
Suggested Story Points: X
Confidence Level: [High/Medium/Low]
Reasoning:
| Ticket | Summary | Points | Similarity |
|---|---|---|---|
| TICKET-A | [Summary] | 5 | High - similar scope |
| TICKET-B | [Summary] | 3 | Medium - simpler version |
Once agreed, set story points using:
jira issue edit TICKET-KEY --custom story-points=X --no-input
Or for Story Point Estimate field (Next-gen projects):
jira issue edit TICKET-KEY --custom story-point-estimate=X --no-input
When estimating, consider:
Weekly Installs
–
Repository
GitHub Stars
5
First Seen
–
Security Audits
Azure Data Explorer (Kusto) 查询技能:KQL数据分析、日志遥测与时间序列处理
114,200 周安装