requirement-to-test v1.0.0A

Immutable. This exact content never changes and is served at /api/v1/blob/394eba83c6bb324b.

---
name: requirement-to-test
description: Use this skill when you need to turn requirements into testable, risk-driven, traceable test design; triggers include requirement-to-test and Requirement-to-Test Workflow.
license: PolyForm-Noncommercial-1.0.0
metadata:
  version: "1.0.0"
  compatibility: ""
  author: "Awesome QA Skills contributors"
  language: "en"
  category: "testing-workflows"
  source: "https://github.com/naodeng/awesome-qa-skills"
  license-url: "https://polyformproject.org/licenses/noncommercial/1.0.0"
---

# Requirement-to-Test Workflow

**Chinese version:** See `README.md`.

## When to use

Use this Skill to turn requirements into testable, risk-driven, traceable test design.

## Workflow

Read `prompts/requirement-to-test.md` first; validate inputs, complete each stage, preserve sources, and return risk and handoff details.

## Core constraints

Compose existing specialist Skills without copying their analysis rules. Mark host installation `UNKNOWN` without evidence. Do not report plans or static analysis as executed results. Read-only by default; external writes require authorization.

## Load on demand

- Main process: `prompts/requirement-to-test.md`
- Usage and FAQ: `README_EN.md`
- Evals: `evals/`

## Before delivery

- [ ] Input scope and assumptions are explicit
- [ ] Handoffs preserve sources, status, and gaps
- [ ] Execution evidence is separate from plans
- [ ] Next steps and permission boundary are clear

## Common mistakes

Do not invent input, assume dependencies are installed, or present recommendations as execution or approval.