Back to Details

ask

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese
<!-- markdownlint-disable MD013 -->
<!-- markdownlint-disable MD013 -->

Ask

询问

You don't remember every skill, so ask. A router over the workflow catalog.
你不可能记住所有skill，所以直接询问即可。这是一个工作流目录的导航工具。

First time in a repo

首次进入仓库时

bootstrap
 — run once before anything else. Discovers the tracker, labels, and docs layout and writes 
docs/agents/*
. If 
to-spec
, 
to-tickets
, or 
triage
start guessing where issues live, this hasn't been run yet.
bootstrap
 —— 在进行任何操作前先运行一次。它会识别追踪器、标签和文档布局，并生成
docs/agents/*
文件。如果
to-spec
、
to-tickets
或
triage
开始猜测问题所在位置，说明还未运行过此命令。

The main flow: idea → ship

主流程：想法 → 交付

The route most work travels:
  1. Sharpen the idea in conversation against the codebase — terminology into 
    CONTEXT.md
    , decisions into ADRs (
    docs/adr/
    ).
  2. to-spec
     — turn the thread into a spec and publish it as a GitHub issue (the validation gate). Set its milestone, assignee, and project at creation; label it 
    ready-for-human
    — a human approves direction before any code.
  3. Multi-session build? 
    to-tickets
     — split the spec into tracer-bullet tickets with blocking edges. Single-session? Skip to step 5.
  4. triage
     — move issues through the state machine as work is evaluated.
  5. implement
     — build a 
    ready-for-agent
    ticket: TDD at the seams, on the minimalism ladder, closing with 
    code-review
    , then commit.
大多数工作遵循的流程：
  1. 打磨想法：结合代码库进行讨论——将术语整理到
    CONTEXT.md
    中，将决策记录到ADR（
    docs/adr/
    ）中。
  2. to-spec
     —— 将讨论内容转化为规范，并作为GitHub issue发布（这是验证关卡）。创建时设置里程碑、负责人和项目；为其添加
    ready-for-human
    标签——在编写任何代码前，需由人工批准方向。
  3. 需要多阶段构建？
    to-tickets
     —— 将规范拆分为带有依赖关系的追踪式任务单。单阶段构建？直接跳到第5步。
  4. triage
     —— 随着工作推进，将issues在状态机中流转。
  5. implement
     —— 完成
    ready-for-agent
    任务单：在接口处采用TDD，遵循极简原则，完成后进行
    code-review
    ，然后提交代码。

Pick by intent

根据意图选择

You want to...Reach for
Set this repo up for the workflow
bootstrap
Turn a discussion into a validated feature
to-spec
Break a spec into buildable tickets
to-tickets
Sort / label / brief issues
triage
Build a spec or ticket
implement
Plan / cut a release from a milestonerelease management (
docs/agents/workflow.md
)
Review a branch/PR (Standards + Spec + Stability)
code-review
Add stability/invariant tests over generated dataproperty-based (in 
implement
)
Find what to delete / is this over-engineeredminimalism audit (
docs/agents/workflow.md
)
See the shortcuts we deferreddeferral ledger (
docs/agents/workflow.md
)
Simplest-solution discipline on any coding taskminimalism ladder (always on)
你想要...选择...
为仓库配置此工作流
bootstrap
将讨论转化为经过验证的功能
to-spec
将规范拆分为可执行的任务单
to-tickets
整理/标记/梳理issues
triage
实现规范或任务单
implement
基于里程碑规划/发布版本发布管理（
docs/agents/workflow.md
）
审查分支/PR（标准+规范+稳定性）
code-review
为生成的数据添加稳定性/不变量测试属性测试（在
implement
中）
查找可删除内容 / 判断是否过度设计极简性审计（
docs/agents/workflow.md
）
查看已推迟的快捷方式推迟记录（
docs/agents/workflow.md
）
在任何编码任务中遵循最简解决方案原则极简阶梯（始终启用）

Context hygiene

上下文维护

Keep steps 1–2 in one unbroken context window. When splitting into tickets, clear context between implementing each one — a fresh window per ticket.
将步骤1–2放在同一个连续的上下文窗口中。拆分任务单时，在实现每个任务单之间清空上下文——每个任务单使用一个新窗口。