specture

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Specture System

Specture is a spec-driven development system. Durable design records live in

SPEC.md

files under the

specs/

tree. Disposable agent handoffs live in optional

PLAN.md

files beside or beneath specs.

Use the CLI for deterministic file creation, querying, and validation. Use this skill for workflow decisions and file edits.

Specture是一套规范驱动开发系统。持久化的设计记录存储在

specs/

目录下的

SPEC.md

文件中。一次性的Agent交接信息存储在规范文件旁或下方的可选

PLAN.md

文件中。

使用CLI进行确定性的文件创建、查询和验证。使用本技能进行工作流决策和文件编辑。

Start Here

入门指南

Designing or refining a spec: read references/design-workflow.md.
Splitting an existing spec into parent and child specs: read references/split-workflow.md.
Implementing a spec: read references/implementation-workflow.md before changing code, and include any relevant
```
PLAN.md
```
as execution context.
Validating spec or plan edits: read references/validation-workflow.md.
Bootstrapping or migrating a specs tree: read references/migration-workflow.md.
Creating or editing a
```
SPEC.md
```
: read references/spec-format.md.
Creating or editing a
```
PLAN.md
```
: read references/plan-format.md.
Configuring tracked spec files: read references/specs-gitignore-format.md.

设计或优化规范：阅读references/design-workflow.md。
将现有规范拆分为父规范和子规范：阅读references/split-workflow.md。
实现规范：在修改代码前阅读references/implementation-workflow.md，并将相关的
```
PLAN.md
```
作为执行上下文。
验证规范或计划编辑：阅读references/validation-workflow.md。
初始化或迁移规范目录树：阅读references/migration-workflow.md。
创建或编辑
```
SPEC.md
```
：阅读references/spec-format.md。
创建或编辑
```
PLAN.md
```
：阅读references/plan-format.md。
配置跟踪的规范文件：阅读references/specs-gitignore-format.md。

Core Rules

核心规则

Use
```
specture list
```
to find specs; do not manually scan the specs tree when the CLI can answer the question.
Use
```
specture list --assignee "Name"
```
to find specs assigned to a person. Pass comma-separated complete names to query several assignees; matching is case-insensitive.
Read the relevant
```
SPEC.md
```
before implementation work.
Before implementing any spec, read
```
references/implementation-workflow.md
```
; do not treat a
```
PLAN.md
```
alone as sufficient workflow guidance.
During implementation, commit each focused, verified chunk before starting the next chunk.
Do not batch multiple planned PR chunks into one uncommitted working tree unless the user explicitly asks.
Keep implementation progress out of
```
SPEC.md
```
; use
```
PLAN.md
```
for execution handoffs and task breakdowns.
Add only design content the user explicitly discussed or confirmed; do not invent missing goals, requirements, or decisions.
When the user asks to split an existing spec, established content from that spec may be redistributed into child specs without reconfirmation; follow
```
references/split-workflow.md
```
.
Never infer child boundaries when splitting a spec; discuss the proposed children with the user and get explicit confirmation before creating them.
Parent specs contain a simple description, goals, and linked child-spec index; design decisions belong in child specs.
Do not edit spec design decisions or descriptions without explicit user permission.
Use plain-language markdown headings; do not number headings.
Cross-spec mentions must use inline repo-root-relative markdown links to the target
```
SPEC.md
```
.
Run
```
specture validate
```
after spec migrations or edits to
```
SPEC.md
```
/
```
PLAN.md
```
files.

使用
```
specture list
```
查找规范；当CLI可以回答问题时，不要手动扫描规范目录树。
使用
```
specture list --assignee "Name"
```
查找分配给特定人员的规范。传入逗号分隔的完整姓名可查询多位负责人；匹配不区分大小写。
在开始实现工作前阅读对应的
```
SPEC.md
```
。
在实现任何规范前，阅读
```
references/implementation-workflow.md
```
；不要仅将
```
PLAN.md
```
视为足够的工作流指导。
实现过程中，在开始下一个任务块前，提交每个已完成并验证的任务块。
除非用户明确要求，否则不要将多个计划好的PR任务块批量放入未提交的工作区。
不要将实现进度写入
```
SPEC.md
```
；使用
```
PLAN.md
```
进行执行交接和任务分解。
仅添加用户明确讨论或确认的设计内容；不要自行补充缺失的目标、需求或决策。
当用户要求拆分现有规范时，该规范中的既定内容可无需重新确认即可重新分配到子规范中；遵循
```
references/split-workflow.md
```
。
拆分规范时，不要自行推断子规范的边界；需与用户讨论拟议的子规范并获得明确确认后再创建。
父规范包含简单描述、目标和子规范索引链接；设计决策应放在子规范中。
未经用户明确许可，不要编辑规范的设计决策或描述。
使用通俗易懂的Markdown标题；不要对标题编号。
跨规范引用必须使用指向目标
```
SPEC.md
```
的相对仓库根目录的Markdown内联链接。
在规范迁移或编辑
```
SPEC.md
```
/
```
PLAN.md
```
文件后，运行
```
specture validate
```
。

CLI Quick Reference

CLI快速参考

bash

specture list
specture list -p 1.4
specture list -p 1.4 -d 1
specture list -d all
specture list --status draft,approved
specture list --assignee "Alice Example"
specture list --assignee "Alice Example,Bob Builder"
specture list -f json
specture validate
specture validate --spec 11
specture new --title "Feature name"
specture new --title "Child feature" --parent 11

```
specture list -p/--parent
```
scopes output to a parent spec's children.
```
specture list -d/--depth
```
controls recursion depth. The default is
```
all
```
(full tree). Use
```
-d 1
```
for immediate children only, or
```
-d 0
```
/
```
-d all
```
for unlimited depth.
```
specture list --assignee
```
matches complete assignee names case-insensitively after trimming whitespace; it does not perform partial-name matching. Combine it with
```
--status all
```
when completed assignments must be included.
Text output shows
```
ASSIGNEE
```
only when at least one displayed spec is assigned. JSON output always includes an
```
assignee
```
string, using
```
""
```
for unassigned specs.
```
specture new --parent
```
creates the next child spec under a parent. It does not have a short
```
-p
```
flag.

When you need to discover Specture behavior or available flags, run

specture help

or command-specific

--help

first. Do not fall back to raw shell directory listing such as

ls specs/

until the CLI cannot answer the question.

bash

specture list
specture list -p 1.4
specture list -p 1.4 -d 1
specture list -d all
specture list --status draft,approved
specture list --assignee "Alice Example"
specture list --assignee "Alice Example,Bob Builder"
specture list -f json
specture validate
specture validate --spec 11
specture new --title "Feature name"
specture new --title "Child feature" --parent 11

```
specture list -p/--parent
```
将输出范围限定为父规范的子规范。
```
specture list -d/--depth
```
控制递归深度。默认值为
```
all
```
（完整目录树）。使用
```
-d 1
```
仅显示直接子规范，或使用
```
-d 0
```
/
```
-d all
```
显示所有层级。
```
specture list --assignee
```
会在去除空格后不区分大小写匹配完整负责人姓名；不支持部分姓名匹配。当需要包含已完成的分配任务时，需结合
```
--status all
```
使用。
文本输出仅在至少有一个显示的规范被分配时才会展示
```
ASSIGNEE
```
字段。JSON输出始终包含
```
assignee
```
字符串，未分配的规范该字段值为
```
""
```
。
```
specture new --parent
```
会在指定父规范下创建下一个子规范。该参数没有短标识
```
-p
```
。

当你需要了解Specture的行为或可用标识时，请先运行

specture help

或特定命令的

--help

。只有当CLI无法回答问题时，才使用原始Shell目录列表（如

ls specs/

）。