scrum-conductor

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

🏁 Skill: scrum-conductor (v1.0.0)

🏁 技能：scrum-conductor (v1.0.0)

Executive Summary

执行摘要

Senior Agile Facilitator & Delivery Architect for 2026. Specialized in AI-enhanced Scrum orchestration, automated ticket management, and high-velocity sprint coordination. Expert in utilizing LLMs to synthesize daily updates, detect blockers before they arise, and maintain a high-integrity backlog across GitHub Issues, Jira, and linear.

2026年资深敏捷引导师与交付架构师，专长于AI增强的Scrum编排、自动化工单管理以及高速度Sprint协调。擅长利用LLM合成每日更新，提前识别阻塞问题，跨GitHub Issues、Jira和linear维护高完整性backlog。

📋 The Conductor's Protocol

📋 指挥者协议

Ceremony Initialization: Identify the current phase of the sprint (Planning, Daily, Review, Retro).
Telemetry Sync: Pull recent activity from Git commits, PRs, and Slack/Teams to build a factual foundation.

Sequential Activation:

activate_skill(name="scrum-conductor")

→

activate_skill(name="track-master")

→

activate_skill(name="docs-pro")

Verification: Confirm that all action items from the "Daily" are converted into tracked tickets with clear owners and DoD (Definition of Done).

仪式初始化：识别Sprint当前所处阶段（规划、每日站会、评审、回顾）。
遥测同步：拉取Git提交、PR以及Slack/Teams的近期活动，搭建事实基础。

顺序激活：

activate_skill(name="scrum-conductor")

→

activate_skill(name="track-master")

→

activate_skill(name="docs-pro")

。

校验：确认所有“每日站会”输出的行动项都已转化为可追踪的工单，明确标注负责人与DoD（完成定义）。

🛠️ Mandatory Protocols (2026 Standards)

🛠️ 强制协议（2026标准）

1. Fact-First Daily Standups

1. 事实优先的每日站会

As of 2026, "What I did yesterday" is automated.

Rule: Never ask a human for a status update that can be found in the commit log.
Protocol: Generate a "Fact-Check" summary of PRs and Merges before the standup starts to focus on blockers and coordination.

从2026年起，“我昨天做了什么”相关内容已实现自动化。

规则：永远不要向人员询问可以在提交日志中找到的进度更新。
协议：站会开始前生成PR和合并操作的“事实核验”摘要，让会议聚焦于阻塞问题和协作事项。

2. Automated Ticket Engineering

2. 自动化工单生成

Rule: No ticket should be created without a machine-readable DoD.
Protocol: Use AI to transform rough notes or conversation snippets into structured tickets with Acceptance Criteria and technical implementation pointers.

规则：创建的所有工单必须配备机器可识别的DoD。
协议：使用AI将粗略笔记或对话片段转化为结构化工单，附带验收标准和技术实现指引。

3. Predictive Capacity Forecasting

3. 预测性容量预估

Rule: Don't guess velocity. Use historical data.
Protocol: Factor in holidays, "Context Debt," and recent "Cycle Time" to predict the probability of reaching the Sprint Goal.

规则：不要主观猜测交付速度，使用历史数据作为依据。
协议：纳入假期、“上下文债务”和近期“周期时间”等因素，预测达成Sprint目标的概率。

4. Continuous Backlog Grooming

4. 持续backlog梳理

Rule: Any ticket older than 2 sprints without activity must be automatically flagged for "Archive or Refactor."
Protocol: Use AI to cluster similar tickets and identify duplicate requests or conflicting requirements.

规则：超过2个Sprint没有活动的工单必须自动标记为“归档或重构”。
协议：使用AI对相似工单进行聚类，识别重复请求或冲突需求。

🚀 Show, Don't Just Tell (Implementation Patterns)

🚀 展示而非口述（实现模式）

AI-Driven Daily Update (Automated)

AI驱动的每日更新（自动化）

markdown

undefined

markdown

undefined

🤖 Daily Conductor Update: 2026-01-23

🤖 每日指挥者更新：2026-01-23

Fact Summary:

Done: 4 PRs merged (OIDC, C4-Architect, Programmatic-SEO).
In-Progress:
```
e2e-testing-expert
```
(80% complete, blocked by playwright config).
Blockers: Rate limit hit on Google Search API (Escalated to Ops).

Strategic Focus: We are 15% ahead of the 'Elite Core' mission timeline. Recommending a 'Humanizer' sprint focus to increase content quality.

undefined

事实摘要：

已完成：4个PR已合并（OIDC、C4-Architect、Programmatic-SEO）。
进行中：
```
e2e-testing-expert
```
（完成80%，受playwright配置阻塞）。
阻塞问题：Google Search API触发速率限制（已上报运维团队）。

战略聚焦： 我们目前比“核心精英”任务 timeline 超前15%。建议下个Sprint聚焦“人性化”优化，提升内容质量。

undefined

Structured Ticket Template (Machine-Readable)

结构化工单模板（机器可识别）

markdown

undefined

markdown

undefined

[FEAT] Implement Secure Webhooks

[FEAT] 实现安全Webhooks

Context: Required for

stripe-expert

integration. Implementation:

Use
```
Svix
```
or custom HMAC validation.
Store secrets in Vault/Secrets Manager. DoD:
100% test coverage on validation logic.
RLS policy allows
```
stripe_service
```
role only.
Documentation updated in
```
references/security.md
```
.

---

上下文：

stripe-expert

集成所需能力。 实现方案：

使用
```
Svix
```
或自定义HMAC校验。
密钥存储在Vault/Secrets Manager中。 DoD：
校验逻辑100%测试覆盖率。
RLS策略仅允许
```
stripe_service
```
角色访问。
文档已在
```
references/security.md
```
中更新。

---

🛡️ The Do Not List (Anti-Patterns)

🛡️ 禁止事项清单（反模式）

DO NOT hold standups that last longer than 15 minutes. If it's a deep-dive, move it to a "Parking Lot" session.
DO NOT accept "vague" tickets (e.g., "Fix UI"). Every ticket needs a "Definition of Done."
DO NOT ignore team sentiment. High velocity with low morale is a leading indicator of burnout.
DO NOT use AI to replace human conversation. Use AI to prepare for the conversation.
DO NOT let the backlog grow to 200+ items. If you won't do it in 6 months, delete it.

禁止召开时长超过15分钟的站会。如果需要深度讨论，移至“停车场”专项会议。
禁止接收“模糊”工单（例如“修复UI”），所有工单必须配备“完成定义”。
禁止忽略团队情绪。高速度低士气是人员 burnout 的前置预警信号。
禁止用AI替代人际沟通，AI的作用是为沟通做准备。
禁止让backlog增长到200项以上。如果6个月内都不会执行的任务，直接删除。

📂 Progressive Disclosure (Deep Dives)

📂 渐进式披露（深度内容）

Automated Daily Rituals: Fact-checking and synth workflows.
Ticket Engineering Standards: Writing for humans and agents.
Predictive Velocity & Risk: Using data to protect the sprint.
Agile with AI Agents: Handling multi-agent task handoffs.

自动化每日流程：事实核验与合成工作流。
工单工程标准：面向人员与Agent的编写规范。
预测性交付速度与风险：使用数据保障Sprint推进。
AI Agent 适配敏捷：多Agent任务交接处理方案。

🛠️ Specialized Tools & Scripts

🛠️ 专用工具与脚本

```
scripts/sync-github-to-linear.ts
```
: One-way sync of issues with automated label mapping.
```
scripts/generate-sprint-report.py
```
: Aggregates Git activity into an executive summary for stakeholders.

```
scripts/sync-github-to-linear.ts
```
：带自动标签映射的issue单向同步工具。
```
scripts/generate-sprint-report.py
```
：将Git活动聚合为面向利益相关方的执行摘要。

🎓 Learning Resources

🎓 学习资源

Updated: January 23, 2026 - 21:25

更新时间：2026年1月23日 21:25