SuperAPI AI Directory

aisdlc-project-discover-scope

Coding & development

View repository

Updated 10-16 08:50

About this skill

aisdlc-project-discover-scope (Step 1: Scope stop-loss and module classification)

Overview

The biggest risk of Discover is not "not writing enough," but "trying to cover all modules, which leads to unmaintainability." Scope's task is to first make the scopeconverge, and to specify for different priorities theminimum delivery depth。

At the beginning, announce:"I am using the aisdlc-project-discover-scope skill to classify modules as P0/P1/P2 and set reverse-engineering depth gates."

Classification rules (recommended)

  • P0 (must reverse engineer): high-frequency changes, cross-team boundaries, many external integrations, incident hotspots, high compliance risk
  • P1 (recommended to reverse engineer): stable but frequently referenced/asked about/depended-on foundational capabilities
  • P2 (reverse engineer as needed): low risk, low collaboration, short lifecycle; keep only index placeholders and entry points

Depth gates (hard constraints)

  • P0 must also have
    • .aisdlc/project/components/{module}.md
    • .aisdlc/project/contracts/api/{module}.md
    • .aisdlc/project/contracts/data/{module}.md
    • evidence entry points (code/tests/CI/ops)
  • P1 must have
    • .aisdlc/project/components/{module}.md
    • at least one contract entry page (API or Data)
  • P2 only requires
    • an index placeholder (components/index.md; if there are products, also a placeholder)
    • keeping the entry link is sufficient (if there is no entry, write "not found")

How to write the Scope output (put it in the index)

In .aisdlc/project/components/index.md reflect the classification and progress in the table (the index only navigates, it does not write 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/... - [ ]

status use checkboxes:- [ ] not met;- [x] meets the DoD for the corresponding priority.

Common mistakes

  • Treating P0/P1/P2 as "writing priority": the correct meaning is "different delivery depth gates."
  • P0 only writes component pages, not contract entry pages: this makes it impossible to trace the "commitment boundary" in subsequent integrations/changes.
  • P2 is also written as a detailed module page: the scope will get out of control and maintenance will fail.

Red flag checklist (if any one appears: stop and correct)

  • "All modules must be written down to the field level" or "write all the details first"
  • Before P0 is completed, start spreading out the details of P1/P2
  • Cannot clearly identify who the P0 module is/what its boundaries are, yet has already started writing a large amount of process detail