# Requirements Analyzer [简体中文](README.zh-CN.md) · [How it works](HOW_IT_WORKS.md) · [Known limitations](KNOWN_LIMITATIONS.md) Quality-and-risk analysis of **requirement documents**. It audits sources, finds gaps and conflicts, and writes one register with executable P0 / P1 verification. What the register looks like:
It is **not** [`codexqa-testcase-generator`](https://github.com/openqa-cn/codexqa/blob/main/skills/codexqa-testcase-generator/README.md). That skill writes test plans and manual cases from local requirements (files, paste, or HTTPS docs). This skill reviews whether the requirements themselves are complete, consistent, and testable. ## What you give it **Documents, not a git clone.** | Job | Bring | |---|---| | Analyze one PRD | The requirement text (file, paste, or URL the agent can fetch) | | Multi-source pack | PRD plus stories / API notes / scope / plan. Optional role reports with `source_role` | | Incomplete pack | Whatever you have. The run still ships a first draft and marks gaps | No application `code/`. No clone URL. Do not ask this skill to invent endpoints, SLAs, or whether the feature is worth building. ## What it does 1. Intake and a short-input gate. 2. Structure inventory, source audit, smells, NFR and success-metrics grids. 3. One gap / conflict register (`RA-xx`) with risk and testability. 4. P0 / P1 items get verification fields (preconditions, stimulus, expected, evidence). Default output is Markdown. Excel / CSV / JSON / Word only when you ask (`output-formats.md`). Helper scripts live in `scripts/` (`npx --yes tsx scripts/run_analysis.ts --input