release-testing-workflow · diff
git:20260325.c371d73 to git:20260803.f52f41e
29 added, 36 removed. Audit A to A.
---
name: release-testing-workflow
- description: Use this skill when you need release-phase QA workflow from T-14 planning to go/no-go and post-release monitoring; triggers include release testing workflow and release readiness testing.
+ description: Use this skill when you need release-phase QA workflow from T-14 planning to go/no-go and post-release monitoring; triggers include release testing workflow and go/no-go QA.
---
# Release Testing Workflow
- **中文版：** 见对应中文技能。
+ **中文版：** See the corresponding Chinese skill.
## When to Use
- - Need a structured release testing workflow flow instead of a single testing task.
- - Need to move step by step across a testing phase with the matching prompts.
+ - Need a release-window cadence: T-N planning → specialties → RC → Go/No-Go → post-release watch.
+ - Need release gates and a ship evidence pack, with specialty execution handed to type skills.
- ## Output Format Options
+ ## Workflow
- Markdown by default unless the request explicitly asks for another format.
+ 1. Read and follow `prompts/release-testing-workflow.md` (timeline, gates, Go/No-Go, handoffs).
+ 2. Add release date, scope, freeze rules, candidate build, and known defects that change decisions.
+ 3. After locating the T window, optionally read stage files under `prompts/`; invoke specialty type skills by name.
+ 4. If input is incomplete, still draft a gate board and mark assumptions—**never invent pass results**.
- ## How to Use
+ ## Core Constraints
- 1. Check [reference.md](reference.md) first and find the prompt file for the current step.
- 2. Open the matching file under `prompts/` and add only the context that matters: scope, environment, risks, constraints, and expected output.
- 3. Run step by step, and adjust priorities when blockers, risks, or scope changes appear.
+ - Own release timeline and ship decision; hand specialty reports to `performance-testing` / `security-testing` / etc.
+ - Timelines may compress; gate criteria may not be deleted.
+ - Go/No-Go requires evidence; conditional Go must be verifiable.
+ - No relative-path links to other skill files.
- ## Workflow Steps
+ ## Progressive Disclosure
- - `accessibility-testing.md`
- - `ai-assisted-testing.md`
- - `automation-testing.md`
- - `functional-testing.md`
- - `manual-testing.md`
- - `performance-testing.md`
- - `requirements-analysis.md`
- - `security-testing.md`
- - `test-case-writing.md`
- - `test-reporting.md`
- - `test-strategy.md`
+ - Before producing output, read and follow `prompts/release-testing-workflow.md`.
+ - For step mapping: read `reference.md`.
+ - For stage/specialty deep-dives: read matching `prompts/*.md` in this skill.
+ - Templates: `output-templates/`.
- ## Reference Files
+ ## Pre-delivery Checklist
- - `prompts/`: prompt files used by this skill.
- - `reference.md`: step-to-prompt mapping and workflow routing.
- - `references/`: supporting notes loaded only when needed.
- - `scripts/`: helper scripts or converters for this skill.
+ - [ ] Followed the main prompt’s output structure
+ - [ ] Includes scope/exclusions, T window, gate board, evidence gaps, next skill
+ - [ ] At decision point: Go / No-Go / conditional with rationale
+ - [ ] Did not invent pass results or unknown defect states
+ - [ ] Assumptions and open questions are marked
## Common Pitfalls
- - Do not jump into execution before confirming the current step.
- - Do not try to run the whole workflow with one giant prompt.
- - Do not ignore blockers and reprioritization.
-
- ## Best Practices
-
- - Start from the prompt file, then add only the context that matters.
- - Keep the output risk-driven and executable.
- - If the request is incomplete, return a usable first version and mark gaps.
+ - Do not delete gates just to compress the calendar.
+ - Do not declare RC done before freeze.
+ - Do not write full specialty long-reports inside this skill.
+ - Do not replace conditional-Go terms with vague “keep watching”.