Spec Pack Verification Main Skill: spec-test

This skill is the worker skill entry for the verification phase: it is responsible for unified access control, input/output constraints, traceability and DoD self-check. Actual artifacts are generated by the sub-skill

spec-test-*

Authoritative Reference:

design/aisdlc_spec_verification.md

(this document is the SSOT for this skill).

When to Use

You need to produce or update any of the following files for a Spec Pack:

```
verification/test-plan.md
```
```
verification/usecase.md
```
```
verification/suites.md
```
```
verification/report-{date}-{version}.md
```

You start to notice the following "red flags" (indicating high risk of rule violation):
- You want to "just write to
```
./verification/
```
  first and migrate later"
- You want to skip
```
requirements/*
```
  or project-level memory, saying "just write a template placeholder first"
- You want to use
```
TBD/to be filled
```
  instead of AC traceability and impact scope
- You want to decide the next process within the skill (unauthorized routing)

When Not to Use

You are making the diversion judgment of "where to go next/whether to skip verification": this belongs to the Router, you should return to
```
using-aisdlc
```
.
You need to write automated test code: this skill in the verification phase is only responsible for document artifacts and access control, and does not require automated code implementation.

Hard Access Control (Must Comply)

1) Locate before reading/writing:

FEATURE_DIR

must be obtained first

For any read/write operation on
verification/*
, you must run
spec-context
first to get
FEATURE_DIR
and echo it.
Stop immediately if
spec-context
fails: do not guess the path, do not infer from the current working directory, do not "write to the root directory first".

2) Must-read context (progressive disclosure)

If reading fails or the context does not exist, you must explicitly write

CONTEXT GAP

, and do not skip silently:

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

Minimum required input at requirement level (at least one must exist):

{FEATURE_DIR}/requirements/solution.md

{FEATURE_DIR}/requirements/prd.md

3) Worker boundary: Unauthorized routing is prohibited

This skill and its sub-skills are only responsible for access control + artifact storage + DoD self-check.
After completion, you must not decide "what to do next" inside the skill, you can only output
```
ROUTER_SUMMARY
```
and prompt "return to Router (using-aisdlc) to continue routing".

Sub-skill List (Call/Routing Entry)

Sub-skill	Artifacts (Persistent Storage)	Purpose
`spec-test-plan`	`{FEATURE_DIR}/verification/test-plan.md`	Freeze scope/strategy/environment/entry & exit criteria/risk list
`spec-test-usecase`	`{FEATURE_DIR}/verification/usecase.md`	Convert AC into executable, automation-ready test case structure
`spec-test-suites`	`{FEATURE_DIR}/verification/suites.md`	Organize smoke/regression/targeted suites and execution order
`spec-test-execute`	`{FEATURE_DIR}/verification/report-{date}-{version}.md`	Produce conclusive report: coverage/results/blockers/defect references/risk suggestions

Anti-patterns and Explicit Countermeasures (From Baseline Pressure Scenarios)

Common Excuses/Pressure Statements	Facts and Countermeasures
"We are in a hurry, just write to `./verification/` first and move it later"	Path guessing is prohibited. Storing artifacts without locating `FEATURE_DIR` will create untraceable junk artifacts; you must run `spec-context` first.
"Requirements are coming too slow, just write a template placeholder first"	The core of verification is AC → test case/report traceability; not reading `solution/prd` equals giving up verifiable criteria. `CONTEXT GAP` is allowed, but using `TBD` to pretend completion is not allowed.
"The person in charge said ignore the access control, as long as it works"	The value of worker skill is access control; if you have to deviate from the process, you can only write down the risks and consequences in the artifact, upgrade the deviation to an explicit `CONTEXT GAP / PROCESS DEVIATION` , and still cannot guess the path.
"I'll tell you what to do next by the way"	Unauthorized routing is prohibited. You can only output `ROUTER_SUMMARY` , and the next step is decided by `using-aisdlc` .

Output Convention (Unified for Router Consumption)

When any

spec-test

spec-test-*

is completed, you must perform the three steps of "post-completion output and automatic routing" (consistent with worker skills such as

spec-product-clarify

Output ROUTER_SUMMARY (in YAML format for Router decision; specific stage/artifacts are subject to each sub-skill)
Execute
using-aisdlc
immediately: Pass
```
ROUTER_SUMMARY
```
as routing input, and the Router will determine the next step and automatically proceed (no need to wait for the user to say "continue")
Conversation output: Before calling using-aisdlc, you can briefly state "The artifacts of this phase have been stored, and using-aisdlc is being called to route the next step."

Compatibility note: Historically, some documents used free text/custom field form of "router summary". In the Spec Pack process of this repository, the YAML
ROUTER_SUMMARY
defined by
using-aisdlc
is the only authoritative output format.

spec-test

NPX Install

Tags

SKILL.md Content (Chinese)