sprint-status

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Sprint Status

Sprint 状态

This is a fast situational awareness check, not a sprint review. It reads the current sprint plan and story files, scans for status markers, and produces a concise snapshot in under 30 lines. For detailed sprint management, use

/sprint-plan update

/milestone-review

This skill is read-only. It never proposes changes, never asks to write files, and makes at most one concrete recommendation.

这是一次快速的情况检查，并非 Sprint 评审。它会读取当前 Sprint 计划和故事文件，扫描状态标记，并生成不超过30行的简洁快照。如需详细的 Sprint 管理，请使用

/sprint-plan update

或

/milestone-review

。

该技能为只读模式。 它不会提出修改建议，不会请求写入文件，最多只会给出一项具体建议。

1. Find the Sprint

1. 查找 Sprint

Argument:

$ARGUMENTS[0]

(blank = use current sprint)

If an argument is given (e.g.,
```
/sprint-status 3
```
), search
```
production/sprints/
```
for a file matching
```
sprint-03.md
```
,
```
sprint-3.md
```
, or similar. Report which file was found.
If no argument is given, find the most recently modified file in
```
production/sprints/
```
and treat it as the current sprint.
If
```
production/sprints/
```
does not exist or is empty, report: "No sprint files found. Start a sprint with
```
/sprint-plan new
```
." Then stop.

Read the sprint file in full. Extract:

Sprint number and goal
Start date and end date
All story or task entries with their priority (Must Have / Should Have / Nice to Have), owner, and estimate

参数：

$ARGUMENTS[0]

（留空则使用当前 Sprint）

若提供参数（例如
```
/sprint-status 3
```
），则在
```
production/sprints/
```
目录下搜索匹配
```
sprint-03.md
```
、
```
sprint-3.md
```
或类似格式的文件，并报告找到的文件。
若未提供参数，则查找
```
production/sprints/
```
目录下最近修改的文件，并将其视为当前 Sprint。
若
```
production/sprints/
```
目录不存在或为空，则报告：“未找到 Sprint 文件。请使用
```
/sprint-plan new
```
启动一个 Sprint。” 然后停止操作。

完整读取 Sprint 文件，提取以下信息：

Sprint 编号和目标
开始日期和结束日期
所有故事或任务条目及其优先级（Must Have / Should Have / Nice to Have）、负责人和预估工作量

2. Calculate Days Remaining

2. 计算剩余天数

Using today's date and the sprint end date from the sprint file, calculate:

Total sprint days (end minus start)
Days elapsed
Days remaining
Percentage of time consumed

If the sprint file does not include explicit dates, note "Sprint dates not found — burndown assessment skipped."

根据当前日期和 Sprint 文件中的结束日期，计算：

Sprint 总天数（结束日期减开始日期）
已过去天数
剩余天数
时间消耗百分比

若 Sprint 文件未包含明确日期，则标注“Sprint 日期未找到 — 跳过燃尽评估。”

3. Scan Story Status

3. 扫描故事状态

First: check for
production/sprint-status.yaml
.

If it exists, read it directly — it is the authoritative source of truth. Extract status for each story from the

status

field. No markdown scanning needed. Use its

sprint

goal

start

end

fields instead of re-parsing the sprint plan.

If
sprint-status.yaml
does not exist (legacy sprint or first-time setup), fall back to markdown scanning:

If the entry references a story file path, check if the file exists. Read the file and scan for status markers: DONE, COMPLETE, IN PROGRESS, BLOCKED, NOT STARTED (case-insensitive).
If the entry has no file path (inline task in the sprint plan), scan the sprint plan itself for status markers next to that entry.
If no status marker is found, classify as NOT STARTED.
If a file is referenced but does not exist, classify as MISSING and note it.

When using the fallback, add a note at the bottom of the output: "⚠ No

sprint-status.yaml

found — status inferred from markdown. Run

/sprint-plan update

to generate one."

Optionally (fast check only — do not do a deep scan): grep

src/

for a directory or file name that matches the story's system slug to check for implementation evidence. This is a hint only, not a definitive status.

第一步：检查
production/sprint-status.yaml
文件。

若该文件存在，则直接读取它——这是权威的事实来源。从

status

字段提取每个故事的状态，无需扫描 Markdown 文件。使用该文件中的

sprint

、

goal

、

start

、

end

字段，无需重新解析 Sprint 计划。

若
sprint-status.yaml
文件不存在（旧版 Sprint 或首次设置），则回退到 Markdown 扫描：

若条目引用了故事文件路径，检查该文件是否存在。读取文件并扫描状态标记：DONE、COMPLETE、IN PROGRESS、BLOCKED、NOT STARTED（不区分大小写）。
若条目未包含文件路径（Sprint 计划中的内联任务），则在 Sprint 计划本身中扫描该条目旁的状态标记。
若未找到状态标记，则归类为 NOT STARTED。
若引用的文件不存在，则归类为 MISSING 并标注。

使用回退方式时，在输出底部添加标注： "⚠ 未找到

sprint-status.yaml

文件 — 状态从 Markdown 推断而来。请运行

/sprint-plan update

生成该文件。"

可选操作（仅快速检查——不进行深度扫描）：在

src/

目录下 grep 匹配故事系统别名的目录或文件名，以检查是否有实现痕迹。这仅作为提示，并非确定的状态。

Stale Story Detection

停滞故事检测

After collecting status for all stories, check each IN PROGRESS story for staleness:

For each story that has a referenced file, read the file and look for a
```
Last Updated:
```
field in the frontmatter or header (e.g.,
```
Last Updated: 2026-04-01
```
or
```
updated: 2026-04-01
```
). Accept any reasonable date field name:
```
Last Updated
```
,
```
Updated
```
,
```
last-updated
```
,
```
updated_at
```
.
Calculate days since that date using today's date.
If the date is more than 2 days ago, flag the story as STALE.
If no date field is found in the story file, note "no timestamp — cannot check staleness."
If the story has no referenced file (inline task), note "inline task — cannot check staleness."

STALE stories are included in the output table and collected into an "Attention Needed" section (see Phase 5 output format).

Stale story escalation: If any IN PROGRESS story is flagged STALE, the burndown verdict is upgraded to at least At Risk — even if the completion percentage is within the normal On Track window. Record this escalation reason: "At Risk — [N] story(ies) with no progress in [N] days."

收集所有故事的状态后，检查每个 IN PROGRESS 故事是否停滞：

对于每个有引用文件的故事，读取文件并在前置内容或页眉中查找
```
Last Updated:
```
字段（例如
```
Last Updated: 2026-04-01
```
或
```
updated: 2026-04-01
```
）。接受任何合理的日期字段名称：
```
Last Updated
```
、
```
Updated
```
、
```
last-updated
```
、
```
updated_at
```
。
根据当前日期计算该日期至今的天数。
若该日期距今超过2天，则将该故事标记为 STALE（停滞）。
若故事文件中未找到日期字段，则标注“无时间戳 — 无法检查是否停滞。”
若故事无引用文件（内联任务），则标注“内联任务 — 无法检查是否停滞。”

STALE 故事会包含在输出表格中，并汇总到“需关注”部分（见第5阶段输出格式）。

停滞故事升级规则：若任何 IN PROGRESS 故事被标记为 STALE，则燃尽评估结果至少升级为 At Risk（存在风险）——即使完成百分比处于正常的 On Track（按计划进行）区间。记录升级原因：“存在风险 — [N] 个故事已 [N] 天无进展。”

4. Burndown Assessment

4. 燃尽评估

Calculate:

Tasks complete (DONE or COMPLETE)
Tasks in progress (IN PROGRESS)
Tasks blocked (BLOCKED)
Tasks not started (NOT STARTED or MISSING)
Completion percentage: (complete / total) * 100

Assess burndown by comparing completion percentage to time consumed percentage:

On Track: completion % is within 10 points of time consumed % or ahead
At Risk: completion % is 10-25 points behind time consumed %
Behind: completion % is more than 25 points behind time consumed %

If dates are unavailable, skip the burndown assessment and report "On Track / At Risk / Behind: unknown — sprint dates not found."

计算：

已完成任务（DONE 或 COMPLETE）
进行中任务（IN PROGRESS）
阻塞任务（BLOCKED）
未开始任务（NOT STARTED 或 MISSING）
完成百分比：(已完成数 / 总数) * 100

通过比较完成百分比与时间消耗百分比来评估燃尽情况：

按计划进行：完成百分比与时间消耗百分比相差不超过10个百分点，或完成进度领先
存在风险：完成百分比落后于时间消耗百分比10-25个百分点
进度落后：完成百分比落后于时间消耗百分比超过25个百分点

若日期不可用，则跳过燃尽评估并报告“按计划进行/存在风险/进度落后：未知 — Sprint 日期未找到。”

5. Output

5. 输出

Keep the total output to 30 lines or fewer. Use this format:

markdown

undefined

总输出行数不超过30行，使用以下格式：

markdown

undefined

Sprint [N] Status — [Today's Date]

Sprint Goal: [from sprint plan] Days Remaining: [N] of [total] ([% time consumed])

Progress: [complete/total] tasks ([%])

Story / Task	Priority	Status	Owner	Blocker
[title]	Must Have	DONE	[owner]
[title]	Must Have	IN PROGRESS	[owner]
[title]	Must Have	BLOCKED	[owner]	[brief reason]
[title]	Should Have	NOT STARTED	[owner]

Story / Task	Priority	Status	Owner	Blocker
[title]	Must Have	DONE	[owner]
[title]	Must Have	IN PROGRESS	[owner]
[title]	Must Have	BLOCKED	[owner]	[brief reason]
[title]	Should Have	NOT STARTED	[owner]

Attention Needed

Story / Task	Status	Last Updated	Days Stale	Note
[title]	IN PROGRESS	[date or N/A]	[N days]	[STALE / no timestamp — cannot check staleness / inline task — cannot check staleness]

(Omit this section entirely if no IN PROGRESS stories are stale or have timestamp concerns.)

Story / Task	Status	Last Updated	Days Stale	Note
[title]	IN PROGRESS	[date or N/A]	[N days]	[STALE / no timestamp — cannot check staleness / inline task — cannot check staleness]

(Omit this section entirely if no IN PROGRESS stories are stale or have timestamp concerns.)

Burndown: [On Track / At Risk / Behind]

[1-2 sentences. If behind: which Must Haves are at risk. If on track: confirm and note any Should Haves the team could pull.]

Must-Haves at Risk

[List any Must Have stories that are BLOCKED or NOT STARTED with less than 40% of sprint time remaining. If none, write "None."]

Emerging Risks

[Any risks visible from the story scan: missing files, cascading blockers, stories with no owner. If none, write "None identified."]

Recommendation

[One concrete action, or "Sprint is on track — no action needed."]

---

[One concrete action, or "Sprint is on track — no action needed."]

---

6. Fast Escalation Rules

6. 快速升级规则

Apply these rules before outputting, and place the flag at the TOP of the output if triggered (above the status table):

Critical flag — if Must Have stories are BLOCKED or NOT STARTED and less than 40% of the sprint time remains:

SPRINT AT RISK: [N] Must Have stories are not complete with [X]% of sprint
time remaining. Recommend replanning with `/sprint-plan update`.

Completion flag — if all Must Have stories are DONE:

All Must Haves complete. Team can pull from Should Have backlog.

Missing stories flag — if any referenced story files do not exist:

NOTE: [N] story files referenced in the sprint plan are missing.
Run `/story-readiness sprint` to validate story file coverage.

在输出前应用以下规则，若触发则将标记放在输出顶部（状态表格上方）：

紧急标记 — 若 Must Have 故事处于 BLOCKED 或 NOT STARTED 状态，且 Sprint 剩余时间不足40%：

SPRINT AT RISK: [N] Must Have stories are not complete with [X]% of sprint
time remaining. Recommend replanning with `/sprint-plan update`.

完成标记 — 若所有 Must Have 故事均已完成：

All Must Haves complete. Team can pull from Should Have backlog.

缺失故事标记 — 若任何引用的故事文件不存在：

NOTE: [N] story files referenced in the sprint plan are missing.
Run `/story-readiness sprint` to validate story file coverage.

Collaborative Protocol

协作协议

This skill is read-only. It reports observed facts from files on disk.

It does not update the sprint plan
It does not change story status
It does not propose scope cuts (that is
```
/sprint-plan update
```
)
It makes at most one recommendation per run

For more detail on a specific story, the user can read the story file directly or run

/story-readiness [path]

For sprint replanning, use

/sprint-plan update

. For end-of-sprint retrospective, use

/milestone-review

该技能为只读模式，仅报告从磁盘文件中观察到的事实。

不会更新 Sprint 计划
不会修改故事状态
不会提出范围缩减建议（该操作需使用
```
/sprint-plan update
```
）
每次运行最多给出一项建议

如需了解特定故事的详细信息，用户可直接读取故事文件或运行

/story-readiness [path]

。

如需重新规划 Sprint，请使用

/sprint-plan update

。如需 Sprint 结束回顾，请使用

/milestone-review

。