Organize usecase.md the use case numbers in into an executable set (smoke / regression / targeted), and specify execution order, dependencies, and blocking criteria。
Inputs and gates (must be followed)
REQUIRED SUB-SKILL: currently executing spec-context to obtain context, and echo in the conversation FEATURE_DIR=...(allows (reuse)）。
- must-read project-level memory：
project/memory/product.md、project/memory/tech.md、project/memory/glossary.md; if it cannot be read, you must writeCONTEXT GAP。 - Input dependencies：
{FEATURE_DIR}/verification/usecase.mdand{FEATURE_DIR}/verification/test-plan.mdshould already exist; if missing, you must writeCONTEXT GAPand stop (to avoid fabricating arrangements). - Suites must be locatable: suite entries must point to specific use case numbers (vague descriptions such as "covers the login flow" are prohibited).
Output (written to disk)
{FEATURE_DIR}/verification/suites.md
Mandatory template (must be followed)
suites.mdmust be generated according to the template (do not invent structures/field names):assets/suites_template.md
Content requirements (minimum structure)
suites.md must contain at least:
- Smoke
- Blocking rules (consistent with
test-plan.mdexit criteria) - Use case list:
TC-*
- Blocking rules (consistent with
- Regression
- Use case list:
TC-*(may be grouped)
- Use case list:
- Targeted (targeted regression, if applicable)
- Trigger conditions (impact-analysis / risk list / change description)
- Use case list:
TC-*
- Execution order and dependencies (e.g., smoke → targeted → regression)
DoD self-check (V3-DoD)
- Every entry in the suite can be traced to a specific
TC-*number - The smoke suite has a clear criterion of "failure blocks delivery" and is consistent with
test-plan.mdconsistent - The targeted suite can be traced back to the impact scope/risk source (if any
requirements/solution.md#impact-analysis）