Generate/update the test plan for the current Spec Pack: freeze scope, strategy, environment, entry/exit criteria, risks, and verification checklist, and keep it traceably consistent with the acceptance criteria of requirements/* .
Inputs and Gates (must comply)
REQUIRED SUB-SKILL: currently executing spec-context to obtain context, and echo in the conversation FEATURE_DIR=...(allowed (reuse)）。
- Required reading of project-level memory：
project/memory/product.md、project/memory/tech.md、project/memory/glossary.md; if it cannot be read, must writeCONTEXT GAP。 - Minimum requirement-level input：
{FEATURE_DIR}/requirements/solution.mdor{FEATURE_DIR}/requirements/prd.mdat least one of them must exist; otherwise stop and writeCONTEXT GAP。
Output (write to disk)
{FEATURE_DIR}/verification/test-plan.md
Mandatory Template (must comply)
test-plan.mdmust be generated according to the template (no inventing structures/field names):assets/test_plan_template.md
Content Requirements (minimum structure)
test-plan.md must contain at least:
- Executive Summary (capability under test/version/objective/key risks)
- Test Scope (In/Out)
- Test Strategy (types: functional/UI/integration/regression/security...; methods: positive/negative/boundary)
- Environment and Data (environment, accounts/permissions, data preparation method)
- Entry Criteria
- Exit Criteria (must include the definition of "blocking delivery")
- Risk and Verification Checklist (Owner/Deadline/Signal/Action)
- Traceability Links (pointing to
solution/prd's AC/scope source; if there is#impact-analysis, it must also be linked) - CONTEXT GAP (if any: impact caused by missing inputs)
DoD Self-Check (V1-DoD)
- Scope In/Out is clear and consistent with
requirements/*Agree - Has entry/exit criteria and can clearly state "under what circumstances delivery is blocked"
- Risks are not just a checklist for show: each risk has a minimum verification action (Owner/Signal/Action)
- Has a traceability entry: at least can answer "which AC/scope definition this plan is based on"