aisdlc-project-discover-scope

Original：🇨🇳 Chinese

Translated

Use this when the Discover (reverse engineering) of legacy projects tends to get out of control in coverage. You need to first conduct module classification (P0/P1/P2) and constrain the depth of reverse engineering, ensuring that high-ROI modules are made traceable first instead of "writing everything but making it unmaintainable."

1installs

Sourcezixun-github/aisdlc

Added on2026-02-26

NPX Install

npx skill4agent add zixun-github/aisdlc aisdlc-project-discover-scope

SKILL.md Content (Chinese)

View Translation Comparison →

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

Overview

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 (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 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)

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

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

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)

"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