AI Agent Skill HUB

requirements-analysis

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.

12 stars
bynaodeng
View on GitHubInstallation ↓

Best use case

requirements-analysis is best used when you need a repeatable AI agent workflow instead of a one-off prompt.

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.

Teams using requirements-analysis should expect a more consistent output, faster repeated execution, less prompt rewriting.

When to use this skill

  • You want a reusable workflow that can be run more than once with consistent structure.

When not to use this skill

  • You only need a quick one-off answer and do not need a reusable workflow.
  • You cannot install or maintain the underlying files, dependencies, or repository context.

Installation

Claude Code / Cursor / Codex

$curl -o ~/.claude/skills/requirements-analysis/SKILL.md --create-dirs "https://raw.githubusercontent.com/naodeng/awesome-qa-skills/main/skills/en/testing-types/requirements-analysis/SKILL.md"

Manual Installation

  1. Download SKILL.md from GitHub
  2. Place it in .claude/skills/requirements-analysis/SKILL.md inside your project
  3. Restart your AI agent — it will auto-discover the skill

How requirements-analysis Compares

Feature / Agentrequirements-analysisStandard Approach
Platform SupportNot specifiedLimited / Varies
Context Awareness High Baseline
Installation ComplexityUnknownN/A

Frequently Asked Questions

What does this skill do?

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.

Where can I find the source code?

You can find the source code on GitHub using the link provided at the top of the page.

SKILL.md Source

# 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](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

requirements-analysis-plus

12
from naodeng/awesome-qa-skills

Parse Word/HTML/JSON/Markdown/Excel requirement files and produce a structured analysis conclusion.

sprint-testing-workflow

12
from naodeng/awesome-qa-skills

Use this skill when you need a sprint-based QA workflow from planning through review and retrospective; triggers include sprint testing workflow and sprint QA flow.

release-testing-workflow

12
from naodeng/awesome-qa-skills

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.

discover-testing

12
from naodeng/awesome-qa-skills

Use this skill when you need to quickly route a request to the best testing-type or testing-workflow skill.

daily-testing-workflow

12
from naodeng/awesome-qa-skills

Use this skill when you need a day-by-day QA routine including planning, execution, bug reporting, and end-of-day wrap-up; triggers include daily testing workflow and daily QA routine.

testcase-writer-plus

12
from naodeng/awesome-qa-skills

Parse requirement and analysis files, then generate high-quality test cases.

test-strategy

12
from naodeng/awesome-qa-skills

Use this skill when you need to define a test strategy covering scope, methods, resources, risks, and quality gates; triggers include test strategy and QA planning.

test-strategy-plus

12
from naodeng/awesome-qa-skills

Generate a structured test strategy from requirement, analysis, technical, and plan documents.

test-reporting

12
from naodeng/awesome-qa-skills

Use this skill when you need to generate test reports with summary, metrics, defect analysis, and risk assessment; triggers include test reporting and QA status report.

test-case-writing

12
from naodeng/awesome-qa-skills

Use this skill when you need to create high-quality test cases with normal, exception, and boundary scenarios; triggers include test case writing and test design.

test-case-reviewer

12
from naodeng/awesome-qa-skills

Use this skill when you need to review test cases for completeness, clarity, maintainability, and missing scenarios; triggers include test case review and test case QA.

test-case-reviewer-plus

12
from naodeng/awesome-qa-skills

Review test cases using requirement, strategy, and supporting documents, then output structured findings.