---

name: by-the-way description: Use when a user or Claude notices an interesting tangent, optional idea, rabbit hole, or follow-up topic that should continue in a separate chat without derailing the main thread. Trigger on requests like "顺便聊聊", "另开一个聊", "开个支线", "不要影响主线", "先记着", or when Claude should offer a self-contained side-thread prompt instead of expanding inline.

By The Way

Use this skill to split a promising tangent into a clean side thread. Keep the current thread moving. Do not answer the tangent in depth here unless the user clearly wants to abandon the mainline.

Decide Whether To Branch

Use this skill only when all of these are true:

• The tangent is interesting or potentially useful.
• It is not required to finish the current main task.
• Exploring it properly would cost more than a short aside.
• The user wants to protect the main thread, or Claude should proactively suggest that split.

Do not use this skill when:

• The tangent blocks the current task.
• A one- or two-sentence answer is enough.
• The user is clearly changing topics entirely rather than preserving the current thread.

Use this quick triage:

• answer inline: the tangent is cheap and does not meaningfully derail the current thread.
• branch now: the tangent deserves real exploration and the user wants to protect the main thread.
• park for later: the tangent is promising, but the user does not want to switch right now.

Offer The Split

If the user has not asked for a branch yet, surface the tangent in one short sentence.

Good shape:

• 这里有个值得单开的旁支，如果你要，我给你一个新聊天启动 prompt。
• 这个点展开会打断主线，要不要我给你一个支线 prompt 单开聊？

Do not start solving the tangent in the current thread while offering the split.

Produce A Branch Packet

Match the user's current language. Keep the packet compact and self-contained.

Always output these sections in this order:

支线标题

Give a short, concrete title.

为什么值得单开

State the payoff in one or two sentences.

新聊天启动 Prompt

Write a ready-to-paste prompt for the new chat. Include:

• the tangent itself
• the minimum relevant context from the current thread
• what to explore, decide, or produce
• any constraints worth preserving
• the preferred response style if obvious

主线恢复点

State:

• what the current thread was doing
• what should happen next here
• what result from the side thread would matter later, if any

Branching Rules

• Treat the new chat as blank context. Do not assume it has seen the current thread.
• Copy only the context that matters. Do not dump the full conversation.
• If Claude noticed the tangent first, frame it as a proposal, not a commitment.
• If the user says later, 先记着, or similar, make the prompt future-ready rather than urgent.
• If the tangent depends on an unverified assumption, label it as a hypothesis inside the new-chat prompt.
• Do not claim a new chat was opened unless the environment actually supports that action. Otherwise, return the prompt only.
• End by returning to the current thread in one sentence if the user still wants to continue the main task now.
• If the tangent is weak, say so and keep it inline instead of forcing a branch.
• If the tangent is good but underspecified, build the new-chat prompt around clarifying and scoping, not around fake certainty.

Default Response Shape

## 支线标题
...

## 为什么值得单开
...

## 新聊天启动 Prompt
...

## 主线恢复点
...

## 现在主线继续什么
...

The final section is required when the current thread should continue immediately. Keep it to one sentence.

Example Triggers

• 这个想法挺有意思，但别打断主线，另开一个聊。
• 顺便帮我把这个分成一个支线 prompt，我晚点单开。
• 你刚提的那个方向值得聊，但先不展开。