office-hours

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

/cs:office-hours — Six-Question Founder Interrogation

/cs:office-hours — 创始人六问质询

Command:

/cs:office-hours <topic>

Before any advice, the founder must answer six questions. Modeled on YC office hours: no analysis until the founder has done the thinking. This is the cognitive forcing function that prevents drift into solutionism.

命令：

/cs:office-hours <主题>

在给出任何建议前，创始人必须先回答六个问题。该模式借鉴YC办公时间的思路：在创始人完成独立思考前，不做任何分析。这是一种认知强制机制，避免陷入“解决方案先行”的误区。

When to Run

适用场景

Before starting any major initiative
Before fundraising
Before a strategic pivot
When the founder is excited (excitement is a tell — pressure-test)
When the answer is "obvious" (the obvious answer is usually wrong)

启动任何重大项目之前
融资之前
战略转型之前
创始人情绪亢奋时（亢奋是信号——需压力测试）
当答案看似“显而易见”时（显而易见的答案通常是错误的）

The Six Questions

六个核心问题

The founder must answer all six in writing before any C-role weighs in.

创始人必须以书面形式回答全部六个问题，之后管理层才能介入讨论。

1. Problem

1. 问题本质

Whose problem is this, and how do they describe it in their own words?

Not your framing. Their words.
If you can't quote a customer, you don't have a problem worth solving.

这是谁的问题？他们自己是如何描述这个问题的？

不要用你的视角，要用客户的原话。
如果你无法引用客户的真实表述，说明这个问题不值得解决。

2. Customer

2. 目标客户

Who is the ICP? Name one real person who would buy this today.

Real human. Real company. Real seat.
If you can't name one, the ICP isn't ready.

谁是ICP？说出一位当下会购买产品的真实用户。

真实的个人、真实的公司、真实的岗位。
如果你无法说出具体的人，说明ICP还未明确。

3. Distribution

3. 获客渠道

How does the customer first hear your name?

Channel, intent, search query, friend, conference — name it.
If the answer is "we'll figure out marketing later," the answer is no.

客户最初是通过什么途径了解到你的？

具体渠道：意向场景、搜索关键词、朋友推荐、行业会议等——请明确说明。
如果答案是“我们之后再考虑营销”，则该方案不予通过。

4. Defensibility

4. 护城河

If this works, what stops a competitor from copying it in 6 months?

Network effects, switching costs, data moat, regulatory moat, brand — pick one.
"We'll execute better" is not a defense.

如果项目成功，是什么阻止竞争对手在6个月内复制你的模式？

可选方向：网络效应、转换成本、数据壁垒、监管壁垒、品牌优势——选其一。
“我们执行力更强”不构成护城河。

5. Capital

5. 资金规划

What does this cost, when does it pay back, and what's the alternative use of the money?

Total spend, payback months, opportunity cost.
If you don't know, don't approve it.

项目成本是多少？何时回本？这笔资金的其他用途是什么？

需明确总支出、回本周期、机会成本。
若无法明确，则不予批准。

6. Founder Fit

6. 创始人适配性

Why are you the right person to do this — and why does this matter enough to spend the next 3 years on it?

Founder-market fit is the strongest predictor of survival.
If the answer is mercenary, the company will be too.

为什么你是做这件事的合适人选？这件事值得你投入未来3年的时间的原因是什么？

创始人-市场适配度是企业存活的最强预测指标。
如果答案带有功利性，公司也会变得功利。

Output Format

输出格式

After the founder answers all six, this command produces a one-page brief:

markdown

undefined

创始人回答完所有问题后，该命令会生成一份单页简报：

markdown

undefined

Office Hours Brief: <topic>

办公时间简报：<主题>

Date: YYYY-MM-DD Founder: <name>

日期： YYYY-MM-DD 创始人： <姓名>

1. Problem

1. 问题本质

[founder's verbatim answer]

[创始人的原话回答]

2. Customer

2. 目标客户

[founder's verbatim answer]

[创始人的原话回答]

3. Distribution

3. 获客渠道

[founder's verbatim answer]

[创始人的原话回答]

4. Defensibility

4. 护城河

[founder's verbatim answer]

[创始人的原话回答]

5. Capital

5. 资金规划

[founder's verbatim answer]

[创始人的原话回答]

6. Founder Fit

6. 创始人适配性

[founder's verbatim answer]

Assessment (one of):

🟢 GREEN — ship the brief to /cs:boardroom
🟡 YELLOW — sharpen Q[N] before proceeding
🔴 RED — kill or redefine; do not proceed

undefined

[创始人的原话回答]

评估结果（三选一）：

🟢 绿色 — 将简报提交至 /cs:boardroom
🟡 黄色 — 完善第[N]个问题后再推进
🔴 红色 — 终止或重新定义项目；不得推进

undefined

Routing

流程路由

After the brief is GREEN, route to:

Single-role question → corresponding
```
/cs:{role}-review
```
Multi-role question →
```
/cs:brief
```
then
```
/cs:boardroom
```

当简报评估为绿色后，按以下路径推进：

单一角色决策问题 → 对应
```
/cs:{role}-review
```
命令
多角色决策问题 → 先执行
```
/cs:brief
```
再提交至
```
/cs:boardroom
```

Why This Works

设计原理

Most bad decisions don't fail at execution — they fail at framing. Forcing six concrete answers surfaces the framing weaknesses before anyone burns time on analysis. The founder either fills the gaps or recognizes the question wasn't ready.

This is the YC

office hours

pattern adapted for Claude Code: the interrogation is the value.

大多数错误决策并非败在执行层面，而是败在框架设计阶段。通过强制要求六个具体答案，能在投入时间分析前暴露框架缺陷。创始人要么填补认知缺口，要么意识到项目尚未准备就绪。

这是适配Claude Code的YC

office hours

模式：质询本身就是核心价值。

office-hours

Original

Translation

/cs:office-hours — Six-Question Founder Interrogation

/cs:office-hours — 创始人六问质询

When to Run

适用场景

The Six Questions

六个核心问题

1. Problem

1. 问题本质

2. Customer

2. 目标客户

3. Distribution

3. 获客渠道

4. Defensibility

4. 护城河

5. Capital

5. 资金规划

6. Founder Fit

6. 创始人适配性

Output Format

输出格式

Office Hours Brief: <topic>

办公时间简报：<主题>

1. Problem

1. 问题本质

2. Customer

2. 目标客户

3. Distribution

3. 获客渠道

4. Defensibility

4. 护城河

5. Capital

5. 资金规划

6. Founder Fit

6. 创始人适配性

Routing

流程路由

Why This Works

设计原理

Related Commands

相关命令

Related Agents

相关Agent