release-testing-workflow

Release Testing Workflow (Chinese Version)

English version: See the corresponding English skill.

When to Use

Need to advance according to the release window: T-N planning → special topic → RC → Go/No-Go → post-release observation.
Need release gates and a release evidence package, and hand off special-topic execution to the type skill.

Authorization Decision Boundary

Only provide release recommendations; formal approval requires an authorized decision-maker and records of version, scope, time, and source. Emergency hotfix/canary may compress the timeline, but gate conditions cannot be omitted.

Execution Flow

Read and follow prompts/release-testing-workflow.md(timeline, gates, Go/No-Go, handoff).
Supplement context such as release date, scope, freeze rules, candidate version, known defects, etc.
After locating the T window, follow reference.md to name the handoff type skill; for special-topic execution, only name the skill.
When information is incomplete, still provide an initial version of the gate dashboard and mark assumptions;fabricating test pass results is prohibited。

Core Constraints

Manage the release timeline and release recommendations; hand special-topic reports to performance-testing / security-testing , etc.
Gates may compress time, but criteria must not be deleted.
Go/No-Go must be based on evidence; conditional release must be verifiable.
Relative-path links to other skill files are prohibited.

Load on Demand

Before producing output, you must read and follow prompts/release-testing-workflow.md。
Steps and handoff comparison: read reference.md。
Phase/special-topic deep dive: call the corresponding type skill; do not expand a full special-topic report within this skill.
Template:output-templates/。

Pre-Delivery Self-Check

Has followed the output structure of the main prompt
Includes scope/exclusions, T window, gate dashboard, evidence gaps, next-hop skill
If at a decision point: Go / No-Go / conditional release has a basis
Did not fabricate pass results or defect statuses that were not provided
Assumptions and open questions are marked

Common Misconceptions

Do not delete gates just to compress the schedule.
Do not claim RC completion when it has not been frozen.
Do not write a full special-topic long report on behalf of others within this skill.
Do not replace conditional release terms with a vague "continue monitoring".