Release Testing Workflow

中文版： 见技能 release-testing-workflow。

End-to-end release testing (1–2 weeks before release through post-release). Prompts: see reference.md and this directory's prompts/.

When to Use

• User mentions release testing, Go/No-Go, or release readiness
• Need timeline: T-14 planning → T-7 feature freeze → T-5–T-4 specialized testing → T-3 RC → T-2 quality assessment → T-1 Go/No-Go → T-day release → T+1–T+7 post-release
• Trigger: e.g. “How do we schedule pre-release testing?” or “Go/No-Go checklist”

How to Use

1. Check reference.md to find the prompt file for the current step.
2. Open the corresponding file in prompts/, then combine it with the current context (scope, environment, risks, constraints).
3. Run step by step, and update priorities or gates based on outputs and blockers.

Common Pitfalls