requirements-analysis SKILL.md skillA
requirements-analysis from naodeng/awesome-qa-skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add naodeng/awesome-qa-skills/requirements-analysis@git:20260903.6713296Pins git:20260903.6713296 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- naodeng/awesome-qa-skills
- Path
skills/en/testing-types/requirements-analysis/SKILL.md- Versions recorded
- 3
- Latest version
- git:20260903.6713296, committed Sep 3, 2026
- First version recorded
- Mar 25, 2026
- Size
- 2,598 bytes
- Repository stars
- 301
- License
- a license file GitHub does not identify
Use this skill when you need to analyze requirements, identify test points, boundaries, dependencies, and risks before test design; triggers include requirements analysis and test point analysis.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Requirements Analysis (English) **Chinese version：** See the corresponding Chinese skill. ## When to Use - Need help with requirements analysis in a real project context. - Need an output that can be used directly for execution, review, or follow-up. ## Workflow 1. Read and follow the main prompt listed under Progressive disclosure (coverage, structure, quality bar). 2. Add only project context that changes the result: scope, environment, constraints, risks, dependencies, expected deliverable. 3. If input is incomplete, return a usable first draft and explicitly mark assumptions and gaps. 4. Default to Markdown; switch formats only when the user asks. ## Core Constraints - Prioritize by risk / business impact — do not treat everything equally. - Separate confirmed facts from current assumptions. - Do not invent endpoints, fields, environments, or root causes the user did not provide. - Keep output executable: concrete scenarios, clear priority, clear next steps. ## Progressive Disclosure - Before producing output, read and follow `prompts/requirements-analysis.md` (minimum coverage, output structure, quality bar). …
Read the whole file at its exact version.
How to install
mdr add naodeng/awesome-qa-skills/requirements-analysis@sha256:722a4c371eaad84aThe line at the top of this page pins the label git:20260903.6713296, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_ypem4iurcyb2vcud)
1 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 3 versions of this file, between Mar 25, 2026 and Sep 3, 2026, about one every 81 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260903.6713296 latest | 2026-09-03 | 6713296 | 2,598 B | A | view · diff |
| git:20260803.f52f41e | 2026-08-03 | f52f41e | 2,592 B | A | view · diff |
| git:20260325.c371d73 | 2026-03-25 | c371d73 | 1,642 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (2598 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
naodeng/awesome-qa-skills · 301 stars · license a license file GitHub does not identify · pushed 2026-11-06 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_ypem4iurcyb2vcud GET https://markdownregistry.com/api/v1/resolve?ref=naodeng/awesome-qa-skills/requirements-analysis GET https://markdownregistry.com/api/v1/blob/722a4c371eaad84a53abd919d6808cdb82b1da0d7d6354c95efb8156b35b0550
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.
More from naodeng/awesome-qa-skills
Every file in naodeng/awesome-qa-skills