MISSION.md 格式

MISSION.md 位于工作区根目录。它记录用户学习该主题的原因。每个教学决策 — 下一步教什么、呈现哪些资源、设计哪些练习 — 都应回溯到本文档。

模板

# Mission: {Topic}

## Why
{1-3 sentences. The concrete real-world goal the user is chasing. What changes in their life or work when they have this skill? Avoid abstract framings like "to understand X" — push for the underlying outcome.}

## Success looks like
- {A specific, observable thing the user will be able to do}
- {Another specific thing}
- {…}

## Constraints
- {Time, budget, prior commitments, learning preferences, anything that bounds the approach}

## Out of scope
- {Adjacent topics the user explicitly does not want to chase right now — protects the zone of proximal development}

规则

• 每个工作区一个 mission。 若用户想学两件无关的事，那是两个工作区。
• 具体优于抽象。 "Run a half marathon by October" 胜过 "get fitter"。"Ship a Rust CLI to my team" 胜过 "learn Rust"。
• 对含糊表述要追问。 若用户说不清原因，在写任何东西前先访谈他们。糟糕的 mission 比没有 mission 更糟。
• 现实变化时修订。 Mission 会变。用户目标移动时，更新本文件 — 不要留下过时的 mission 引导后续会话。
• 保持简短。 若 MISSION.md 超过一屏，它已从指南针变成计划书。