Individual skill

codexqa-requirement-analyzer

Full quality-and-risk analysis of requirement documents (single- or multi-source), producing one gap/conflict register with executable P0/P1 verification. Triggers: requirements analyzer, requirement quality, gap register, 需求分析, 需求分析器, 需求评审, 需求缺口. Not for writing a case library (that is codexqa-testcase-generator), constructing test data (codexqa-testdata-generator), or reviewing code (codexqa-defect-analyzer / codexqa-code-reviewer). Former skill name: requirements-analyzer.

skills/codexqa-requirement-analyzer/SKILL.md

Read pinned source

Source commit 783954281fc4898a9fac66a575363f419d4683e4

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Local scripts
Last checked
Nov 5, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
236
Repository last updated
Nov 6, 2026
License
Apache-2.0

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Requirements Analyzer

Human-facing install and method docs: `README.md`, `HOW_IT_WORKS.md`, `KNOWN_LIMITATIONS.md` (and `.zh-CN.md`). Do not load those at runtime.

## When to Use

- Need a complete quality and risk analysis of requirement documents, not just a scope scan or a gap list.
- Materials may be a single PRD or a multi-source pack (stories, APIs, plans, role reports).
- Need one reviewable, assignable, verifiable gap register that can hand off to strategy or case writing.

## Workflow

1. Read and follow the main prompt listed under Progressive disclosure (coverage, structure, quality bar).
2. Run the fixed pipeline: intake → short-input gate → structure inventory → input audit → quality/smell/NFR → success metrics → behavior plus UX states → trace and goal-feature alignment → dependency grid → single register → risk algorithm → testability and oracles → blockers and next actions. Do not write risks or a “TOP 3” list first.