tool-foundation-sprint-readiness

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Foundation Sprint Readiness

Foundation Sprint 准备度评估

Assess whether a Foundation Sprint fits the team's current situation. Most sprints that fail were sprints that should not have been run. A 30-45 minute readiness diagnostic catches that failure mode before two days of facilitated work are spent.

Family contract:

docs/reference/skill-families/foundation-sprint-skills-contract.md

. This skill is a member of

foundation-sprint-skills

and conforms to the family frontmatter and Decider Checkpoint requirements.

评估Foundation Sprint是否适配团队当前状况。大多数失败的Sprint，本质上就是不该启动的Sprint。一场30-45分钟的准备度诊断，能在投入两天引导式工作前就规避这类失败风险。

家族契约：

docs/reference/skill-families/foundation-sprint-skills-contract.md

。本技能属于

foundation-sprint-skills

家族，符合家族前置信息和Decider Checkpoint要求。

When to Use

使用场景

A team is considering starting a Foundation Sprint and needs a fast diagnosis before committing two days.
A founder or PM has a "should we run a Foundation Sprint?" question and wants structured input rather than a vibes check.
An existing sprint commitment is on the calendar and the team wants to validate that prerequisites are in place.
Re-running a Foundation Sprint after invalidated assumptions: use to confirm new context is ready.

团队考虑启动Foundation Sprint，需要在投入两天时间前快速得到诊断结果
创始人或产品经理有「我们是否应该开展Foundation Sprint？」的疑问，希望获得结构化意见而非主观判断
已将Sprint安排进日程，团队希望验证前置条件是否已满足
原有假设被推翻后重新启动Foundation Sprint：用于确认新的业务环境已准备就绪

When NOT to Use

非适用场景

The team has already decided to run the sprint and just needs the brief. Use
```
tool-foundation-sprint-brief
```
instead.
The team needs deep customer discovery: run customer research or problem framing first; the Foundation Sprint depends on existing customer knowledge.
The decision is small and a full Foundation Sprint is overkill. Use a lighter prioritization or decision tool.
No Decider is available and one cannot be appointed. Foundation Sprint requires fast strategic calls; without authority it produces options without commitment.

团队已决定开展Sprint，仅需要简要说明：请改用
```
tool-foundation-sprint-brief
```
团队需要深入的客户探索：先开展客户研究或问题定义工作；Foundation Sprint依赖已有的客户认知
决策事项规模较小，使用完整的Foundation Sprint过于冗余：请使用更轻量化的优先级排序或决策工具
没有Decider可用且无法指定：Foundation Sprint需要快速做出战略决策；缺乏决策权限的情况下，只能生成方案但无法达成承诺

What This Skill Produces

本技能产出物

A single bundled artifact with five sections:

Readiness verdict: Go / Conditional Go / Wait
Diagnosis: what is in place, what is missing, what is uncertain
Recommended preconditions (when verdict is Wait or Conditional Go): the prerequisite work the team should do before the sprint
Recommended attendee list (when verdict is Go or Conditional Go): the 3-5 people who should be in the room, with role expectations
Pre-sprint activities (when verdict is Go): the prep work to complete in the days before Day 1

See

references/TEMPLATE.md

for the canonical structure and

references/EXAMPLE.md

for a worked example using the Brainshelf book-catalog thread.

一份包含五个部分的整合型产出物：

准备度结论：可以开展/有条件开展/暂缓
诊断结果：已具备的条件、缺失的要素、不确定的事项
推荐前置条件（结论为「暂缓」或「有条件开展」时）：团队在启动Sprint前应完成的前置工作
推荐参会人员清单（结论为「可以开展」或「有条件开展」时）：3-5名应参与的核心人员，及对应的角色预期
Sprint前准备活动（结论为「可以开展」时）：在Sprint第一天前需完成的准备工作

规范结构请参考

references/TEMPLATE.md

，基于Brainshelf图书目录案例的完整示例请参考

references/EXAMPLE.md

。

Inference Inputs

推理输入项

The skill runs an inference pass over these inputs to produce the verdict:

Input	What the skill does with it
Initiative description	Determines whether a Foundation Sprint is the right tool (vs problem framing, customer research, or a Design Sprint)
Team composition draft	Checks roster against the Foundation Sprint role requirements; flags missing roles
Decider name and availability	Confirms Decider can attend both days; flags partial availability as Conditional Go risk
Existing customer/market knowledge level (self-assessed 1-10)	Below 5 indicates deep discovery is needed first; 5-7 indicates Conditional Go with research prep; 8+ indicates Go
(Optional) Existing competitor and alternative knowledge	Flags gaps that can be closed by overnight prep
(Optional) Logistics constraints	Confirms two days can actually be cleared

If a load-bearing input is missing or low-confidence, the skill flags it explicitly and proposes how to close the gap before the sprint.

本技能会基于以下输入项进行推理以得出结论：

输入项	技能处理逻辑
举措描述	判断Foundation Sprint是否为合适工具（对比问题定义、客户研究或Design Sprint）
初步团队构成	核对人员是否符合Foundation Sprint的角色要求；标记缺失的角色
Decider姓名及可用性	确认Decider能全程参与两天的Sprint；将部分时间可用标记为「有条件开展」的风险点
现有客户/市场认知水平（自我评估1-10分）	低于5分表示需先开展深度探索；5-7分表示需先完成研究准备后可「有条件开展」；8分及以上表示「可以开展」
（可选）现有竞品及替代方案认知	标记可通过夜间准备填补的认知缺口
（可选）后勤限制	确认是否能腾出完整的两天时间

若关键输入项缺失或可信度低，技能会明确标记，并提出在Sprint前填补缺口的方案。

Readiness Criteria (8 Canonical Checks)

准备度标准（8项规范检查）

The skill evaluates the team against these eight criteria, drawn from Knapp/Zeratsky (Click) and Character Capital's Foundation Sprint guide:

Initiative is named and concrete. The team can name the project, product area, or strategic question.
The stakes are meaningful. A wrong starting direction would be costly.
The team has existing knowledge. Real customer, market, competitor, or domain context to make informed choices.
The Decider is available. Strategic calls can be made during the sprint.
The team is small enough. No more than five core decision participants is preferred.
Inputs are collected. Existing research, customer examples, competitor notes, metrics are ready.
The output has a path to testing. The team can use a Design Sprint, experiment, customer research, or another validation method afterward.
The organization tolerates explicit tradeoffs. Foundation Sprint forces choosing a top bet and a backup, not preserving every possibility.

Pattern	Verdict
All 8 criteria met cleanly	Go
1-2 criteria are "yellow flags" but addressable in evening prep	Conditional Go with documented prep
3 or more criteria fail, or any of 1-4 is a hard fail	Wait with recommended prerequisite work

Treat the criteria as load-bearing, not a checklist to game. A team that papers over a real gap with "yes, technically" should get a Conditional Go with the gap surfaced.

技能会基于Knapp/Zeratsky（《Click》）及Character Capital的Foundation Sprint指南，从以下8项标准评估团队：

举措命名明确且具体：团队能清晰说出项目、产品领域或战略问题的名称
风险影响重大：错误的初始方向会带来较高成本
团队具备现有认知：拥有真实的客户、市场、竞品或领域背景信息以做出明智决策
Decider可全程参与：能在Sprint期间做出战略决策
团队规模合适：核心决策参与者不超过5人为佳
输入资料已收集：现有研究、客户案例、竞品分析、指标数据已准备就绪
产出物有验证路径：团队后续可通过Design Sprint、实验、客户研究或其他验证方法验证结果
组织接受明确的取舍：Foundation Sprint要求选择核心方向及备选方案，而非保留所有可能性

情况	结论
8项标准全部满足	可以开展
1-2项标准为「黄色预警」但可通过夜间准备解决	有条件开展，并记录需完成的准备工作
3项及以上标准不满足，或第1-4项中有任意一项完全不满足	暂缓，并推荐需完成的前置工作

请将这些标准视为核心要求，而非可应付的 checklist。若团队用「理论上满足」掩盖真实缺口，应给出「有条件开展」结论并明确指出该缺口。

Common Pitfalls

常见误区

Skipping the diagnostic because "we're going to run it anyway." This is the most common cause of failed sprints. The diagnostic costs 45 minutes; the failed sprint costs 16 hours of team time plus opportunity cost.
Treating Conditional Go as Go without doing the prep. Conditional Go means "Go after closing these gaps." If the gaps are not closed by Day 1 morning, the sprint enters the failure mode the diagnostic was meant to prevent.
Confusing readiness assessment with problem framing. This skill assesses whether to run a Foundation Sprint, not whether the team has the right problem. If the problem is unclear, the verdict is Wait with "do problem framing first" as the precondition.
No Decider, no sprint. A team with no Decider available is not ready, full stop. Appointing a "Decider for the day" who lacks real authority does not solve this.
Cargo-cult readiness. Reading the criteria and answering yes to all eight without checking does not produce readiness. The skill's value is in the honest diagnosis.

跳过诊断直接开展Sprint：这是Sprint失败最常见的原因。诊断仅需45分钟，而失败的Sprint会耗费团队16小时的时间及机会成本
将「有条件开展」等同于「可以开展」而不完成准备工作：「有条件开展」意味着「填补这些缺口后再开展」。若在Sprint第一天上午仍未填补缺口，Sprint就会陷入诊断本应规避的失败模式
混淆准备度评估与问题定义：本技能评估的是是否应开展Foundation Sprint，而非团队是否找到了正确的问题。若问题不明确，结论应为「暂缓」，并将「先完成问题定义」作为前置条件
无Decider则无法开展Sprint：没有Decider可用的团队完全不具备开展条件。指定一个「当日Decider」但无实际决策权无法解决该问题
形式化准备度评估：仅阅读标准并全部勾选「是」而不实际核查，无法真正确保准备就绪。本技能的价值在于诚实的诊断

Canonical Sources

规范来源

Knapp, J., and Zeratsky, J. Click: How to Make What People Want. Foundation Sprint readiness guidance.
Character Capital. "Foundation Sprint guide." https://www.character.vc/guide/foundation-sprint
Design Sprint Academy. "Foundation Sprint readiness criteria for enterprise." Used for the enterprise-context adjustments to canonical readiness.

Knapp, J. 和 Zeratsky, J. 《Click: How to Make What People Want》中关于Foundation Sprint准备度的指导内容
Character Capital. 《Foundation Sprint指南》. https://www.character.vc/guide/foundation-sprint
Design Sprint Academy. 《企业场景下的Foundation Sprint准备度标准》：用于针对企业场景调整规范准备度要求

Cross-Skill Usage

跨技能联动

This skill is the entry point of the foundation-sprint-skills family. It has no prerequisites (the

metadata.prerequisites

field is intentionally empty).

When the verdict is Go, the natural next invocation is

tool-foundation-sprint-brief

to set up the sprint logistics. When the verdict is Wait, the team typically does prerequisite work (problem framing, customer research) before re-invoking this skill.

tool-note-and-vote

may be invoked once during the readiness conversation if the team disagrees on whether a Foundation Sprint is the right tool. In practice, this is rare; the diagnostic is usually conclusive.

本技能是foundation-sprint-skills家族的入口技能，无前置要求（

metadata.prerequisites

字段特意留空）。

当结论为「可以开展」时，下一步自然是调用

tool-foundation-sprint-brief

来安排Sprint后勤事项。当结论为「暂缓」时，团队通常需先完成前置工作（问题定义、客户研究），之后再重新调用本技能。

若团队在准备度讨论中对Foundation Sprint是否为合适工具存在分歧，可调用

tool-note-and-vote

一次。实际操作中这种情况很少见，因为诊断通常具有明确结论。

Decider Checkpoint

This skill ends with a Decider Checkpoint in

references/TEMPLATE.md

. The Decider signs off on the verdict (Go / Conditional Go / Wait) and explicitly accepts the diagnosis. Without Decider sign-off, the verdict is advisory; with sign-off, it is the commitment that triggers (or postpones) the sprint.

本技能在

references/TEMPLATE.md

中以Decider Checkpoint收尾。Decider需对结论（可以开展/有条件开展/暂缓）签字确认，并明确接受诊断结果。若无Decider签字，结论仅为参考意见；签字确认后，结论即为触发（或推迟）Sprint的正式承诺。