Back to Details

scrum-master-agent

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Scrum Master Agent

Scrum Master Agent

A production-ready Scrum Master assistant designed for SaaS startups and application engineering teams. This skill provides intelligent sprint analytics, capacity planning, backlog prioritization, and actionable insights with token-efficient, context-aware output formatting.
一款面向SaaS初创企业和应用工程团队的可投入生产的Scrum Master助手。该Skill提供智能迭代分析、容量规划、待办事项优先级排序，以及具备令牌高效性、上下文感知的输出格式的可行见解。

Capabilities

功能特性

Sprint Management

迭代管理

  • Sprint Planning: Capacity-based story allocation with velocity tracking
  • Backlog Grooming: Priority scoring with effort/value/risk analysis
  • Sprint Health Monitoring: Real-time burndown tracking with predictive alerts
  • Velocity Analysis: Historical trend analysis with forecasting
  • 迭代规划：基于容量的用户故事分配，附带速度跟踪
  • 待办事项梳理：结合工作量/价值/风险分析的优先级评分
  • 迭代健康监控：实时燃尽图跟踪与预测警报
  • 速度分析：历史趋势分析与未来预测

Team Operations

团队运营

  • Daily Standups: Ultra-lightweight progress summaries (50-100 tokens)
  • Capacity Planning: Team availability calculation with holiday/PTO handling
  • Sprint Retrospectives: Action items extraction with sentiment analysis
  • Risk Detection: Automated alerts for scope creep, velocity drops, blocked tasks
  • 每日站会：超轻量化进度摘要（50-100令牌）
  • 容量规划：包含假期/带薪休假处理的团队可用时长计算
  • 迭代回顾：结合情感分析的行动项提取
  • 风险检测：针对范围蔓延、速度下降、阻塞任务的自动警报

Multi-Tool Integration

多工具集成

  • Linear: Native JSON import with Linear-specific field mapping
  • Jira: REST API adapter with custom field support
  • GitHub Projects: GraphQL integration with issue/PR tracking
  • Azure DevOps: Work item queries with sprint hierarchy
  • Linear：原生JSON导入，支持Linear特定字段映射
  • Jira：REST API适配器，支持自定义字段
  • GitHub Projects：GraphQL集成，支持议题/PR跟踪
  • Azure DevOps：工作项查询，支持迭代层级结构

Notification Integration

通知集成

  • Slack Notifications: Token-efficient webhook integration with rich block formatting
  • MS Teams Notifications: Adaptive Card integration for Microsoft Teams channels
  • Optional/Disabled by Default: No setup required to use skill, notifications opt-in
  • User Choice: Select Slack or Teams via configuration or environment variables
  • Concise Summaries: 50-100 token notifications with top 3 risks only
  • Slack通知：令牌高效的Webhook集成，支持富文本块格式
  • MS Teams通知：适配Microsoft Teams频道的自适应卡片集成
  • 默认禁用/可选：无需配置即可使用Skill，通知为可选功能
  • 用户选择：通过配置文件或环境变量选择Slack或Teams
  • 简洁摘要：50-100令牌的通知内容，仅展示前3项风险

Intelligent Output Design

智能输出设计

  • Context Detection: Automatically adapts to Claude AI Desktop vs Claude Code
  • Token Efficiency: Summary-first approach with progressive disclosure
  • Conditional Alerts: Only shows warnings/risks when they exist
  • Format Optimization: Markdown tables for Claude AI, ASCII charts for CLI
  • 上下文检测：自动适配Claude AI Desktop与Claude Code环境
  • 令牌效率：先摘要后详情的渐进式披露方式
  • 条件警报：仅在存在问题时显示警告/风险
  • 格式优化：Claude AI使用Markdown表格，CLI使用ASCII图表

Input Requirements

输入要求

Supported Formats

支持的格式

  1. JSON (Recommended):
    json
    {
  "tool": "linear|jira|github|azure",
  "sprint_name": "Sprint 45",
  "start_date": "2025-11-05",
  "end_date": "2025-11-19",
  "team_capacity": 80,
  "stories": [...]
}
  2. CSV:
    csv
    story_id,title,points,status,assignee,priority,blocked
STORY-123,User login,5,In Progress,Alice,High,false
  3. YAML:
    yaml
    sprint:
  name: "Sprint 45"
  team:
    - name: Alice
      capacity: 40
    - name: Bob
      capacity: 40
  4. Tool-Specific Exports:
    • Linear: Export to JSON from project view
    • Jira: Use REST API or CSV export
    • GitHub Projects: GraphQL query or CSV export
    • Azure DevOps: Work Item Query Results
  1. JSON（推荐）：
    json
    {
  "tool": "linear|jira|github|azure",
  "sprint_name": "Sprint 45",
  "start_date": "2025-11-05",
  "end_date": "2025-11-19",
  "team_capacity": 80,
  "stories": [...]
}
  2. CSV:
    csv
    story_id,title,points,status,assignee,priority,blocked
STORY-123,User login,5,In Progress,Alice,High,false
  3. YAML:
    yaml
    sprint:
  name: "Sprint 45"
  team:
    - name: Alice
      capacity: 40
    - name: Bob
      capacity: 40
  4. 工具特定导出格式:
    • Linear：从项目视图导出为JSON
    • Jira：使用REST API或CSV导出
    • GitHub Projects：GraphQL查询或CSV导出
    • Azure DevOps：工作项查询结果

Required Fields

必填字段

  • Sprint metadata: name, start_date, end_date, team_capacity
  • Stories: id, title, points, status, assignee
  • Optional: priority, blocked, dependencies, labels, created_date
  • 迭代元数据：名称、start_date、end_date、team_capacity
  • 用户故事：id、标题、故事点数、状态、经办人
  • 可选字段：优先级、是否阻塞、依赖项、标签、创建日期

Data Quality

数据质量要求

  • Story points must be numeric (Fibonacci or T-shirt sizes)
  • Dates in ISO 8601 format (YYYY-MM-DD)
  • Status values normalized to: Todo, In Progress, In Review, Done
  • Team capacity in story points per sprint
  • 故事点数必须为数值（斐波那契数列或T恤尺码）
  • 日期采用ISO 8601格式（YYYY-MM-DD）
  • 状态值需标准化为：Todo、In Progress、In Review、Done
  • 团队容量以每个迭代的故事点数为单位

Output Formats

输出格式

1. Daily Standups (Ultra-Lightweight)

1. 每日站会（超轻量化）

Token Budget: 50-100 tokens
🚀 Sprint 45 - Day 7/10

✅ Completed: 3 stories (13 pts)
🔄 In Progress: 5 stories (21 pts)
⚠️ Blocked: 1 story (5 pts) - Needs DB access

Velocity: On track (65% complete, 70% time elapsed)
令牌预算：50-100令牌
🚀 Sprint 45 - Day 7/10

✅ 已完成：3个用户故事（13点）
🔄 进行中：5个用户故事（21点）
⚠️ 阻塞：1个用户故事（5点） - 需要数据库访问权限

速度：按计划推进（完成65%，时间已过70%）

2. Sprint Planning (Moderate Detail)

2. 迭代规划（中等细节）

Token Budget: 200-500 tokens
📊 Sprint 45 Planning Summary

Capacity: 80 pts | Committed: 75 pts | Buffer: 5 pts

High Priority (35 pts):
  - STORY-123: User authentication (8 pts)
  - STORY-124: Payment integration (13 pts)
  - STORY-125: Dashboard redesign (8 pts)

Recommendations:
  1. P0: Address DB access blocker
  2. P1: Reduce scope if velocity drops below 85%
  3. P2: Consider splitting STORY-124 (13 pts is risky)
令牌预算：200-500令牌
📊 Sprint 45规划摘要

容量：80点 | 承诺：75点 | 缓冲：5点

高优先级（35点）:
  - STORY-123：用户身份验证（8点）
  - STORY-124：支付集成（13点）
  - STORY-125：仪表盘重设计（8点）

建议:
  1. P0：解决数据库访问阻塞问题
  2. P1：若速度低于85%则缩减范围
  3. P2：考虑拆分STORY-124（13点风险较高）

3. Sprint Review (Full Report)

3. 迭代评审（完整报告）

Token Budget: 500-1000 tokens
Includes:
  • Velocity trends (ASCII chart for CLI, table for Claude AI)
  • Burndown analysis with predictive completion date
  • Team performance metrics (throughput, cycle time)
  • Risk alerts (conditional - only if issues exist)
  • Prioritized recommendations (P0/P1/P2)
令牌预算：500-1000令牌
包含:
  • 速度趋势图（CLI使用ASCII图表，Claude AI使用表格）
  • 燃尽图分析与预测完成日期
  • 团队绩效指标（吞吐量、周期时间）
  • 风险警报（仅在存在问题时显示）
  • 优先级建议（P0/P1/P2）

4. Retrospective Analysis

4. 回顾分析

Token Budget: 300-500 tokens
🔍 Sprint 45 Retrospective

What Went Well:
  - 95% velocity achievement
  - Zero production incidents
  - Early story completion (3 days before deadline)

What Needs Improvement:
  - 2 stories blocked for >2 days
  - Code review delays (avg 18 hours)

Action Items:
  [P0] Establish DB access protocol (Owner: Alice, Due: 11/12)
  [P1] Set 8-hour code review SLA (Owner: Bob, Due: 11/15)
  [P2] Add automated status updates (Owner: Team, Due: 11/20)
令牌预算：300-500令牌
🔍 Sprint 45回顾报告

做得好的地方:
  - 达成95%的速度目标
  - 零生产事故
  - 用户故事提前完成（比截止日期早3天）

需要改进的地方:
  - 2个用户故事阻塞超过2天
  - 代码审查延迟（平均18小时）

行动项:
  [P0] 建立数据库访问协议（负责人：Alice，截止日期：11/12）
  [P1] 设置8小时代码审查SLA（负责人：Bob，截止日期：11/15）
  [P2] 添加自动状态更新（负责人：团队，截止日期：11/20）

5. Optional JSON Export

5. 可选JSON导出

For tool integration and dashboards:
json
{
  "sprint": "Sprint 45",
  "metrics": {
    "velocity": 75,
    "completion_rate": 0.95,
    "cycle_time_avg": 3.2
  },
  "risks": [...],
  "recommendations": [...]
}
用于工具集成与仪表盘:
json
{
  "sprint": "Sprint 45",
  "metrics": {
    "velocity": 75,
    "completion_rate": 0.95,
    "cycle_time_avg": 3.2
  },
  "risks": [...],
  "recommendations": [...]
}

How to Use

使用方法

Quick Invocations

快速调用

Daily Standup:
@scrum-master-agent

Generate a quick standup summary for Sprint 45 using the attached Linear export.
Sprint Planning:
@scrum-master-agent

Help me plan Sprint 46. Team capacity is 80 points. Here's the backlog (CSV attached).
Prioritize based on effort, value, and risk.
Burndown Analysis:
@scrum-master-agent

Analyze Sprint 45 burndown. Are we on track? When will we likely finish?
Attached: Jira sprint export (JSON)
Retrospective:
@scrum-master-agent

Generate retrospective report for Sprint 45. Focus on blockers and cycle time.
Attached: GitHub Projects export (CSV)
Capacity Planning:
@scrum-master-agent

Calculate team capacity for next sprint. Alice is on PTO for 3 days, Bob has 2 days of meetings.
Team size: 4 engineers (40 pts each normally).
每日站会:
@scrum-master-agent

使用附带的Linear导出文件生成Sprint 45的快速站会摘要。
迭代规划:
@scrum-master-agent

帮我规划Sprint 46。团队容量为80点。这是待办事项（附带CSV文件）。
根据工作量、价值和风险进行优先级排序。
燃尽图分析:
@scrum-master-agent

分析Sprint 45的燃尽图。我们是否按计划推进？预计何时完成？
附件：Jira迭代导出文件（JSON）
回顾会议:
@scrum-master-agent

生成Sprint 45的回顾报告，重点关注阻塞项和周期时间。
附件：GitHub Projects导出文件（CSV）
容量规划:
@scrum-master-agent

计算下一个迭代的团队容量。Alice将休假3天，Bob有2天会议。
团队规模：4名工程师（正常每人40点）。

Advanced Usage

高级用法

Multi-Tool Comparison:
Compare velocity trends across last 3 sprints using Linear data for Sprint 43-44 and Jira data for Sprint 45.
Risk Analysis:
Identify high-risk stories in the backlog. Flag anything with >8 points, blockers, or missing dependencies.
Custom Metrics:
Calculate sprint health score based on: velocity (40%), burndown trend (30%), blocked items (20%), team morale (10%).
多工具对比:
使用Sprint 43-44的Linear数据和Sprint 45的Jira数据，对比过去3个迭代的速度趋势。
风险分析:
识别待办事项中的高风险用户故事。标记任何超过8点、存在阻塞或缺少依赖项的故事。
自定义指标:
根据以下维度计算迭代健康得分：速度（40%）、燃尽趋势（30%）、阻塞项（20%）、团队士气（10%）。

Scripts

脚本模块

Core Modules

核心模块

  • parse_input.py
    : Multi-format parser (JSON/CSV/YAML) with tool-specific adapters
  • tool_adapters.py
    : Integration adapters for Linear, Jira, GitHub, Azure DevOps
  • calculate_metrics.py
    : All 6 metric calculations (velocity, burndown, capacity, priority, health, retrospective)
  • detect_context.py
    : Environment detection (Claude AI Desktop vs Claude Code)
  • format_output.py
    : Context-aware report generation with token efficiency
  • notify_channels.py
    : Slack and MS Teams webhook integrations (optional)
  • prioritize_backlog.py
    : Priority scoring with effort/value/risk analysis
  • parse_input.py
    : 多格式解析器（JSON/CSV/YAML），支持工具特定适配器
  • tool_adapters.py
    : Linear、Jira、GitHub、Azure DevOps的集成适配器
  • calculate_metrics.py
    : 6类指标计算（速度、燃尽图、容量、优先级、健康度、回顾分析）
  • detect_context.py
    : 环境检测（Claude AI Desktop vs Claude Code）
  • format_output.py
    : 上下文感知的报告生成，兼顾令牌效率
  • notify_channels.py
    : Slack和MS Teams的Webhook集成（可选）
  • prioritize_backlog.py
    : 结合工作量/价值/风险分析的优先级评分

Calculation Details

计算细节

1. Velocity Analysis:
  • Historical average over last 3-5 sprints
  • Trend analysis (improving/declining/stable)
  • Forecasting for next sprint
2. Burndown Tracking:
  • Daily story point completion
  • Ideal burndown line calculation
  • Predictive completion date (linear regression)
3. Capacity Planning:
  • Team availability calculation (PTO, holidays, meetings)
  • Story point allocation
  • Buffer recommendation (10-20% of capacity)
4. Priority Scoring:
  • Effort: Story points (normalized 0-10)
  • Value: Business impact (High=10, Medium=5, Low=2)
  • Risk: Blockers, dependencies, complexity (0-10)
  • Formula: 
    priority_score = (value * 2 + (10 - effort) + (10 - risk)) / 4
5. Sprint Health Score:
  • Velocity: Actual vs committed (40% weight)
  • Burndown: Actual vs ideal (30% weight)
  • Blocked Items: Count and duration (20% weight)
  • Team Morale: Optional sentiment input (10% weight)
  • Scale: 0-100 (90+ = Excellent, 70-89 = Good, 50-69 = Fair, <50 = At Risk)
6. Retrospective Analysis:
  • Completed vs committed stories
  • Blocked item analysis (count, duration, causes)
  • Cycle time metrics (avg time from start to done)
  • Action item extraction from retro notes
1. 速度分析:
  • 过去3-5个迭代的历史平均值
  • 趋势分析（提升/下降/稳定）
  • 下一个迭代的速度预测
2. 燃尽图跟踪:
  • 每日故事点完成情况
  • 理想燃尽线计算
  • 预测完成日期（线性回归）
3. 容量规划:
  • 团队可用时长计算（休假、节假日、会议）
  • 故事点分配
  • 缓冲建议（容量的10-20%）
4. 优先级评分:
  • 工作量：故事点数（标准化为0-10）
  • 价值：业务影响（高=10，中=5，低=2）
  • 风险：阻塞项、依赖项、复杂度（0-10）
  • 公式：
    priority_score = (value * 2 + (10 - effort) + (10 - risk)) / 4
5. 迭代健康得分:
  • 速度：实际值 vs 承诺值（权重40%）
  • 燃尽图：实际值 vs 理想值（权重30%）
  • 阻塞项：数量与持续时间（权重20%）
  • 团队士气：可选情感输入（权重10%）
  • 评分范围：0-100（90+ = 优秀，70-89 = 良好，50-69 = 一般，<50 = 风险）
6. 回顾分析:
  • 已完成 vs 承诺的用户故事
  • 阻塞项分析（数量、持续时间、原因）
  • 周期时间指标（从开始到完成的平均时间）
  • 从回顾笔记中提取行动项

Best Practices

最佳实践

Data Quality

数据质量

  1. Consistent Story Pointing: Use Fibonacci (1,2,3,5,8,13) or T-shirt sizes (XS=1, S=2, M=3, L=5, XL=8)
  2. Accurate Status Updates: Update story status daily (automate if possible)
  3. Blocked Item Tracking: Always document why items are blocked and who can unblock
  4. Sprint Boundaries: Never change sprint scope after day 3 (exception: critical bugs)
  1. 一致的故事点估算：使用斐波那契数列（1,2,3,5,8,13）或T恤尺码（XS=1, S=2, M=3, L=5, XL=8）
  2. 准确的状态更新：每日更新故事状态（尽可能自动化）
  3. 阻塞项跟踪：始终记录阻塞原因及负责人
  4. 迭代边界：迭代开始3天后不要更改范围（关键Bug除外）

Workflow Integration

工作流集成

  1. Daily Standups: Generate lightweight summary every morning (automated)
  2. Sprint Planning: Use priority scoring to allocate top 80% of capacity
  3. Mid-Sprint Check: Run health score on day 5-7 to catch issues early
  4. Retrospectives: Generate within 24 hours of sprint end while feedback is fresh
  1. 每日站会：每天早上生成轻量化摘要（自动化）
  2. 迭代规划：使用优先级评分分配80%的容量
  3. 迭代中期检查：在第5-7天运行健康得分，提前发现问题
  4. 回顾会议：迭代结束后24小时内生成报告，确保反馈新鲜

Token Efficiency

令牌效率

  1. Progressive Disclosure: Start with summary, offer details on request
  2. Conditional Alerts: Only show risks if they exist (don't report "No issues")
  3. Lazy Calculation: Compute detailed metrics only when asked
  4. Caching: Reuse calculations across multiple report types
  1. 渐进式披露：先展示摘要，按需提供详情
  2. 条件警报：仅在存在风险时显示（无需报告“无问题”）
  3. 延迟计算：仅在需要时计算详细指标
  4. 缓存：在多种报告类型中复用计算结果

Team Adoption

团队采用

  1. Start Simple: Begin with daily standups, add complexity gradually
  2. Customize Thresholds: Adjust health score weights based on team values
  3. Automate Inputs: Set up CI/CD to export tool data automatically
  4. Iterate: Refine priority scoring based on team feedback
  1. 从简开始：先从每日站会入手，逐步增加功能
  2. 自定义阈值：根据团队价值观调整健康得分权重
  3. 自动化输入：设置CI/CD自动导出工具数据
  4. 持续迭代：根据团队反馈优化优先级评分

Limitations

局限性

Data Requirements

数据要求

  • Requires structured sprint data (not suitable for ad-hoc work)
  • Story points must be assigned (can't prioritize unpointed stories)
  • Historical data needed for velocity trends (minimum 3 sprints)
  • 需要结构化的迭代数据（不适用于临时工作）
  • 必须分配故事点数（无法为未估算的故事排序）
  • 速度趋势需要历史数据（至少3个迭代）

Accuracy Considerations

准确性考量

  • Priority scoring is heuristic-based, not ML-driven (no predictive analytics)
  • Burndown predictions assume linear velocity (doesn't account for holidays, blockers)
  • Health score is subjective and depends on accurate weight configuration
  • 优先级评分基于启发式规则，而非机器学习驱动（无预测分析）
  • 燃尽图预测假设速度线性（不考虑节假日、阻塞项）
  • 健康得分具有主观性，依赖准确的权重配置

Scope Boundaries

范围边界

  • Does NOT: Integrate directly with tools (requires exports)
  • Does NOT: Send notifications or update tool state (read-only)
  • Does NOT: Replace Scrum Master judgment (augments decision-making)
  • 不支持：直接与工具集成（需要导出文件）
  • 不支持：发送通知或更新工具状态（只读）
  • 不能替代：Scrum Master的判断（仅辅助决策）

Tool-Specific Notes

工具特定说明

  • Linear: Requires manual JSON export (no API key support in this version)
  • Jira: Custom fields may need mapping in 
    tool_adapters.py
  • GitHub Projects: Beta GraphQL API may change (adapter may need updates)
  • Azure DevOps: Work item hierarchy can be complex (flatten in export)
  • Linear：需要手动导出JSON（当前版本不支持API密钥）
  • Jira：自定义字段可能需要在
    tool_adapters.py
    中映射
  • GitHub Projects：Beta版GraphQL API可能变更（适配器可能需要更新）
  • Azure DevOps：工作项层级可能复杂（导出时需扁平化）

When NOT to Use This Skill

不适用场景

  • Kanban workflows: Skill is optimized for Scrum sprints (not continuous flow)
  • Non-software projects: Priority scoring assumes software development context
  • Single-person teams: Overhead not justified for solo developers
  • Ad-hoc work: Requires structured sprint planning and tracking
  • 看板工作流：Skill针对Scrum迭代优化（不适用于持续流动）
  • 非软件项目：优先级评分基于软件开发场景
  • 单人团队：对于独立开发者来说开销过大
  • 临时工作：需要结构化的迭代规划与跟踪

Installation

安装方法

Claude Code (Recommended)

Claude Code（推荐）

bash
cp -r scrum-master-agent ~/.claude/skills/
bash
cp -r scrum-master-agent ~/.claude/skills/

Claude AI Desktop

Claude AI Desktop

Drag the 
scrum-master-agent.zip
file into Claude Desktop.
将
scrum-master-agent.zip
文件拖入Claude Desktop。

Claude API

Claude API

Use the 
/v1/skills
endpoint to upload the skill package.
使用
/v1/skills
端点上传Skill包。

Notification Setup (Optional)

通知设置（可选）

Notifications are disabled by default and completely optional. The skill works perfectly without any notification setup.
Option 1: Configuration File (Recommended)
bash
undefined
通知默认禁用，完全可选。Skill无需任何通知配置即可正常使用。
选项1：配置文件（推荐）
bash
undefined

Copy example config

复制示例配置

cp config.example.yaml config.yaml
cp config.example.yaml config.yaml

Edit config.yaml with your webhook URLs

编辑config.yaml填入你的Webhook URL

Set enabled: true

设置enabled: true

Choose channel: slack or teams

选择channel: slack或teams


**Option 2: Environment Variables**
```bash
export NOTIFY_ENABLED=true
export NOTIFY_CHANNEL=slack  # or teams
export SLACK_WEBHOOK_URL=https://hooks.slack.com/services/YOUR/WEBHOOK/URL
export TEAMS_WEBHOOK_URL=https://outlook.office.com/webhook/YOUR/WEBHOOK/URL
Getting Webhook URLs:
Slack:
  1. Go to https://api.slack.com/messaging/webhooks
  2. Create app and activate Incoming Webhooks
  3. Add webhook to workspace and select channel
  4. Copy webhook URL
Microsoft Teams:
  1. Open Teams channel
  2. Click "..." → Connectors → Incoming Webhook
  3. Configure webhook with name
  4. Copy webhook URL
Using Notifications:
@scrum-master-agent

Generate daily standup summary and send notification to Slack.
Notifications are token-efficient (50-100 tokens max) with:
  • Sprint name and status
  • Velocity and health metrics
  • Top 3 risks only (conditional)
  • Rich formatting (Slack blocks, Teams Adaptive Cards)

**选项2：环境变量**
```bash
export NOTIFY_ENABLED=true
export NOTIFY_CHANNEL=slack  # 或teams
export SLACK_WEBHOOK_URL=https://hooks.slack.com/services/YOUR/WEBHOOK/URL
export TEAMS_WEBHOOK_URL=https://outlook.office.com/webhook/YOUR/WEBHOOK/URL
获取Webhook URL:
Slack:
  1. 访问https://api.slack.com/messaging/webhooks
  2. 创建应用并激活Incoming Webhooks
  3. 将Webhook添加到工作区并选择频道
  4. 复制Webhook URL
Microsoft Teams:
  1. 打开Teams频道
  2. 点击“...” → 连接器 → Incoming Webhook
  3. 配置Webhook名称
  4. 复制Webhook URL
使用通知:
@scrum-master-agent

生成每日站会摘要并发送到Slack。
通知内容令牌高效（最多50-100令牌），包含:
  • 迭代名称与状态
  • 速度与健康指标
  • 仅前3项风险（条件显示）
  • 富文本格式（Slack块、Teams自适应卡片）

Version

版本信息

Version: 1.1.0 (with Notification Support) Last Updated: 2025-11-05 Author: Claude Code Skills Factory License: MIT
版本: 1.1.0（新增通知支持） 最后更新: 2025-11-05 作者: Claude Code Skills Factory 许可证: MIT

Support

支持

For issues, feature requests, or contributions, see the skill's GitHub repository or contact the Skills Factory maintainers.
如需报告问题、提出功能请求或参与贡献，请访问Skill的GitHub仓库或联系Skills Factory维护人员。