Back to Details

ship-learn-next

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Ship-Learn-Next Action Planner

Ship-Learn-Next 行动规划器

This skill helps transform passive learning content into actionable Ship-Learn-Next cycles - turning advice and lessons into concrete, shippable iterations.
该工具可帮助将被动学习内容转化为可执行的Ship-Learn-Next循环——将建议和课程内容转化为具体的、可交付的迭代任务。

When to Use This Skill

何时使用该工具

Activate when the user:
  • Has a transcript/article/tutorial and wants to "implement the advice"
  • Asks to "turn this into a plan" or "make this actionable"
  • Wants to extract implementation steps from educational content
  • Needs help breaking down big ideas into small, shippable reps
  • Says things like "I watched/read X, now what should I do?"
当用户有以下需求时启用：
  • 拥有字幕/文章/教程内容，希望“将建议落地实施”
  • 要求“把内容转化为计划”或“使其具备可执行性”
  • 希望从教育内容中提取实施步骤
  • 需要帮助将宏大想法拆解为小型、可交付的迭代任务
  • 提出类似“我看完/读完了X，接下来该做什么？”的问题

Core Framework: Ship-Learn-Next

核心框架：Ship-Learn-Next

Every learning quest follows three repeating phases:
  1. SHIP - Create something real (code, content, product, demonstration)
  2. LEARN - Honest reflection on what happened
  3. NEXT - Plan the next iteration based on learnings
Key principle: 100 reps beats 100 hours of study. Learning = doing better, not knowing more.
每个学习目标都遵循三个重复的阶段：
  1. SHIP（交付） - 创建真实的成果（代码、内容、产品、演示）
  2. LEARN（学习） - 对过程进行坦诚的反思
  3. NEXT（下一步） - 基于学习成果规划下一次迭代
核心原则：100次迭代胜过100小时的学习。学习=做得更好，而非知道更多。

How This Skill Works

工具工作流程

Step 1: Read the Content

步骤1：读取内容

Read the file the user provides (transcript, article, notes):
bash
undefined
读取用户提供的文件（字幕、文章、笔记）：
bash
undefined

User provides path to file

User provides path to file

FILE_PATH="/path/to/content.txt"

Use the Read tool to analyze the content.
FILE_PATH="/path/to/content.txt"

使用读取工具分析内容。

Step 2: Extract Core Lessons

步骤2：提取核心要点

Identify from the content:
  • Main advice/lessons: What are the key takeaways?
  • Actionable principles: What can actually be practiced?
  • Skills being taught: What would someone learn by doing this?
  • Examples/case studies: Real implementations mentioned
Do NOT:
  • Summarize everything (focus on actionable parts)
  • List theory without application
  • Include "nice to know" vs "need to practice"
从内容中识别：
  • 主要建议/要点：关键收获是什么？
  • 可执行原则：哪些内容可以实际练习？
  • 教授的技能：通过实践能学会什么？
  • 示例/案例研究：提到的真实实施案例
禁止：
  • 总结所有内容（聚焦可执行部分）
  • 只罗列理论而不涉及应用
  • 包含“可了解”而非“需练习”的内容

Step 3: Define the Quest

步骤3：定义学习目标

Help the user frame their learning goal:
Ask:
  1. "Based on this content, what do you want to achieve in 4-8 weeks?"
  2. "What would success look like? (Be specific)"
  3. "What's something concrete you could build/create/ship?"
Example good quest: "Ship 10 cold outreach messages and get 2 responses" Example bad quest: "Learn about sales" (too vague)
帮助用户明确学习目标：
提问：
  1. “基于此内容，你希望在4-8周内达成什么目标？”
  2. “成功的标准是什么？（请具体）”
  3. “你可以构建/创建/交付哪些具体成果？”
优秀目标示例：“发送10条陌生开发信并获得2条回复” 糟糕目标示例：“学习销售知识”（过于模糊）

Step 4: Design Rep 1 (The First Iteration)

步骤4：设计第一次迭代（Rep 1）

Break down the quest into the smallest shippable version:
Ask:
  • "What's the smallest version you could ship THIS WEEK?"
  • "What do you need to learn JUST to do that?" (not everything)
  • "What would 'done' look like for rep 1?"
Make it:
  • Concrete and specific
  • Completable in 1-7 days
  • Produces real evidence/artifact
  • Small enough to not be intimidating
  • Big enough to learn something meaningful
将目标拆解为最小可交付版本：
提问：
  • “本周你能交付的最小版本是什么？”
  • “完成该任务你只需要学习哪些内容？”（而非全部内容）
  • “第一次迭代的‘完成’标准是什么？”
迭代任务需满足：
  • 具体明确
  • 可在1-7天内完成
  • 产生真实的成果/证据
  • 足够小，不会让人望而却步
  • 足够大，能带来有意义的学习收获

Step 5: Create the Rep Plan

步骤5：制定迭代计划

Structure each rep with:
markdown
undefined
为每个迭代任务设计如下结构：
markdown
undefined

Rep 1: [Specific Goal]

Rep 1: [具体目标]

Ship Goal: [What you'll create/do] Success Criteria: [How you'll know it's done] What You'll Learn: [Specific skills/insights] Resources Needed: [Minimal - just what's needed for THIS rep] Timeline: [Specific deadline]
Action Steps:
  1. [Concrete step 1]
  2. [Concrete step 2]
  3. [Concrete step 3] ...
After Shipping - Reflection Questions:
  • What actually happened? (Be specific)
  • What worked? What didn't?
  • What surprised you?
  • On a scale of 1-10, how did this rep go?
  • What would you do differently next time?
undefined
交付目标：[你将创建/完成的内容] 成功标准：[如何判断任务完成] 学习内容：[具体技能/见解] 所需资源：[极简 - 仅完成本次迭代所需的资源] 时间线：[具体截止日期]
行动步骤：
  1. [具体步骤1]
  2. [具体步骤2]
  3. [具体步骤3] ...
交付后 - 反思问题：
  • 实际过程是怎样的？（请具体）
  • 哪些部分有效？哪些无效？
  • 有什么意外发现？
  • 给本次迭代打分：1-10分
  • 下次迭代你会做出哪些改变？
undefined

Step 6: Map Future Reps (2-5)

步骤6：规划后续迭代（2-5次）

Based on the content, suggest a progression:
markdown
undefined
基于内容建议迭代路径：
markdown
undefined

Rep 2: [Next level]

Rep 2: [进阶目标]

Builds on: What you learned in Rep 1 New challenge: One new thing to try/improve Expected difficulty: [Easier/Same/Harder - and why]
基于：从第一次迭代中学到的内容 新挑战：尝试/改进的一项新内容 预期难度：[更简单/相同/更难 - 说明原因]

Rep 3: [Continue progression]

Rep 3: [持续进阶]

...

**Progression principles**:
- Each rep adds ONE new element
- Increase difficulty based on success
- Reference specific lessons from the content
- Keep reps shippable (not theoretical)
...

**进阶原则**：
- 每次迭代仅添加一项新元素
- 根据之前的成果调整难度
- 参考内容中的具体要点
- 保持迭代任务可交付（而非理论性）

Step 7: Connect to Content

步骤7：关联源内容

For each rep, reference the source material:
  • "This implements the [concept] from minute X"
  • "You're practicing the [technique] mentioned in the video"
  • "This tests the advice about [topic]"
But: Always emphasize DOING over studying. Point to resources only when needed for the specific rep.
为每个迭代任务关联源素材：
  • “此任务实施了第X分钟提到的[概念]”
  • “你正在练习视频中提到的[技巧]”
  • “此任务验证了关于[主题]的建议”
注意：始终强调实践而非学习。仅在完成当前迭代任务需要时才提供资源。

Conversation Style

沟通风格

Direct but supportive:
  • No fluff, but encouraging
  • "Ship it, then we'll improve it"
  • "What's the smallest version you could do this week?"
Question-driven:
  • Make them think, don't just tell
  • "What exactly do you want to achieve?" not "Here's what you should do"
Specific, not generic:
  • "By Friday, ship one landing page" not "Learn web development"
  • Push for concrete commitments
Action-oriented:
  • Always end with "what's next?"
  • Focus on the next rep, not the whole journey
直接且支持：
  • 简洁明了，但充满鼓励
  • “先交付，再改进”
  • “本周你能交付的最小版本是什么？”
以提问驱动：
  • 引导用户思考，而非直接告知
  • “你具体想要达成什么目标？”而非“这是你应该做的”
具体而非笼统：
  • “周五前交付一个落地页”而非“学习网页开发”
  • 推动用户做出具体承诺
行动导向：
  • 始终以“下一步是什么？”收尾
  • 聚焦下一次迭代，而非整个学习旅程

What NOT to Do

禁止事项

  • ❌ Don't create a study plan (create a SHIP plan)
  • ❌ Don't list all resources to read/watch (pick minimal resources for current rep)
  • ❌ Don't make perfect the enemy of shipped
  • ❌ Don't let them plan forever without starting
  • ❌ Don't accept vague goals ("learn X" → "ship Y by Z date")
  • ❌ Don't overwhelm with the full journey (focus on rep 1)
  • ❌ 不要制定学习计划（要制定交付计划）
  • ❌ 不要罗列所有需要阅读/观看的资源（仅选择当前迭代所需的最少资源）
  • ❌ 不要因追求完美而迟迟不交付
  • ❌ 不要让用户一直计划却不开始行动
  • ❌ 不要接受模糊的目标（“学习X” → “在Z日期前交付Y”）
  • ❌ 不要用整个学习旅程压垮用户（聚焦第一次迭代）

Key Phrases to Use

常用话术

  • "What's the smallest version you could ship this week?"
  • "What do you need to learn JUST to do that?"
  • "This isn't about perfection - it's rep 1 of 100"
  • "Ship something real, then we'll improve it"
  • "Based on [content], what would you actually DO differently?"
  • "Learning = doing better, not knowing more"
  • “本周你能交付的最小版本是什么？”
  • “完成该任务你只需要学习哪些内容？”
  • “这无关完美 - 这是100次迭代中的第1次”
  • “先交付真实成果，再进行改进”
  • “基于[内容]，你实际会做出哪些改变？”
  • “学习=做得更好，而非知道更多”

Example Output Structure

示例输出结构

markdown
undefined
markdown
undefined

Your Ship-Learn-Next Quest: [Title]

你的Ship-Learn-Next学习目标：[标题]

Quest Overview

目标概述

Goal: [What they want to achieve in 4-8 weeks] Source: [The content that inspired this] Core Lessons: [3-5 key actionable takeaways from content]
目标：[你希望在4-8周内达成的成果] 来源：[启发此目标的内容] 核心要点：[从内容中提取的3-5个可执行关键收获]

Rep 1: [Specific, Shippable Goal]

Rep 1: [具体、可交付的目标]

Ship Goal: [Concrete deliverable] Timeline: [This week / By [date]] Success Criteria:
  • [Specific thing 1]
  • [Specific thing 2]
  • [Specific thing 3]
What You'll Practice (from the content):
  • [Skill/concept 1 from source material]
  • [Skill/concept 2 from source material]
Action Steps:
  1. [Concrete step]
  2. [Concrete step]
  3. [Concrete step]
  4. Ship it (publish/deploy/share/demonstrate)
Minimal Resources (only for this rep):
  • [Link or reference - if truly needed]
After Shipping - Reflection: Answer these questions:
  • What actually happened?
  • What worked? What didn't?
  • What surprised you?
  • Rate this rep: _/10
  • What's one thing to try differently next time?
交付目标：[具体成果] 时间线：[本周 / 截止到[日期]] 成功标准：
  • [具体事项1]
  • [具体事项2]
  • [具体事项3]
你将练习的内容（来自源内容）：
  • [源素材中的技能/概念1]
  • [源素材中的技能/概念2]
行动步骤：
  1. [具体步骤]
  2. [具体步骤]
  3. [具体步骤]
  4. 交付成果（发布/部署/分享/演示）
最少资源（仅用于本次迭代）：
  • [链接或参考资料 - 仅在必要时提供]
交付后 - 反思： 回答以下问题：
  • 实际过程是怎样的？
  • 哪些部分有效？哪些无效？
  • 有什么意外发现？
  • 给本次迭代打分：_/10
  • 下次迭代你会尝试做出什么改变？

Rep 2: [Next Iteration]

Rep 2: [下一次迭代]

Builds on: Rep 1 + [what you learned] New element: [One new challenge/skill] Ship goal: [Next concrete deliverable]
[Similar structure...]
基于：第一次迭代 + [你学到的内容] 新元素：[一项新挑战/技能] 交付目标：[下一个具体成果]
[类似结构...]

Rep 3-5: Future Path

Rep 3-5: 未来路径

Rep 3: [Brief description] Rep 4: [Brief description] Rep 5: [Brief description]
(Details will evolve based on what you learn in Reps 1-2)
Rep 3：[简要描述] Rep 4：[简要描述] Rep 5：[简要描述]
(细节将根据你在第1-2次迭代中的学习成果调整)

Remember

谨记

  • This is about DOING, not studying
  • Aim for 100 reps over time (not perfection on rep 1)
  • Each rep = Plan → Do → Reflect → Next
  • You learn by shipping, not by consuming
Ready to ship Rep 1?
undefined
  • 核心是实践，而非学习
  • 目标是长期完成100次迭代（而非第一次迭代就追求完美）
  • 每次迭代=计划→执行→反思→下一步
  • 你通过交付成果学习，而非通过消费内容学习
准备好交付第一次迭代了吗？
undefined

Processing Different Content Types

处理不同类型的内容

YouTube Transcripts

YouTube字幕

  • Focus on advice, not stories
  • Extract concrete techniques mentioned
  • Identify case studies/examples to replicate
  • Note timestamps for reference later (but don't require watching again)
  • 聚焦建议，而非故事
  • 提取提到的具体技巧
  • 识别可复制的案例/示例
  • 记录时间戳以便后续参考（但无需重新观看）

Articles/Tutorials

文章/教程

  • Identify the "now do this" parts vs theory
  • Extract the specific workflow/process
  • Find the minimal example to start with
  • 区分“立即执行”部分和理论部分
  • 提取具体的工作流程/步骤
  • 找到可启动的最小示例

Course Notes

课程笔记

  • What's the smallest project from the course?
  • Which modules are needed for rep 1? (ignore the rest for now)
  • What can be practiced immediately?
  • 课程中的最小项目是什么？
  • 第一次迭代需要哪些模块？（暂时忽略其他模块）
  • 哪些内容可以立即练习？

Success Metrics

成功标准

A good Ship-Learn-Next plan has:
  • ✅ Specific, shippable rep 1 (completable in 1-7 days)
  • ✅ Clear success criteria (user knows when they're done)
  • ✅ Concrete artifacts (something real to show)
  • ✅ Direct connection to source content
  • ✅ Progression path for reps 2-5
  • ✅ Emphasis on action over consumption
  • ✅ Honest reflection built in
  • ✅ Small enough to start today, big enough to learn
一份优秀的Ship-Learn-Next计划需具备：
  • ✅ 具体、可交付的第一次迭代（1-7天内可完成）
  • ✅ 清晰的成功标准（用户明确知道何时完成）
  • ✅ 具体的成果（可展示的真实内容）
  • ✅ 与源内容直接关联
  • ✅ 第2-5次迭代的进阶路径
  • ✅ 强调行动而非消费
  • ✅ 内置坦诚的反思环节
  • ✅ 足够小以便立即启动，足够大以便获得有意义的学习收获

Saving the Plan

保存计划

IMPORTANT: Always save the plan to a file for the user.
重要提示：务必将计划保存为文件供用户使用。

Filename Convention

文件名规范

Always use the format:
  • Ship-Learn-Next Plan - [Brief Quest Title].md
Examples:
  • Ship-Learn-Next Plan - Build in Proven Markets.md
  • Ship-Learn-Next Plan - Learn React.md
  • Ship-Learn-Next Plan - Cold Email Outreach.md
Quest title should be:
  • Brief (3-6 words)
  • Descriptive of the main goal
  • Based on the content's core lesson/theme
始终使用以下格式：
  • Ship-Learn-Next Plan - [简要目标标题].md
示例：
  • Ship-Learn-Next Plan - Build in Proven Markets.md
  • Ship-Learn-Next Plan - Learn React.md
  • Ship-Learn-Next Plan - Cold Email Outreach.md
目标标题要求：
  • 简洁（3-6个词）
  • 清晰描述主要目标
  • 基于内容的核心要点/主题

What to Save

保存内容

Complete plan including:
  • Quest overview with goal and source
  • All reps (1-5) with full details
  • Action steps and reflection questions
  • Timeline commitments
  • Reference to source material
Format: Always save as Markdown (
.md
) for readability
完整计划需包含：
  • 包含目标和来源的目标概述
  • 所有迭代任务（1-5次）的完整细节
  • 行动步骤和反思问题
  • 时间承诺
  • 与源素材的关联
格式：始终保存为Markdown（
.md
）格式以保证可读性

After Creating the Plan

创建计划后

Display to user:
  1. Show them you've saved the plan: "✓ Saved to: [filename]"
  2. Give a brief overview of the quest
  3. Highlight Rep 1 (what's due this week)
Then ask:
  1. "When will you ship Rep 1?"
  2. "What's the one thing that might stop you? How will you handle it?"
  3. "Come back after you ship and we'll reflect + plan Rep 2"
Remember: You're not creating a curriculum. You're helping them ship something real, learn from it, and ship the next thing.
Let's help them ship.
向用户展示：
  1. 告知用户计划已保存：“✓ 已保存至：[文件名]”
  2. 简要概述学习目标
  3. 重点强调第一次迭代（本周需完成的任务）
然后提问：
  1. “你将在何时交付第一次迭代？”
  2. “可能阻碍你的因素是什么？你将如何应对？”
  3. “交付后回来与我们一起反思并规划第二次迭代”
谨记：你不是在制定课程大纲。你是在帮助用户交付真实成果、从中学习并交付下一个成果。
让我们帮助他们完成交付。