ask-matt

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Ask Matt

You don't remember every skill, so ask.

A flow is a path through the skills. Most paths run along one main flow, and two on-ramps merge onto it. Everything else is standalone.

你无需记住所有技能，直接提问即可。

flow（流程） 是贯穿各项技能的路径。大多数路径遵循一条主流程，另有两个接入流程可并入主流程。其余均为独立流程。

The main flow: idea → ship

主流程：想法 → 交付

The route most work travels. You have an idea and want it built.

/grill-with-docs
— sharpen the idea by interview. Start here when you have a codebase: it's stateful, retaining what it learns in
```
CONTEXT.md
```
and ADRs. (No codebase? Use
```
/grill-me
```
— see Standalone.)
Branch — can you settle every question in conversation? If a question needs a runnable answer (state, business logic, a UI you have to see), detour through a prototype, bridged by /handoff
in both directions (see Crossing sessions):
- /handoff
  out, then open a fresh session against that file,
- /prototype
  to answer the question with throwaway code,
- /handoff
  back what you learned, and reference it from the original idea thread.
Branch — is this a multi-session build?
- Yes → /to-prd
  (turn the thread into a PRD) → /to-issues
  (split the PRD into independently-grabbable issues). Because the issues are independent, clear context between each one: start a fresh session per issue and kick off /implement
  by passing it the PRD and the single issue to work on.
- No → /implement
  right here, in the same context window.

这是大多数工作遵循的路径。当你有一个想法并希望将其落地时适用。

/grill-with-docs
—— 通过访谈完善想法。当你已有代码库时从此处开始：它是有状态的，会将所获取的信息保存在
```
CONTEXT.md
```
和ADRs中。（没有代码库？使用
```
/grill-me
```
——详见独立流程部分。）
分支——能否通过对话解决所有问题？ 如果某个问题需要可运行的答案（状态、业务逻辑、需可视化的UI），则通过原型绕路，双向通过**
```
/handoff
```
**衔接（跨会话部分见下文）：
- 先执行**
```
/handoff
```
  **导出，然后针对该文件开启新会话，
- 执行**
```
/prototype
```
  **用临时代码解答问题，
- 再执行**
```
/handoff
```
  **带回所获信息，并在原想法线程中引用该信息。
分支——这是否是跨多会话的构建任务？
- 是 → 执行**
```
/to-prd
```
  （将线程转换为PRD）→ 执行
```
/to-issues
```
  （将PRD拆分为可独立处理的任务）。由于任务相互独立，每个任务间需明确上下文：针对每个任务开启新会话，传入PRD和单个任务来启动
```
/implement
```
  **。
- 否 → 直接在此处执行**
```
/implement
```
  **，保持同一上下文窗口。

Context hygiene

上下文维护

Keep steps 1–3 in one unbroken context window — don't compact or clear until after

/to-issues

— so the grilling, PRD, and issues all build on the same thinking. Each

/implement

then starts fresh, working from the issue.

The limit on this is the smart zone: the window (~120k tokens on state-of-the-art models) within which the model still reasons sharply. If a session approaches it before

/to-issues

, don't push on degraded —

/handoff

and continue in a fresh thread.

将步骤1-3保持在同一个连续的上下文窗口中——在执行

/to-issues

之前不要压缩或清空上下文，这样访谈、PRD和任务都能基于相同的思路构建。每个

/implement

都将从任务开始，开启新的上下文。

此方式的限制是**smart zone**：即模型仍能清晰推理的上下文窗口（在当前最先进的模型中约为120k tokens）。如果会话在执行

/to-issues

前接近该限制，不要在性能下降的情况下继续——执行

/handoff

并在新线程中继续。

On-ramps

接入流程

A starting situation that generates work, then merges onto the main flow.

Bugs and requests piling up → /triage
. It moves issues through triage roles and produces agent-ready issues, which /implement
later picks up.
Triage is only for issues you didn't create — bug reports, incoming feature requests, anything that arrives raw. Issues that
```
/to-issues
```
produced are already agent-ready, so don't triage them.

一种启动场景，生成工作任务后并入主流程。

Bug和请求堆积 → 执行**
```
/triage
```
。它会将任务按分类角色流转，并生成可由Agent处理的任务，供后续
```
/implement
```
**使用。
分类仅适用于你未创建的任务——Bug报告、外来功能请求、任何原始提交的任务。由
```
/to-issues
```
生成的任务已可由Agent处理，因此无需对其进行分类。

Codebase health

代码库健康维护

Not feature work — upkeep.

/improve-codebase-architecture
— run whenever you have a spare moment to keep the codebase good for agents to operate in. It surfaces deepening opportunities; picking one generates an idea you can take into the main flow at
```
/grill-with-docs
```
.

非功能开发工作——属于维护范畴。

/improve-codebase-architecture
—— 当你有空时运行此工具，以保持代码库适合Agent操作。它会挖掘优化机会；选择其中一个机会将生成一个想法，你可以在主流程的
```
/grill-with-docs
```
环节接入。

Crossing sessions

跨会话操作

/handoff
— when a thread is full or you need to branch off (e.g. into a
```
/prototype
```
session), this compacts the conversation into a markdown file. You don't continue in place — you open a new session and reference that file to carry the context across. It's the bridge between context windows, in either direction. Use it when you want a fresh session but need the current conversation preserved.
/compact
(built-in) — stay in the same conversation, letting the earlier turns be summarized. Use it at intentional breaks between phases, when you don't mind losing the verbatim history. Don't compact mid-phase — the agent can lose its way.
```
/handoff
```
forks;
```
/compact
```
continues.

/handoff
—— 当线程已满或你需要分支（例如进入
```
/prototype
```
会话）时，此工具会将对话压缩为markdown文件。你无需在此处继续——需开启新会话并引用该文件以传递上下文。它是上下文窗口之间的双向桥梁。当你需要新会话但又要保留当前对话内容时使用。
/compact
（内置工具）—— 继续在同一会话中，让早期对话内容被总结。在阶段间的有意断点处使用，此时你不介意丢失逐字记录的历史。不要在阶段中途压缩——Agent可能会迷失方向。
```
/handoff
```
是分支；
```
/compact
```
是继续。

Standalone

独立流程

Off the main flow entirely.

/grill-me
— the same relentless interview as
```
/grill-with-docs
```
, but for when you have no codebase. Stateless: it saves nothing locally, builds no
```
CONTEXT.md
```
. Reach for it to sharpen any plan or design that doesn't live in a repo.
/teach
— learn a concept over multiple sessions, using the current directory as a stateful workspace.
/writing-great-skills
— reference for writing and editing skills well.

完全脱离主流程。

/grill-me
—— 与
```
/grill-with-docs
```
的访谈流程相同，但适用于你没有代码库的情况。无状态：不会在本地保存任何内容，也不会生成
```
CONTEXT.md
```
。当你需要完善任何不在代码库中的计划或设计时使用。
/teach
—— 通过多会话学习某个概念，将当前目录作为有状态工作区。
/writing-great-skills
—— 编写和优化技能的参考指南。

Precondition

前置条件

/setup-matt-pocock-skills
— run before your first engineering flow to configure the issue tracker, triage labels, and doc layout the other skills assume. Custom issue trackers also work.

/setup-matt-pocock-skills
—— 在首次执行工程流程前运行此工具，以配置其他技能所需的任务跟踪器、分类标签和文档布局。自定义任务跟踪器也适用。