Back to Details

tool-foundation-sprint-brief

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese
<!-- PM-Skills | https://github.com/product-on-purpose/pm-skills | Apache 2.0 -->
<!-- PM-Skills | https://github.com/product-on-purpose/pm-skills | Apache 2.0 -->

Foundation Sprint Brief

Foundation Sprint 简报

Produce the one-page brief that aligns the team on scope, decision target, participants, logistics, and success criteria before Day 1 begins. A well-built brief prevents Day 1 from opening with re-litigation of why-are-we-here; a missing or vague brief almost guarantees it.
Family contract: 
docs/reference/skill-families/foundation-sprint-skills-contract.md
. This skill is a member of 
foundation-sprint-skills
.
在第1天开始前生成一份单页简报，让团队在范围、决策目标、参与者、后勤安排和成功标准上达成一致。一份完善的简报能避免第1天开场就陷入“我们为何在此”的重复争论；而缺失或模糊的简报几乎必然会引发这类问题。
所属技能族协议：
docs/reference/skill-families/foundation-sprint-skills-contract.md
。本技能属于
foundation-sprint-skills
技能族。

When to Use

使用时机

  • The readiness verdict from 
    tool-foundation-sprint-readiness
    is Go (or Conditional Go with preconditions cleared).
  • The sprint has dates blocked on calendars and you need the artifact that names what the sprint is for.
  • The team has prep activities scheduled and you need a written reference for what to bring.
  • A skeptical exec wants to know "what is the team doing for two days?" and you need an answer that fits on one page.
  • 来自
    tool-foundation-sprint-readiness
    的就绪判定为“通过（Go）”（或“有条件通过（Conditional Go）”且前提条件已满足）。
  • 冲刺日期已在日历上锁定，你需要一份明确冲刺目标的成果物。
  • 团队已安排准备活动，你需要一份书面参考来明确需携带的材料。
  • 持怀疑态度的高管询问“团队这两天要做什么？”，你需要一份单页的答复。

When NOT to Use

不适用时机

  • The sprint has already started. The brief is a prep artifact, not an in-sprint deliverable. If Day 1 is happening, run 
    tool-foundation-sprint-basics
    instead.
  • The readiness verdict is Wait. The brief cannot fix an unready team; close the preconditions first, then re-run readiness, then invoke this skill.
  • The team wants a strategy document. The brief is internal prep, not a stakeholder deliverable. If a stakeholder document is needed, that is a downstream artifact.
  • The brief threatens to become a multi-page strategic document. Stop and reframe: the canonical brief is one page.
  • 冲刺已开始。本简报是准备阶段的成果物，而非冲刺中的交付物。如果第1天已启动，请改用
    tool-foundation-sprint-basics
    。
  • 就绪判定为“等待（Wait）”。简报无法解决团队未就绪的问题；先完成前提条件，重新进行就绪判定，再调用本技能。
  • 团队需要一份战略文档。本简报是内部准备材料，而非面向利益相关者的交付物。如果需要面向利益相关者的文档，那是后续的成果物。
  • 简报有变成多页战略文档的趋势。请停止并重新调整：标准简报必须是单页。

What This Skill Produces

本技能产出

A single bundled artifact with six sections:
  1. Initiative statement and stakes: one paragraph naming what the team is sprinting on and why a wrong direction would be costly.
  2. Decision the sprint must unlock: the open strategic question the sprint resolves. Single sentence.
  3. Team roster with role assignments: who is in the room and what role each person plays per section of the sprint.
  4. Logistics plan: dates, hours, location, format (in-person, remote, hybrid), tools, daily rhythm.
  5. Existing inputs to bring: the research, customer examples, competitor notes, metrics, and constraints the team should reference during the sprint.
  6. Readiness reaffirmation: a final check that the Go verdict from 
    tool-foundation-sprint-readiness
    still holds.
See 
references/TEMPLATE.md
for the canonical structure and 
references/EXAMPLE.md
for the Brainshelf book-catalog brief.
一份包含六个部分的整合成果物：
  1. 倡议声明与风险：一段文字，说明团队冲刺的内容以及错误方向会带来的损失。
  2. 冲刺必须明确的决策：冲刺要解决的开放性战略问题。单句表述。
  3. 带角色分配的团队名单：参与人员名单，以及每个人在冲刺各环节中扮演的角色。
  4. 后勤计划：日期、时长、地点、形式（线下、远程、混合）、工具、每日节奏。
  5. 需携带的现有输入材料：团队在冲刺中需参考的研究资料、客户案例、竞品笔记、指标数据和约束条件。
  6. 就绪状态确认：最终检查
    tool-foundation-sprint-readiness
    给出的“通过”判定是否仍然有效。
参考
references/TEMPLATE.md
获取标准结构，参考
references/EXAMPLE.md
获取Brainshelf图书目录简报示例。

Inference Inputs

推理输入

InputWhat the skill does with it
Readiness verdict and recommendations (from 
tool-foundation-sprint-readiness
)		Pulls the recommended attendees, preconditions, and pre-sprint activities into the brief; flags any precondition that has not been closed
Initiative descriptionCompresses into one paragraph for the Initiative Statement section
Team rosterMaps people to the required Foundation Sprint roles (Decider, Facilitator, PM, Design, Engineering, Customer Expert)
Logistics constraintsProduces the dates/hours/location/format/tools matrix; flags any constraint that would force the sprint to extend beyond two days
(Optional) Skeptical-exec talking pointsTightens the Stakes paragraph to address why-now and why-this concerns
输入技能处理方式
就绪判定与建议（来自
tool-foundation-sprint-readiness
）		将推荐参会人员、前提条件和冲刺前活动纳入简报；标记任何未满足的前提条件
倡议描述压缩为一段文字，用于“倡议声明”部分
团队名单将人员对应到Foundation Sprint所需角色（Decider、Facilitator、PM、Design、Engineering、Customer Expert）
后勤约束生成日期/时长/地点/形式/工具矩阵；标记任何会导致冲刺超过两天的约束条件
（可选）持怀疑态度的高管沟通要点优化“风险”段落，回应“为何是现在”和“为何是这个方案”的疑虑

Brief Length Discipline

简报篇幅规范

The brief MUST fit on one page (or one screen). The skill enforces this through structural choices, not raw character counts:
  • Initiative Statement: one paragraph, four sentences maximum.
  • Decision the sprint must unlock: one sentence.
  • Team Roster: table with one row per person.
  • Logistics: table.
  • Inputs to Bring: bulleted list, five items maximum.
  • Readiness Reaffirmation: checklist.
If the brief expands beyond this scope, the sprint is being over-engineered before it starts. The fix is not a longer brief; the fix is a clearer decision target.
简报必须适配单页（或单屏）。技能通过结构限制而非字符数来强制执行：
  • 倡议声明：一段文字，最多四句。
  • 冲刺必须明确的决策：单句。
  • 团队名单：每人一行的表格。
  • 后勤安排：表格。
  • 需携带的输入材料：项目符号列表，最多五项。
  • 就绪状态确认：勾选清单。
如果简报超出此范围，说明冲刺在启动前被过度设计。解决方法不是延长简报，而是明确决策目标。

Common Pitfalls

常见误区

  • Over-engineering the brief. The brief is a prep artifact, not a strategy doc. If it has an executive summary, an appendix, or a "background" section longer than one paragraph, it has drifted.
  • Treating the brief as a deliverable to stakeholders. Stakeholders do not read the brief; they read the Founding Hypothesis at the end. The brief is for the team. Sharing it publicly invites pre-sprint debate, which the sprint is supposed to resolve.
  • Vague decision target. "We will figure out our strategy" is not a decision. "We will commit to a top bet between [option A] and [option B]" is.
  • Logistics drift. "We'll figure out dates" or "we'll meet hybrid sometimes" telegraphs that the team has not actually committed to the sprint. Either dates and format are locked, or the readiness verdict was wrong.
  • Skipping readiness reaffirmation. The readiness verdict was a snapshot. If a precondition has slipped or the Decider's availability has changed since readiness, the brief needs to surface that, not paper over it.
  • 过度设计简报：简报是准备材料，而非战略文档。如果包含执行摘要、附录或超过一段的“背景”部分，就偏离了初衷。
  • 将简报作为面向利益相关者的交付物：利益相关者不会阅读简报；他们只会阅读最终的创始假设（Founding Hypothesis）。简报是给团队用的。公开分享会引发冲刺前的争论，而这些争论本应在冲刺中解决。
  • 模糊的决策目标：“我们将制定战略”不是一个明确的决策。“我们将在[选项A]和[选项B]之间选定核心赌注”才是。
  • 后勤安排模糊：“我们再确定日期”或“我们有时会混合办公”表明团队并未真正承诺冲刺。要么锁定日期和形式，要么就绪判定有误。
  • 跳过就绪状态确认：就绪判定是一个快照。如果自就绪判定以来，某个前提条件未满足或决策者的可用性发生变化，简报需要指出这一点，而非掩盖。

Canonical Sources

标准参考资料

  • Character Capital. "Foundation Sprint guide." Section on pre-sprint preparation and team scoping.
  • Knapp, J., and Zeratsky, J. Click: How to Make What People Want. Pre-sprint prep recommendations.
  • pm-skills 
    foundation-meeting-brief
    precedent: brief-structure pattern adapted for the strategic context of a Foundation Sprint rather than a meeting.
  • Character Capital. 《Foundation Sprint指南》。关于冲刺前准备和团队范围界定的章节。
  • Knapp, J., 和 Zeratsky, J. 《Click: How to Make What People Want》。冲刺前准备建议。
  • pm-skills 
    foundation-meeting-brief
    先例：简报结构模式适配了Foundation Sprint的战略场景，而非普通会议。

Cross-Skill Usage

跨技能使用

Prerequisites: 
tool-foundation-sprint-readiness
. The brief expects the readiness output as its primary input. When 
prerequisites
is honored, the brief inherits the readiness verdict, attendee recommendations, and pre-sprint activities; the skill then refines and commits them.
If the team has done equivalent prep without running the readiness skill explicitly (e.g., experienced sprint facilitator who knows the readiness criteria), the brief skill can be invoked directly. In that case, the skill body prompts the team to confirm the readiness criteria are met before generating the brief.
Next invocation in the sprint: 
tool-foundation-sprint-basics
on Day 1 morning.
前置技能：
tool-foundation-sprint-readiness
。本简报将就绪输出作为主要输入。当满足前置条件时，简报会继承就绪判定、参会人员建议和冲刺前活动；随后技能会对这些内容进行优化并确认。
如果团队未明确运行就绪技能但已完成等效准备（例如，熟悉就绪标准的资深冲刺引导者），可直接调用本简报技能。此时，技能会提示团队先确认就绪标准已满足，再生成简报。
冲刺中的下一个调用：第1天上午调用
tool-foundation-sprint-basics
。

Decider Checkpoint

决策者检查点

This skill ends with a Decider Checkpoint in 
references/TEMPLATE.md
. The Decider signs off on scope (the decision target), team (the roster and role assignments), success criteria (what makes the sprint successful or not), and the explicit tradeoff that the sprint will force a top bet rather than preserve all directions. Without sign-off, the brief is advisory; with sign-off, it is the contract for the next two days.
本技能在
references/TEMPLATE.md
中包含一个决策者检查点。决策者需对范围（决策目标）、团队（名单和角色分配）、成功标准（冲刺成功或失败的判定依据）以及冲刺将强制选定核心赌注而非保留所有方向的明确权衡进行签字确认。未经签字，简报仅为参考；签字后，简报即为接下来两天的协议。