Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
naodeng avatar

Requirements Analysis

  • 146 installs
  • 144 repo stars
  • Updated August 5, 2026
  • naodeng/awesome-qa-skills

requirements-analysis is a Claude agent QA skill that analyzes requirement documents for test points, boundaries, dependencies, and risks for developers and QA engineers who must assess testability before writing test ca

About

requirements-analysis is a QA skill from naodeng/awesome-qa-skills that helps developers and QA engineers analyze requirements before test design when documents are incomplete, ambiguous, or changing frequently. The skill loads prompts/requirements-analysis.md as the main prompt, accepts project context including scope, environment, constraints, risks, and dependencies, and outputs a risk-driven analysis usable for execution and review. The workflow decomposes requirements into business rules and state transitions, marks ambiguity such as missing inputs or conflicting logic, maps test dimensions across functional, data, interface, workflow, and non-functional areas, prioritizes by user impact and change volatility, forms clarification questions with decision owners, and delivers analysis conclusions with recommended next QA actions. Default output is Markdown with optional Excel, CSV, JSON, or Word formats documented in output-formats.md. Reach for requirements-analysis when the team needs to know what can be tested now versus what requires PM or dev clarification before case implementation.

  • Loads prompts/requirements-analysis.md as the primary analysis prompt template
  • Six-step flow: decompose rules, mark ambiguity, map test dimensions, prioritize, clarify, conclude
  • Maps functional, data, interface, workflow, and non-functional test dimensions
  • Outputs ambiguity list, clarification questions, risk ranking, and testability conclusion
  • Supports Markdown default plus optional Excel, CSV, JSON, Word via output-formats.md

Requirements Analysis by the numbers

  • 146 all-time installs (skills.sh)
  • +8 installs in the week ending Aug 4, 2026 (Skillselion tracking)
  • Ranked #892 of 2,153 Testing & QA skills by installs in the Skillselion catalog
  • Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/naodeng/awesome-qa-skills --skill requirements-analysis

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs146
repo stars144
Last updatedAugust 5, 2026
Repositorynaodeng/awesome-qa-skills

How do you assess requirement testability before test design?

Analyze a PRD with requirements-analysis to produce ambiguity lists, risk rankings, clarification questions, and testability conclusions before writing test cases.

Who is it for?

QA engineers and developers analyzing PRDs or specs with ambiguous, incomplete, or fast-changing requirements before investing in test case authoring.

Skip if: Teams with fully specified acceptance criteria and stable requirements who are ready to jump directly into automated test implementation.

When should I use this skill?

User requests requirements analysis, test point identification, ambiguity review, or risk assessment on a PRD before test case writing.

What you get

Requirements analysis report with ambiguity list, risk ranking, clarification questions, dependency map, and testability conclusion.

  • requirements analysis report
  • ambiguity list
  • clarification questions

By the numbers

  • Six-step analysis workflow from decomposition through clarification to conclusions
  • Maps five test dimensions: functional, data, interface, workflow, non-functional
  • Bundled prompt at prompts/requirements-analysis.md with optional output-formats.md

Files

SKILL.mdMarkdownGitHub ↗

Requirements Analysis (English)

中文版: 见对应中文技能。

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.

Output Format Options

Markdown by default. If you need Excel, CSV, JSON, Word, or other supported formats, append the format request at the end and check output-formats.md.

How to Use

1. Open prompts/requirements-analysis.md and use it as the main prompt. 2. Add the real project context: scope, environment, constraints, risks, dependencies, and expected deliverable. 3. If the input is incomplete, return a usable first version and mark missing information and assumptions.

Reference Files

  • prompts/requirements-analysis.md: main prompt for this skill.
  • output-formats.md: optional output format instructions.
  • references/: supporting notes loaded only when needed.
  • scripts/: helper scripts or converters for this skill.

Common Pitfalls

  • Do not use it with vague scope and no context.
  • Do not treat every area as equally important.
  • Do not skip assumptions and missing information.

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.

Related skills

How it compares

Use requirements-analysis for pre-test requirement risk assessment; use requirements-analysis-plus when parsing multi-format source documents with deeper conflict checks.

FAQ

What prompt file drives requirements-analysis?

requirements-analysis uses prompts/requirements-analysis.md as its main prompt; developers add real project context—scope, environment, constraints, risks, and expected deliverable—before triggering analysis on requirement input.

What outputs should requirements-analysis produce?

requirements-analysis should deliver an ambiguity list, clarification questions with decision owners, risk ranking, testability conclusion, dependency list, and recommended next QA actions in Markdown or another requested format.

When should QA rerun requirements-analysis?

requirements-analysis should be rerun after PM or development clarifications arrive so the final analysis reflects resolved ambiguities and updated scope before test case implementation begins.

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.