← teach · 技能图谱

MISSION-FORMAT

MISSION.md 的格式规范

Template

模板

MISSION.md lives at the workspace root. It captures the reason the user is learning this topic. Every teaching decision — what to teach next, which resources to surface, which exercises to design — should trace back to this document.

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

Template

模板

Rules

规则

  • One mission per workspace. If the user wants to learn two unrelated things, that is two workspaces.
  • Concrete over abstract. "Run a half marathon by October" beats "get fitter." "Ship a Rust CLI to my team" beats "learn Rust."
  • Push back on vagueness. If the user cannot articulate why, interview them before writing anything. A bad mission is worse than no mission.
  • Revise when reality shifts. Missions change. When the user's goal moves, update this file — don't leave a stale mission steering future sessions.
  • Keep it short. If MISSION.md runs past a screen, it has stopped being a compass and started being a plan.
  • 每个工作区一个使命。如果用户想学两个不相关的东西，那就是两个工作区。
  • 具体胜于抽象。"10 月前跑完半程马拉松"比"变得更健康"好。"给团队交付一个 Rust CLI"比"学 Rust"好。
  • 拒绝模糊。如果用户无法清晰表达原因，在写任何内容之前先追问他们。一个糟糕的使命比没有使命更糟。
  • 现实变化时修订。使命会变。当用户的目标改变时，更新此文件——不要让过时的使命误导未来的会话。
  • 保持简短。如果 MISSION.md 超过一屏，它就不再是指南针，而变成了计划。