requirements-analysis-plus
Parse Word/HTML/JSON/Markdown/Excel requirement files and produce a structured analysis conclusion.
12 stars
bynaodeng
Best use case
requirements-analysis-plus is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Parse Word/HTML/JSON/Markdown/Excel requirement files and produce a structured analysis conclusion.
Teams using requirements-analysis-plus 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-plus/SKILL.md --create-dirs "https://raw.githubusercontent.com/naodeng/awesome-qa-skills/main/skills/en/testing-types/requirements-analysis-plus/SKILL.md"
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/requirements-analysis-plus/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How requirements-analysis-plus Compares
| Feature / Agent | requirements-analysis-plus | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Parse Word/HTML/JSON/Markdown/Excel requirement files and produce a structured analysis conclusion.
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-plus (EN) **中文版:** 见对应中文技能。 ## When to Use - Need deeper requirement analysis across multiple source documents. - Need stronger prioritization, conflict checks, and follow-up questions than the base version. ## Output Format Options Markdown by default unless the request explicitly asks for another format. ## How to Use 1. Open `prompts/requirements-analysis-plus.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-plus.md`: main prompt for this skill. - `references/`: supporting notes loaded only when needed. - `examples/`: sample inputs or outputs. - `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
We are still matching the closest adjacent skills for this page. In the meantime, continue through the full directory.