Spec Test Suite (V3: Suites)

Organize the test case numbers in

usecase.md

into executable sets (smoke / regression / targeted), and clarify execution order, dependencies and blocking rules.

Official Specification:

design/aisdlc_spec_verification.md

Hard Access Control (Must Comply)

Locate before reading/writing: You must first run
```
spec-context
```
to get and echo
```
FEATURE_DIR=...
```
; stop immediately if it fails, guessing the path is prohibited.
Mandatory reading of project-level memory:
```
project/memory/product.md
```
,
```
project/memory/tech.md
```
,
```
project/memory/glossary.md
```
; if you cannot read them, you must write
```
CONTEXT GAP
```
.
Input dependencies:
```
{FEATURE_DIR}/verification/usecase.md
```
and
```
{FEATURE_DIR}/verification/test-plan.md
```
should already exist; if they are missing, you must write
```
CONTEXT GAP
```
and stop (to avoid out-of-thin-air orchestration).
Suite must be locatable: Suite entries must point to specific test case numbers (vague descriptions such as "cover login process" are prohibited).
Unauthorized routing is prohibited: Only output
```
ROUTER_SUMMARY
```
after completion, the next step is decided by
```
using-aisdlc
```
.

Red Flag Checklist (Stop if any item occurs)

Trying to orchestrate a suite "based on experience" without
```
usecase.md
```
The smoke suite does not have a clear rule of "failure blocks delivery"
Suite entries cannot be mapped to specific
```
TC-*
```
numbers

Only Operation (PowerShell)

1) Get

FEATURE_DIR

powershell

. ".\skills\spec-context\scripts\spec-common.ps1"
$context = Get-SpecContext
$FEATURE_DIR = $context.FEATURE_DIR
Write-Host "FEATURE_DIR=$FEATURE_DIR"

2) Target Output Path

powershell

$out = Join-Path $FEATURE_DIR "verification/suites.md"
Write-Host "OUTPUT=$out"

Minimum Output Structure (Recommended)

Write to

{FEATURE_DIR}/verification/suites.md

, which should include at least:

Smoke
- Objective: Fast blocking of critical paths
- Estimated duration
- Blocking rules (consistent with the release criteria in
```
test-plan.md
```
  )
- Test case list:
```
TC-...
```
  (list)
Targeted
- Trigger conditions (e.g. modules/risks hit by impact-analysis)
- Test case list:
```
TC-...
```
Regression
- Coverage description (by module/capability/risk)
- Test case list:
```
TC-...
```
Execution order and dependencies
- Recommended order: smoke → targeted → regression (can be adjusted according to project constraints, but must be clearly stated)

DoD Self-Check (V3-DoD)

Each entry in the suite can be located to a specific
```
TC-*
```
number
The smoke suite has a clear rule of "failure blocks delivery", which is consistent with that in
```
test-plan.md
```
The targeted suite can be traced to the impact scope/risk source (if any, e.g.
```
requirements/solution.md#impact-analysis
```
)

Output and Automatic Routing after Completion (Mandatory)

After

suites.md

is written to disk, you must complete the following actions (in order, cannot be omitted):

Output ROUTER_SUMMARY (in YAML format for Router decision making):

yaml

ROUTER_SUMMARY:
  stage: V3
  artifacts:
    - "{FEATURE_DIR}/verification/suites.md"
  needs_human_review: false
  blocked: false
  block_reason: ""
  notes: "Soft checkpoint: Test suite has been generated/updated; Router can continue to automatically advance to V4 (spec-test-execute)"

Execute
using-aisdlc
immediately: Pass the above
```
ROUTER_SUMMARY
```
as routing input to using-aisdlc, the Router will determine the next step and automatically proceed (no need to wait for the user to say "continue").
- If the Router determines that automatic continuation is possible: continue to execute the next worker skill (e.g. V4, etc.) in the same round of conversation
- If the Router triggers a hard interrupt: stop and output the blocking reason, required inputs, and candidate next steps
Conversation output: Before calling using-aisdlc, you can briefly state "The product of this phase has been written to disk, and using-aisdlc is being called to route the next step."

name: spec-test-suites description: Use when you need to generate or update the V3 test suite orchestration (verification/suites.md) in the verification phase of the Spec Pack in sdlc-dev, organize test cases by smoke/regression/targeted and clarify blocking rules and traceability sources.

Spec Test Suite (V3: verification/suites.md)

Overview

This skill is a worker skill for the verification phase, only responsible for:

Access control verification (first locate
```
{FEATURE_DIR}
```
, then read necessary inputs)
Generate/update
```
{FEATURE_DIR}/verification/suites.md
```
Self-check according to V3-DoD (suite entries can be located to test case numbers)
Return to
```
using-aisdlc
```
after outputting
```
ROUTER_SUMMARY
```

Hard Access Control (Cannot be Bypassed)

1) Locate FEATURE_DIR first (guessing path is prohibited)

powershell

. ".\skills\spec-context\scripts\spec-common.ps1"
$context = Get-SpecContext
$FEATURE_DIR = $context.FEATURE_DIR
Write-Host "FEATURE_DIR=$FEATURE_DIR"

Stop immediately if it fails.

2) Mandatory reading of project-level Memory (write CONTEXT GAP if missing)

```
.aisdlc/project/memory/product.md
```
```
.aisdlc/project/memory/tech.md
```
```
.aisdlc/project/memory/glossary.md
```

If any is missing: explicitly write

CONTEXT GAP

suites.md

3) Must read test cases and plans (otherwise orchestration is impossible)

```
{FEATURE_DIR}/verification/usecase.md
```
(must exist)
```
{FEATURE_DIR}/verification/test-plan.md
```
(recommended to exist; write
```
CONTEXT GAP
```
if missing and put the risk into blocking items)

{FEATURE_DIR}/requirements/solution.md#impact-analysis

exists: it should be read for targeted suite traceability; if it does not exist, explain the basis source of targeted.

Output (Written to Disk)

```
{FEATURE_DIR}/verification/suites.md
```

Minimum Structure of

suites.md

(Must Include)

smoke
- Estimated execution duration
- Blocking rules (consistent with V1 release criteria)
- Test case list (must write TC numbers)
regression
- Test case list (TC numbers, can be grouped by module/impact scope)
targeted (if applicable)
- Trigger conditions (from impact-analysis / risk list)
- Test case list (TC numbers)
Execution order and dependencies (e.g. smoke → targeted → regression)

V3-DoD Self-Check

Suite entries can be located to specific test case numbers (vague descriptions are prohibited)
Blocking rules of the smoke suite are consistent with V1 release criteria
The targeted suite has traceable sources (impact-analysis/risk list/change description)

Red Flag STOP

Start writing
```
suites.md
```
without echoing
```
FEATURE_DIR=...
```
Suite entries do not reference any
```
TC-...
```
numbers

Output and Automatic Routing after Completion (Mandatory)

After

suites.md

is written to disk, you must complete the following actions (in order, cannot be omitted):

Output ROUTER_SUMMARY (in YAML format for Router decision making):

yaml

ROUTER_SUMMARY:
  stage: V3
  artifacts:
    - "{FEATURE_DIR}/verification/suites.md"
  needs_human_review: false
  blocked: false
  block_reason: ""
  notes: "Soft checkpoint: Test suite has been generated/updated; Router can continue to automatically advance to V4 (spec-test-execute)"

Execute
using-aisdlc
immediately: Pass the above
```
ROUTER_SUMMARY
```
as routing input to using-aisdlc, the Router will determine the next step and automatically proceed (no need to wait for the user to say "continue").
- If the Router determines that automatic continuation is possible: continue to execute the next worker skill (e.g. V4, etc.) in the same round of conversation
- If the Router triggers a hard interrupt: stop and output the blocking reason, required inputs, and candidate next steps
Conversation output: Before calling using-aisdlc, you can briefly state "The product of this phase has been written to disk, and using-aisdlc is being called to route the next step."

spec-test-suites

NPX Install

Tags

SKILL.md Content (Chinese)

Spec Test Suite (V3: Suites)

Hard Access Control (Must Comply)

Red Flag Checklist (Stop if any item occurs)

Only Operation (PowerShell)

1) Get
`FEATURE_DIR`

2) Target Output Path

Minimum Output Structure (Recommended)

DoD Self-Check (V3-DoD)

Output and Automatic Routing after Completion (Mandatory)

name: spec-test-suites description: Use when you need to generate or update the V3 test suite orchestration (verification/suites.md) in the verification phase of the Spec Pack in sdlc-dev, organize test cases by smoke/regression/targeted and clarify blocking rules and traceability sources.

Spec Test Suite (V3: verification/suites.md)

Overview

Hard Access Control (Cannot be Bypassed)

1) Locate FEATURE_DIR first (guessing path is prohibited)

2) Mandatory reading of project-level Memory (write CONTEXT GAP if missing)

3) Must read test cases and plans (otherwise orchestration is impossible)

Output (Written to Disk)

Minimum Structure of
`suites.md`
(Must Include)

V3-DoD Self-Check

Red Flag STOP

Output and Automatic Routing after Completion (Mandatory)