cut

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese
!
bash "${CLAUDE_SKILL_DIR}/../../hooks/yaml-helper.sh" resolve_config --keys automation
Resolved above — use as-is. No block → defaults in
.claude/docs/config-resolution.md
.
!
bash "${CLAUDE_SKILL_DIR}/../../hooks/yaml-helper.sh" resolve_config --keys automation
上面已完成解析——按原样使用。没有区块 → 使用
.claude/docs/config-resolution.md
中的默认值。

Cut

删减

Finishing a game is choosing what not to build. /cut reads what exists, proposes cuts with a reason taken from it, and keeps a polish list; the person picks every cut. For
sell
,
early_access
and
publisher
it asks a target date and proposes a freeze date. It writes the brief, the polish list and any cut story's Status line, and makes one commit.
It runs only when asked:
/cut
, or "what should I cut?", "how do I finish this?". It works on the game
design/game-brief.md
describes. A project with GDDs and no brief is
/scope-check
's.
Ask with the question tool. Without one, list the options numbered and end your turn to wait. The question is the last thing in the reply. A skipped or dismissed question is not an answer: ask again in plain text. Every ask follows
.claude/docs/automation-modes.md
: in
collaborative
and
guided
the cuts and the dates are asked, as scope changes are major decisions; in
autonomous
/cut writes the polish list only and leaves the proposals in its report: cuts and dates wait for the person, and nothing is committed.
完成一款游戏的关键,是决定哪些内容不去构建。/cut 会读取现有内容,基于现状提出删减建议并保留理由,同时维护一份打磨清单;每一项删减都由用户决定。对于
sell
、
early_access
和
publisher
,它会询问目标日期并建议冻结日期。它会写入 brief、打磨清单以及所有被删减 story 的 Status 行,并创建一次提交。
仅在用户明确要求时运行:
/cut
、“应该删减什么?”或“如何完成这款游戏?”。它处理
design/game-brief.md
所描述的游戏。如果项目有 GDD 但没有 brief,则应使用
/scope-check
。
使用 question 工具提问。如果没有该工具,则将选项编号列出,并以等待用户回复结束当前回合。问题必须是回复中的最后一项。跳过或关闭问题不算作回答:改用纯文本再次询问。每次询问都遵循
.claude/docs/automation-modes.md
:在
collaborative
和
guided
模式下,需要询问删减项和日期,因为范围变更属于重大决策;在
autonomous
模式下,/cut 只写入打磨清单,并将建议保留在报告中:删减项和日期仍需等待用户决定,且不会提交任何内容。

Phase 1: Read what exists

阶段 1:读取现有内容

Run
bash .claude/scripts/cut-read.sh
and keep its rows:
RowsUse
brief
,
title
The briefs written, both copies while they are the same text.
brief none
: say "/cut works from the brief's Features list, and there is no
design/game-brief.md
", name
/scope-check
when
design/gdd/
has files, and stop.
brief_differs
: the game's folder copy differs; only
design/game-brief.md
is written, said in one line
goal
,
dates
dates asked
or
not_asked
follows the goal.
goal - unset
(or
unknown
): guess it with
/start
's goal table (
.claude/skills/start/SKILL.md
, Phase 4) from the brief's In your words,
hobby
when nothing fits, and show it guessed
feature
,
keep
,
avoid
,
out
,
cut
The Features list by number, with its marks; the lists the proposals check
recorded
,
passed
Dates already on the brief's Dates line, and any date already past
game
,
record
,
open
A one-shot's last check record and its fails not marked deliberate
smoke
A project's smoke command, from the engine table, or
none
with why
feel
The feel log
polish
,
polish_row
The polish list's rows and ticks.
polish other_game
: it is another game's; say so and write no polish rows
story
,
stories_other
Stories traced to a Features item by number (
cut
: one already cut); a count of stories traced elsewhere, which /cut leaves alone (say so)
Read the brief itself too: its Question, Hooks, First minute, Challenge, Goal & fail state and Build order give the reasons.
  • Fresh first: a
    record ... stale
    row means the game changed after its check record. A changed game gets the light check, never the small check again: the small check is the build's, and
    one-shot-check.sh --record
    records only that, so never run it here. First see whether a light check is newer than every game file. For each marker on disk,
    evidence/changes.tsv
    (a change's light check) and
    evidence/cut-end.png
    (an earlier /cut's), run
    find prototypes/<name> -type f -newer prototypes/<name>/evidence/<marker> ! -path '*/evidence/*' ! -path '*/dist/*' ! -name brief.md ! -name feel-log.md ! -name polish-list.md
    .
    • One prints nothing: that light check is fresh, so run nothing. Errors and a bot stop on
      changes.tsv
      's last line that the polish list lacks become rows.
    • Otherwise, run the light check once, as
      .claude/skills/prototype/references/one-shot-4-change.md
      section 7 does before accept: its step 1 (keep) and step 2 (play it once), the shot
      prototypes/<name>/evidence/cut-end.png
      . A
      not_assessed
      row: say "not checked: <why>" in one line. Fix nothing: each error, bot stop and
      changed
      or
      gone
      keep row becomes a polish row.
    These rows end
    · from: light check of <date>
    . The stale
    record
    row stays; its
    open
    rows still count.
  • A project:
    smoke <command>
    : run
    timeout 900 <command>
    once, as it is: no pipe, redirect or second command (the permission is for that command alone). A failure is a polish row (
    from: smoke run of <date>
    ); a pass adds none.
    record none
    with no smoke command to run: say in one line that the polish rows come from the feel log and the person.
运行
bash .claude/scripts/cut-read.sh
并保留其中的行:
行用途
brief
、
title
已写入的 brief;两份副本内容相同时都要读取。
brief none
:说明“/cut 根据 brief 的 Features 列表工作,但不存在
design/game-brief.md
”;如果
design/gdd/
中有文件,则同时提及
/scope-check
,然后停止。
brief_differs
:游戏文件夹中的副本与主 brief 不同;只写入
design/game-brief.md
,并用一行说明
goal
、
dates
dates asked
或
not_asked
取决于目标。
goal - unset
(或
unknown
):使用
.claude/skills/start/SKILL.md
阶段 4 中
/start
的目标表,根据 brief 的 In your words 章节推测目标;如果都不匹配,则使用
hobby
,并明确显示这是推测值
feature
、
keep
、
avoid
、
out
、
cut
按编号列出 Features 列表及其标记;用于核对各项建议的列表
recorded
、
passed
brief 的 Dates 行中已经记录的日期,以及任何已经过去的日期
game
、
record
、
open
一次性检查的最近记录,以及其中未被标记为有意保留的失败项
smoke
项目的 smoke 命令及对应的引擎表格;如果没有,则为
none
并附上原因
feel
feel 日志
polish
、
polish_row
打磨清单中的行及勾选状态。
polish other_game
:这是另一款游戏的清单;说明这一点,并且不写入任何打磨行
story
、
stories_other
按编号追踪到 Features 项的 story(
cut
:表示已经删减);追踪到其他位置的 story 数量,/cut 不会处理这些 story(需要说明)
还要读取 brief 本身:其中的 Question、Hooks、First minute、Challenge、Goal & fail state 和 Build order 提供了各项建议的理由。
  • 先判断新鲜度:
    record ... stale
    行表示游戏在检查记录之后发生过变化。发生变化的游戏需要执行 light check,绝不能再次执行 small check:small check 属于构建阶段,而且
    one-shot-check.sh --record
    只记录该检查,因此绝不能在这里运行。首先确认 light check 是否比所有游戏文件都新。对于磁盘上的每个标记——
    evidence/changes.tsv
    (变更后的 light check)和
    evidence/cut-end.png
    (之前执行 /cut 时留下的标记)——运行
    find prototypes/<name> -type f -newer prototypes/<name>/evidence/<marker> ! -path '*/evidence/*' ! -path '*/dist/*' ! -name brief.md ! -name feel-log.md ! -name polish-list.md
    。
    • 如果某次查找没有输出: 说明对应的 light check 仍是最新状态,因此不运行任何检查。错误,以及
      changes.tsv
      最后一行中打磨清单尚未包含的 bot stop,都会成为打磨清单中的行。
    • 否则, 按照
      .claude/skills/prototype/references/one-shot-4-change.md
      第 7 节在 accept 之前的方式,运行一次 light check:执行其步骤 1(keep)和步骤 2(实际游玩一次),并截取
      prototypes/<name>/evidence/cut-end.png
      。对于
      not_assessed
      行:用一行说明“未检查:<原因>”。不要修复任何问题:每个错误、bot stop,以及
      changed
      或
      gone
      类型的 keep 行都会成为打磨清单中的一行。
    这些行以
    · from: light check of <date>
    结尾。处于过期状态的
    record
    行会保留;其中的
    open
    行仍然计数。
  • 对于项目: 如果存在
    smoke <command>
    ,则原样运行一次
    timeout 900 <command>
    :不使用管道、重定向或第二条命令(权限仅适用于该条命令)。如果失败,则添加一条打磨记录(
    from: smoke run of <date>
    );如果通过,则不添加记录。如果为
    record none
    且没有可运行的 smoke 命令:用一行说明打磨记录来自 feel 日志以及用户提供的信息。

Phase 2: Propose

阶段 2:提出建议

Cuts, in this order, each with a reason from what exists:
  1. A
    not_yet
    item that Out of scope or Avoid already rules out.
  2. A
    built
    item whose check fails (
    open
    ), offered as cut it or polish it.
  3. A
    not_yet
    item that no Question, Hook, First minute, Challenge, Goal & fail state or Keep line names.
For a selling goal, every
not_yet
item left also shows "build it before <freeze date>, or cut it". Never propose an item a Keep line names. The person can still name any item.
Marks brought up to date: a
not_yet
item whose
story
row is Complete is shown built and marked
[x]
with the other writes.
Polish rows come from what exists, never invented: each
open
row, each smoke failure, and what the person adds. Each row ends
· from: <source>
:
<check> check of <date>
,
smoke run of <date>
or
you said
. The person's rows and ticks stay; a row whose source now passes is ticked, said in one line. Rows about a cut item go with the cut.
删减项按以下顺序排列,每项都给出基于现有内容的理由:
  1. 已经被 Out of scope 或 Avoid 排除的
    not_yet
    项。
  2. 检查失败(
    open
    )的
    built
    项,提供“删减”或“打磨”两个选择。
  3. Question、Hook、First minute、Challenge、Goal & fail state 或 Keep 行均未提及的
    not_yet
    项。
对于销售目标,每个剩余的
not_yet
项还要显示“在 <freeze date> 前构建,或删减它”。绝不提出任何由 Keep 行指定的项。 用户仍然可以主动指定任意项。
更新标记: 如果某个
not_yet
项对应的
story
行已经 Complete,则将其显示为已构建,并随其他写入一起标记为
[x]
。
打磨记录必须来自现有内容,绝不能凭空创建:包括每个
open
行、每次 smoke 失败,以及用户提供的内容。每行以
· from: <source>
结尾:
<check> check of <date>
、
smoke run of <date>
或
you said
。用户提供的记录和勾选状态会保留;如果某行的来源现在已通过检查,则将其勾选,并用一行说明。与被删减项有关的记录应随该项一起处理。

Phase 3: Dates, for sell, early_access and publisher only

阶段 3:日期,仅适用于 sell、early_access 和 publisher

Any other goal gets no date, asked or shown.
  • Recorded dates are shown, not asked again ("move the dates" changes them). A
    passed freeze
    row is said in one line; a
    passed target
    row is asked again.
  • Target: ask in plain words named for the goal: when to release it (
    sell
    ), when the Early Access launch is (
    early_access
    ), when the pitch or demo is (
    publisher
    ). Turn a month or "next spring" into a date and show it.
  • Freeze: run
    bash .claude/scripts/cut-read.sh --target <date>
    ; its
    proposed freeze
    row is 70% of the way from today to the target. Ask "Freeze on <date>?" Options:
    Freeze then
    /
    Another date
    . Say what it means: from then on no new features, only the polish list and fixes; recorded, and nothing holds you to it yet.
    target_past
    : ask the target again.
  • A goal changed on the screen ("I want to sell it") is written at once with
    bash .claude/scripts/config-set.sh project.goal <value>
    , and its dates are asked. A guessed goal left as it is is not written. No other
    project.yaml
    key is touched.
其他任何目标都不设置、不询问也不显示日期。
  • 已记录的日期只显示,不再次询问(“move the dates”会修改这些日期)。对于
    passed freeze
    行,用一行说明;对于
    passed target
    行,再次询问。
  • 目标日期: 根据目标,用日常措辞询问:何时发布(
    sell
    )、何时启动 Early Access(
    early_access
    ),或何时进行推介或演示(
    publisher
    )。如果用户提供月份或“明年春天”之类的表达,将其换算为具体日期并显示出来。
  • 冻结日期: 运行
    bash .claude/scripts/cut-read.sh --target <date>
    ;其中的
    proposed freeze
    行是从今天到目标日期之间 70% 的位置。询问“在 <date> 冻结?”选项:
    Freeze then
    /
    Another date
    。说明其含义:从该日期起不再增加新功能,只处理打磨清单和修复事项;日期会被记录,但目前不会强制执行。
    target_past
    :再次询问目标日期。
  • 如果用户在界面上更改目标(“I want to sell it”),立即运行
    bash .claude/scripts/config-set.sh project.goal <value>
    写入目标,并询问对应日期。如果只是推测目标且用户未作更改,则不写入。除
    project.goal
    外,不修改其他
    project.yaml
    键。

Phase 4: The screen and the pick

阶段 4:屏幕输出与选择

text
/cut · <title> · Goal: <goal> (set | guessed)
Cut? You pick; nothing is cut without your pick.
  1. [ ] <item>
     · <reason>
Staying: <n> built features · Never offered: your <n> Keep lines
Polish: <n> rows, from <the sources>
Dates: target <date> (<what>) · freeze <date>
Writes: <the briefs>, <the polish list>, <each story> · one commit
Leave out the Dates line for a goal that gets none, and Cut? when there is nothing to propose. Every file is named on the Writes line before writing, and nothing is written before the pick. Then ask with the question tool, multi-select, up to four proposals ("Cut which? Pick none to cut nothing"); more are numbered in text and picked by number. The reason is the person's words if they gave any, else the proposal's. With dates to ask, ask the target in the same call, then the freeze as Phase 3 says.
text
/cut · <title> · Goal: <goal> (set | guessed)
Cut? You pick; nothing is cut without your pick.
  1. [ ] <item>
     · <reason>
Staying: <n> built features · Never offered: your <n> Keep lines
Polish: <n> rows, from <the sources>
Dates: target <date> (<what>) · freeze <date>
Writes: <the briefs>, <the polish list>, <each story> · one commit
对于不需要日期的目标,省略 Dates 行;如果没有可提出的内容,则省略 Cut?。写入任何文件之前,必须先在 Writes 行中列出所有相关文件,并且必须等到用户作出选择后才能写入。
然后使用 question 工具提问,采用多选,最多显示四个建议(“Cut which? Pick none to cut nothing”);如果建议更多,则在文本中编号,由用户按编号选择。如果用户提供了理由,则使用用户的原话,否则使用建议自身的理由。需要询问日期时,在同一次调用中先询问目标日期,再按照阶段 3 的方式询问冻结日期。

Phase 5: Write and commit

阶段 5:写入并提交

Run
bash .claude/scripts/cut-apply.sh
with
--brief <path>
for each
brief
row and:
  • --cut <n> "<reason>"
    for each picked item: it leaves Features for the end of Out of scope as
    - [-] <item> · cut: <reason> (<date>)
    , plus
     · was built
    when it was
    [x]
    ; its story's Status becomes
    Blocked — BLOCKED: cut by /cut <date>: <reason>
    , a status
    /dev-story
    stops on (a Complete story keeps its status:
    story moved
    ).
  • --mark <n>
    for each mark brought up to date.
  • --dates <target> <freeze> "<what>"
    when dates were given.
  • --polish "<row>"
    ,
    --tick "<row>"
    and
    --drop "<row>"
    for the polish list.
Moving an item renumbers the Features after it, so the stories traced to them are renumbered too (
story renumbered
); the Writes line names every story a proposed cut can touch.
bad
rows mean nothing was written: fix the arguments and run it again. A cut built item stays in the game until it is taken out, an ordinary change: say "say 'take out <item>' to remove it".
Commit when
git rev-parse --is-inside-work-tree
succeeds, the pick being the commit instruction:
git add <each wrote path, design/ ones first>
, then
git commit -m "docs: cut <items> · dates · polish list (<n> rows)" -m "Brief: design/game-brief.md" -- <the same paths>
. Leave out
cut <items> · 
when nothing was cut, and
dates · 
when the Dates line did not change. No git: "Not committed: this project has no git." Say in one line what was written.
Next step: build what is left before the freeze (
/create-stories
writes a story for each not-yet item in a project), and work down the polish list.
运行
bash .claude/scripts/cut-apply.sh
,为每个
brief
行传入
--brief <path>
,并根据需要加入:
  • 对每个选中的项传入
    --cut <n> "<reason>"
    :它会在
    Out of scope
    末尾的
    Features
    中留下
    - [-] <item> · cut: <reason> (<date>)
    ;如果该项原本为
    [x]
    ,还会附带
     · was built
    。其 story 的 Status 会变为
    Blocked — BLOCKED: cut by /cut <date>: <reason>
    ,这是
    /dev-story
    遇到后会停止处理的状态(处于 Complete 状态的 story 保持其状态:
    story moved
    )。
  • 对每个需要更新的标记传入
    --mark <n>
    。
  • 提供日期时传入
    --dates <target> <freeze> "<what>"
    。
  • 打磨清单使用
    --polish "<row>"
    、
    --tick "<row>"
    和
    --drop "<row>"
    。
移动某一项后,其后的 Features 项会重新编号,因此追踪到这些项的 story 也会重新编号(
story renumbered
);Writes 行必须列出每项建议删减可能影响的 story。出现
bad
行表示没有写入任何内容:修正参数后再次运行。已构建项被标记为删减后,在真正移除之前仍会保留在游戏中;这是一项普通操作:提示用户“say 'take out <item>' to remove it”。
当
git rev-parse --is-inside-work-tree
成功时进行提交,用户的此次选择即视为提交指令:先运行
git add <each wrote path, design/ ones first>
,然后运行
git commit -m "docs: cut <items> · dates ·\npolish list (<n> rows)" -m "Brief: design/game-brief.md" -- <the same paths>
。没有删减任何内容时,省略
cut <items> · 
;Dates 行未发生变化时,省略
dates · 
。如果没有 git,则提示“未提交:此项目没有 git。”最后用一行说明写入了哪些内容。
下一步:在冻结日期之前构建剩余内容(
/create-stories
会为项目中的每个未完成项编写 story),然后逐项处理打磨清单。

Afterwards

后续操作

  • "Bring back <item>":
    cut-apply.sh --back "<item>" built|not_yet
    moves the line back to Features:
    built
    while it is still in the game. Its story goes back to Ready. Commit the
    wrote
    paths as
    docs: bring back <item>
    .
  • "Move the dates": Phase 3 again, with the recorded dates shown, then write and commit as Phase 5 does.
  • Nothing blocks or warns on the freeze date in this version: only /cut reads it back.
  • “Bring back <item>”:
    cut-apply.sh --back "<item>" built|not_yet
    会将该行移回 Features:如果它仍在游戏中,则恢复为
    built
    ;其 story 会恢复为 Ready。将
    wrote
    路径提交,提交信息为
    docs: bring back <item>
    。
  • “Move the dates”: 再次执行阶段 3,并显示已记录的日期,然后按照阶段 5 的方式写入并提交。
  • 此版本不会因冻结日期而阻止或警告任何操作:只有 /cut 会读取该日期。