aisdlc-project-discover-scope

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

aisdlc-project-discover-scope（Step1：范围止损与模块分级）

aisdlc-project-discover-scope (Step 1: Scope Containment and Module Classification)

概览

Overview

Discover 的最大风险不是“写得不够”，而是“试图覆盖所有模块导致不可维护”。Scope 的任务是先把范围收敛，并对不同优先级规定最低交付深度。

开始时宣布：「我正在使用 aisdlc-project-discover-scope 技能对模块做 P0/P1/P2 分级并设置逆向深度门禁。」

The biggest risk of Discover is not "not writing enough," but "trying to cover all modules leading to unmaintainability." The task of Scope is to first converge the scope and define the minimum delivery depth for different priorities.

Announce at the start: "I am using the aisdlc-project-discover-scope skill to classify modules into P0/P1/P2 and set reverse engineering depth gates."

分级规则（建议）

Classification Rules (Recommendations)

P0（必须逆向）：高频变更、跨团队交界、对外集成多、事故热点、合规风险高
P1（建议逆向）：稳定但高频被引用/被问到/被依赖的基础能力
P2（按需逆向）：低风险、低协作、生命周期短；只保留索引占位与入口

P0 (Mandatory Reverse Engineering): High-frequency changes, cross-team boundaries, multiple external integrations, accident hotspots, high compliance risks
P1 (Recommended Reverse Engineering): Stable but frequently referenced/asked about/depended-on basic capabilities
P2 (Reverse Engineering On Demand): Low risk, low collaboration, short lifecycle; only keep index placeholders and entry points

深度门禁（强约束）

Depth Gates (Strict Constraints)

P0 必须同时具备

```
.aisdlc/project/components/{module}.md
```

.aisdlc/project/contracts/api/{module}.md

.aisdlc/project/contracts/data/{module}.md

证据入口（代码/测试/CI/ops）

P1 必须具备
- ```
.aisdlc/project/components/{module}.md
```
- 至少一个契约入口页（API 或 Data）
P2 只要求
- 在索引占位（
```
components/index.md
```
  ；如有 products 也占位）
- 保留入口链接即可（没有入口就写“未发现”）

P0 must have all of the following

```
.aisdlc/project/components/{module}.md
```

.aisdlc/project/contracts/api/{module}.md

.aisdlc/project/contracts/data/{module}.md

Evidence entry (code/test/CI/ops)

P1 must have
- ```
.aisdlc/project/components/{module}.md
```
- At least one contract entry page (API or Data)
P2 only requires
- Placeholder in the index (
```
components/index.md
```
  ; also placeholders if there are products)
- Just keep the entry link (write "Not found" if there's no entry)

Scope 输出怎么写（放到索引里）

How to Write the Scope Output (Put it in the Index)

在

.aisdlc/project/components/index.md

的表格里体现分级与进度（索引只导航，不写细节）：

module	priority	owner	code_entry	api_contract	data_contract	ops_entry	status
user	P0	TeamA	`path/...`	`contracts/api/user.md`	`contracts/data/user.md`	`ops/...`	- [ ]

status
用复选框：
- [ ]
未达标；
- [x]
达到对应优先级的 DoD。

Reflect the classification and progress in the table in

.aisdlc/project/components/index.md

(the index only provides navigation, no details):

module	priority	owner	code_entry	api_contract	data_contract	ops_entry	status
user	P0	TeamA	`path/...`	`contracts/api/user.md`	`contracts/data/user.md`	`ops/...`	- [ ]

Use checkboxes for
status
:
- [ ]
Not meeting the standard;
- [x]
Meeting the DoD for the corresponding priority.

常见错误

Common Mistakes

把 P0/P1/P2 当“写作优先级”：正确含义是“交付深度门禁不同”。
P0 只写组件页，不写契约入口页：这会导致后续对接/改动无法追溯“承诺边界”。
P2 也写成详尽模块页：范围会失控，维护失败。

Treating P0/P1/P2 as "writing priorities": The correct meaning is "different delivery depth gates."
Only writing component pages for P0, not contract entry pages: This will make subsequent docking/changes unable to trace the "commitment boundaries."
Writing detailed module pages for P2 as well: The scope will get out of control, leading to maintenance failure.

红旗清单（出现任一条：停止并纠正）

Red Flag List (Stop and correct if any of these occur)

“全模块都要写到字段级”或“先把细节写全”
还没完成 P0，就开始铺开 P1/P2 的细节
不能明确 P0 模块是谁/边界是什么，却已经开始写大量流程细节

"All modules need to be written down to the field level" or "Write all details first"
Starting to expand on P1/P2 details before completing P0
Unable to clarify who/what the boundaries of P0 modules are, but already starting to write a lot of process details