Overview
The role of DoD is to:make the outputs maintainable. Discover without a DoD will, under pressure, degrade into "detail accumulation / untraceable / no one dares to change it".
At the start, announce:"I am using the aisdlc-project-discover-dod-gates skill to perform a DoD self-check and gate closure on the Discover outputs."
Project-level DoD (minimum self-check checklist)
-
memory/The four documents already have "clear entry points / clear boundaries / navigability" - The Level-1 index skeleton has been generated, and the checkbox progress is usable
- Each P0 modulesatisfies:
-
components/{module}.mdexists and has clear boundaries (In/Out) -
contracts/api/{module}.mdhas the triad (authoritative entry point + invariants + evidence entry point) -
contracts/data/{module}.mdhas the triad (authoritative entry point + invariants + evidence entry point) - index backfill is complete (
components/index.md、contracts/*/index.md)
-
-
productshas converged to ≤ 6; if it cannot converge, the reason and governance entry point have been recorded - The index only navigates, details are not double-written; module pages/contract pages are the authoritative entry points
- (if there are ops)
ops/index.mdprovides locatable entry points (dashboard/alerting/runbook/rollback), and does not copy the operations manual
Gate rules (must enforce)
- The index only navigates: any
index.mdcontaining field tables/detailed sequences/operations manuals → considered a failure. - Contract pages do not write exhaustive field dictionaries: the goal of a contract page is the authoritative entry point and a summary of invariants; field-level descriptions are not part of this Discover's project-level outputs.
- Missing evidence does not permit making things up: when evidence is missing, you may only write "not found + how to look for it next", and expose the gap to the maintainer.
Common pitfalls (and how to avoid them)
- Pitfall: trying to write everything all at once
- Avoidance: Scope first; land P0 first; P1/P2 only get placeholders and entry points
- Pitfall: writing one-off delivery details into the project level
- Avoidance: the project level only writes entry points/boundaries/guardrails; details only provide evidence entry points
- Pitfall: double-writing the index and the module
- Avoidance: the index only navigates; module pages/contract pages are the authority
- Pitfall: the contract is not authoritative
- Avoidance: the triad is mandatory; none may be missing
Red-flag checklist (if any one appears: stop and roll back the direction of changes)
- Adding
.aisdlc/project/docs/*(data-dictionary/api-reference) to carry an exhaustive field dictionary - Adding
.aisdlc/project/flows/*or.aisdlc/project/ops/runbooks/*to carry one-off delivery details - The delivery approach of "write all the details first, fill in the index later"
- A P0 module is missing a contract page or missing an evidence entry point, yet is declared "completed"