phd-mode-switcher

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

PhD Mode Switcher

PhD模式切换器

Purpose

目标

Help the user apply the three-mode cognitive framework from the New Researcher Handbook (Section 8.1.3) — Deep Production, Wide Reading, Collaborative Engagement — to the day in front of them. The framework's core insight: productivity isn't primarily about "working harder"; it's about switching between fundamentally different cognitive modes with as little friction as possible, and respecting that the cost of switching is real.

This skill helps the user (1) diagnose which mode matches their current energy, context, and goals, and (2) structure a realistic day that doesn't try to do all three modes in small fragments.

帮助用户将《新研究者手册》（第8.1.3节）中的三种认知模式框架——Deep Production、Wide Reading、Collaborative Engagement——应用于当日工作。该框架的核心观点是：生产力的关键并非“更努力地工作”，而是尽可能顺畅地在本质不同的认知模式间切换，并正视切换成本的真实性。

此Skill将帮助用户（1）判断哪种模式匹配其当前精力、环境与目标，（2）规划合理的每日安排，避免将三种模式拆分为零散片段进行。

When to Use

使用场景

Start of the day / start of a work block
After a long meeting or interruption, when trying to figure out what's next
When the user reports feeling scattered or unfocused
When the user has a known chunk of time (e.g., "I have 4 hours this afternoon") and wants to use it well
When the user is struggling to switch from one kind of work to another

一天的开端 / 工作时段的起点
长时间会议或被打断后，需要确定下一步工作内容时
用户表示感到杂乱无章或无法集中注意力时
用户拥有明确时长的空闲时段（例如“我下午有4小时时间”）并希望高效利用时
用户难以从一种工作类型切换到另一种时

The Three Modes (Quick Reference)

三种模式（快速参考）

Deep Production Writing, implementing, doing focused technical work that requires sustained concentration. Needs uninterrupted blocks. Optimized for: papers, code, proofs, derivations, plot polishing.

Wide Reading Skimming papers, noting trends, digesting unfamiliar ideas, reviewing related work. Lower-intensity but high-value for keeping current. Optimized for: literature reviews, pre-writing exploration, idea generation.

Collaborative Engagement Meetings, discussions, code reviews, messages, managing collaborations. Low deep-focus but high interpersonal bandwidth. Optimized for: unblocking others, being unblocked, making decisions together.

Each mode benefits from different conditions (energy level, time of day, tools, location). Trying to do two modes simultaneously (e.g., reading papers with Slack open) usually does neither well.

Deep Production 写作、代码实现、完成需要持续专注的技术性工作。需要不受干扰的完整时段。适用场景：论文撰写、代码开发、证明推导、情节打磨。

Wide Reading 浏览论文、梳理趋势、消化陌生观点、综述相关研究。强度较低但价值高，有助于保持知识更新。适用场景：文献综述、写作前探索、创意生成。

Collaborative Engagement 会议、讨论、代码评审、消息回复、协作管理。对深度专注要求低，但需要较高的人际沟通带宽。适用场景：解决他人阻塞问题、寻求自身问题的解决方案、共同决策。

每种模式都需要不同的条件（精力水平、时段、工具、地点）。试图同时进行两种模式（例如开着Slack阅读论文）通常会导致两者都无法做好。

The Workflow

工作流程

Stage 1: Assess Current State

阶段1：评估当前状态

Ask the user a few quick questions:

What time is it, and how much time do you have in this work block?
What's your energy right now — fresh, moderate, or depleted?
What did you just finish doing? (This reveals the cost of switching.)
What's on your calendar for the rest of the day that will interrupt?

Don't make this a long interrogation. Three-four questions is enough.

向用户提出几个简短问题：

现在几点？你当前的工作时段有多长？
你现在的精力如何——充沛、中等还是耗尽？
你刚完成了什么工作？（这能反映切换成本）
今天剩余时间里，你的日程中有哪些会打断工作的安排？

不要进行冗长询问，3-4个问题即可。

Stage 2: Match Mode to State

阶段2：匹配模式与状态

Use this as a starting heuristic, then check against the user's actual situation:

State	Best-fit mode
Fresh energy, long uninterrupted block, clear technical task waiting	Deep Production
Moderate energy, scattered calendar, open-ended exploration needed	Wide Reading
Any energy, block < 90 min, pending replies / people waiting on you	Collaborative Engagement
Depleted energy, no specific deadline	Light reading, administrative clean-up, or honest rest

If the user's stated goal doesn't match the mode that fits their state, name the mismatch rather than papering over it. Example: "You want to finish writing the related work section, but you have a 45-minute block between meetings and you just came out of a 2-hour discussion. That's not a deep-production window. Either take a short break and batch the writing for a longer block tomorrow, or switch to reading the 3 papers you're going to cite — which is more fragmentable."

以下作为初始参考准则，再结合用户实际情况调整：

状态	适配模式
精力充沛、较长不受干扰时段、有明确技术任务待完成	Deep Production
精力中等、日程零散、需要开放式探索	Wide Reading
任意精力水平、时段小于90分钟、有待回复消息/他人等待你的反馈	Collaborative Engagement
精力耗尽、无明确截止日期	轻松阅读、行政事务整理或合理休息

如果用户的既定目标与其状态适配的模式不匹配，要指出这种不匹配而非含糊带过。示例：“你想要完成相关工作部分的写作，但你在两场会议之间只有45分钟的时段，而且刚结束一场2小时的讨论。这不是适合Deep Production的时段。要么短暂休息，把写作任务安排到明天更长的时段，要么切换到阅读你要引用的3篇论文——这类工作更适合碎片化时段。”

Stage 3: Design the Block

阶段3：规划当前时段

Once the mode is chosen, help the user make the block concrete:

For a Deep Production block:

What is the single deliverable you'll produce by the end? (Not "work on the paper" — "finish the methods section through subsection 3.2".)
What notifications/apps will be off for the duration?
What's the minimum viable environment? (Location, music, snacks — whatever the user knows works.)
Is there something that will disrupt this block (a meeting, a Slack message waiting)? Handle it first or explicitly defer it.

For a Wide Reading block:

What question are you reading for? Random reading is rarely high-value — reading with a specific question in mind is.
How many papers / what scope?
How will you capture what you learn? (Short notes in Notion/Obsidian, tagged highlights, a mental-map diagram.)

For a Collaborative Engagement block:

Who are the 3-5 people / threads you need to handle?
Is there anything that needs your decision, vs. things that need your response? Prioritize decisions.
What's your exit trigger — a time, a finished list, or something else?

确定模式后，帮助用户将时段规划具体化：

针对Deep Production时段：

时段结束时你将完成的单一交付成果是什么？（不是“写论文”——而是“完成方法部分至3.2小节”。）
时段内要关闭哪些通知/应用？
你需要的最低可行环境是什么？（地点、音乐、零食——任何你知道有效的因素。）
是否有会干扰该时段的事项（会议、待回复的Slack消息）？先处理或明确推迟。

针对Wide Reading时段：

你阅读的目的是为了回答什么问题？无目的的阅读价值极低——带着明确问题阅读才高效。
你要读多少篇论文/覆盖什么范围？
你将如何记录所学内容？（在Notion/Obsidian中写简短笔记、带标签的高亮内容、思维导图。）

针对Collaborative Engagement时段：

你需要对接的3-5个人/对话线程是谁/哪些？
哪些事项需要你做决策，哪些只需要你回复？优先处理决策类事项。
你的结束触发条件是什么——时间点、完成列表，还是其他？

Stage 4: Respect the Switching Cost

阶段4：重视切换成本

Before ending the session, remind the user of the Handbook's insight: mode-switching has a real cost that people systematically underestimate. Suggest clustering the rest of the day accordingly:

Don't interleave modes every 30 minutes. Group them into chunks.
A good default: Deep Production in the morning (while energy is highest and calendar is clearest), Wide Reading in low-energy afternoon pockets, Collaborative Engagement in scheduled blocks rather than continuously.
Acknowledge that many PhD students' schedules make this hard. The goal is better, not perfect.

会话结束前，提醒用户手册中的观点：模式切换存在真实成本，而人们往往会系统性低估这种成本。建议据此规划当日剩余时间：

不要每30分钟就切换一次模式。将同类模式集中安排成大块时段。
一个不错的默认方案：上午进行Deep Production（此时精力最充沛，日程也最清晰），下午精力低谷时段进行Wide Reading，Collaborative Engagement安排成固定时段而非持续进行。
要承认许多博士生的日程难以做到这一点。目标是变得更好，而非追求完美。

Stage 5: Output

阶段5：输出结果

Produce a short structured plan for the next block (or the rest of the day):

markdown

undefined

为下一个时段（或当日剩余时间）生成简短的结构化计划：

markdown

undefined

Mode Plan — [DATE] [TIME]

模式计划 — [日期] [时间]

Current state

当前状态

Energy: [level]
Available block: [duration]
Upcoming interruption: [when and what]

精力：[等级]
可用时段：[时长]
即将到来的干扰：[时间与事项]

This block

当前时段

Mode: [Deep Production / Wide Reading / Collaborative Engagement]
Specific deliverable: [what will be done]
Conditions to set up: [notifications off, location, etc.]
Exit trigger: [time or milestone]

模式：[Deep Production / Wide Reading / Collaborative Engagement]
具体交付成果：[要完成的内容]
需准备的环境：[关闭通知、地点等]
结束触发条件：[时间点或里程碑]

Rest of day (optional)

当日剩余安排（可选）

[Next block]: [mode + focus]
[Block after]: [mode + focus]

[下一个时段]：[模式 + 重点]
[再下一个时段]：[模式 + 重点]

Not this block

当前时段不做的事

[What the user is consciously deferring]


Keep this short. A 3-line plan is often better than a 10-line plan.

[用户主动推迟的事项]


计划要简短。3行的计划往往比10行的更实用。

Stage 6: End-of-Block Check (Optional)

阶段6：时段结束复盘（可选）

If the user returns at the end of a planned block, briefly reflect:

Did you stay in the chosen mode, or drift?
What tried to pull you out? (This is data for future planning.)
Is the next block still appropriate, or has the situation changed?

如果用户在计划时段结束后返回，可进行简短复盘：

你是否保持在选定的模式中，还是中途偏离了？
是什么因素试图让你分心？（这可为未来规划提供参考。）
下一个时段的安排是否仍然合适，还是情况已发生变化？

Tone and Posture

语气与定位

Be pragmatic. Don't moralize about the importance of deep work.
Acknowledge reality. If the user has 7 meetings today and can't protect any deep block, help them optimize around that instead of pretending the schedule is their choice.
Respect that the user knows their own rhythms. The framework is a scaffold, not a prescription. Morning people and night people both exist.
When energy is honestly depleted, rest is a legitimate recommendation. Don't force a productive mode onto a drained person.

务实为主。不要说教深度工作的重要性。
正视现实。如果用户今天有7场会议，无法保留任何深度工作时段，就帮助他们围绕这种情况优化，而非假装日程可以自主选择。
尊重用户自身的节奏。该框架是一个参考支架，而非硬性规定。早起型和熬夜型人群都存在。
当用户确实精力耗尽时，休息是合理建议。不要强迫疲惫的用户进入产出模式。

What Not to Do

禁忌事项

Don't produce elaborate hourly schedules. They don't survive contact with reality.
Don't pretend every day can be structured — some days are just meetings, or just debugging, or just emotionally hard. Help the user do what they can.
Don't use this skill as a task manager. It's about mode, not about listing everything the user has to do.
Don't ignore the user's stated preferences about time-of-day and environment.
Don't forget that rest is not a mode but a legitimate state. If the user is depleted and there's no hard deadline, say so.

不要制作复杂的小时级日程。这类日程在现实中往往无法执行。
不要假装每一天都能被规划——有些日子全是会议，或者全是调试工作，或者情绪上难以应对。帮助用户做力所能及的事即可。
不要将此Skill用作任务管理器。它关注的是模式，而非列出用户所有要做的事。
不要忽略用户对时段和环境的明确偏好。
不要忘记休息不是一种模式，而是合理状态。如果用户精力耗尽且无紧急截止日期，要直接告知。