This skill is used during the verification phase (V1–V4) of a Spec Pack: generating/updating test plans, test cases, test suites, and test reports. By default it is based onmanual testing; automation is only an optional enhancement.
When to use
- You need to produce or update any of the following files for a Spec Pack:
verification/test-plan.mdverification/usecase.mdverification/suites.mdverification/report-{date}-{version}.md
When not to use
- You need to write automated test code: this skill is only responsible for verification document artifacts and gates, and does not require implementing automated code at this stage.
Inputs and gates (must be followed)
REQUIRED SUB-SKILL: currently executing spec-context to obtain context, and echo it in the conversation FEATURE_DIR=...(allowed (reuse)）。
Required context
- Project level:
project/memory/product.mdproject/memory/tech.mdproject/memory/glossary.md
- Requirement level (at least one of):
{FEATURE_DIR}/requirements/solution.mdor{FEATURE_DIR}/requirements/prd.md
When missing, you must explicitly write it in the output artifact CONTEXT GAP, and must not silently skip it.
Sub-skills overview
| Sub-skill | Artifact (persisted) | Purpose |
|---|---|---|
spec-test-plan |
{FEATURE_DIR}/verification/test-plan.md |
Freeze scope/strategy/environment/entry and exit criteria/risk list |
spec-test-usecase |
{FEATURE_DIR}/verification/usecase.md |
Convert ACs into manually executable test cases (test case template is mandatory) |
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 |
Record execution results and provide conclusions (coverage/blockers/defect references/risk recommendations) |
spec-test-bug |
(does not persist a bug file) | Generate defect report body text that can be pasted directly into an external defect system, and guide writing defect references back to report-*.md |
Equivalent capability scope (aligned with the core capabilities of qa-test-planner)
Without depending on qa-test-planner , this skill group provides the following capabilities and adapts them to this repository's constraints:
- Test plan (V1): scope/strategy/environment/entry and exit criteria/risk list; includes regression layering (smoke/targeted/full) and blocking criteria.
- Manual test cases (V2): generated according to a unified template; each step is decidable; ACs are traceable; structural information can be retained for subsequent automation generation (but writing automated code at this stage is not required).
- Test suites (V3): smoke/regression/targeted; entries must be locatable to
TC-*; execution order and blocking criteria align with the test-plan. - Test report (V4): coverage statistics (suite/priority), AC↔TC coverage mapping, blockers, defect reference list, conclusion and next-step actions (executable).
- Defect report (Vx): outputs defect report body text that can be pasted directly into an external defect system; after the external defect is created/updated, the ID/link/status/severity and associated TC must be written back to
report-*.md。
General constraints
- Defects are not persisted separately within a Spec Pack: adding
verification/bugs/**is prohibited; only reference the external defect system (ID/link/status/severity/associated TC) in the "defect list" ofreport-*.md.