requirement-gap-analysis
Use this skill when you need to find missing, conflicting, or untestable requirement information; triggers include requirement gap analysis.
How do I install this agent skill?
npx skills add https://github.com/naodeng/awesome-qa-skills --skill requirement-gap-analysisIs this agent skill safe to install?
- Gen Agent Trust Hubpass
The skill is a professional quality assurance tool for identifying requirement gaps. It provides structured prompts and evaluation scripts to help QA engineers find ambiguities, omissions, or conflicts in documentation. Analysis of the scripts and instructions found no malicious patterns, secrets, or unauthorized external connections.
- Socketpass
No alerts
- Snykpass
Risk: LOW · No issues
What does this agent skill do?
Requirement Gap Analysis
When to Use
- Use this skill when you need to find ambiguities, omissions, conflicts, untestable statements, and cross-role dependency gaps in requirements.
- Use it to review an existing plan, result, or evidence set and produce actionable improvements.
- Use it when context is incomplete but a bounded first pass is still valuable.
Output Format Options
- Default to Markdown for review, execution, and incremental refinement.
- When the user requests tables, CSV, JSON, or ticket fields, preserve risk, evidence, priority, and boundary information.
- For machine-consumed output, confirm the schema, enums, and required fields first.
How to Use
- Read and follow
prompts/requirement-gap-analysis.md, including its input contract, execution rules, minimum coverage, and output order. - Add only context that changes the decision: scope, environment, version, constraints, evidence, and success criteria.
- Audit the input, then separate confirmed facts, working assumptions, and open questions.
- Rank by risk and evidence strength, and produce an artifact that can be executed or reviewed directly.
- If information is missing, deliver a bounded first pass and state which conclusions remain unsupported.
Reference Files
-
When calibrating domain outcomes, valid controls, or evidence gaps, read references/domain-decision-example.md for sanitized input, per-item oracles, and reproducible calculations.
-
Always read
prompts/requirement-gap-analysis.md; it is the complete execution specification for this skill. -
For evaluation or regression, read
evals/eval.yamland the relevant cases underevals/cases/. -
Load
references/,examples/,scripts/, oroutput-formats.mdonly when those directories exist and the task needs them.
Domain Execution Essentials
- Build a versioned checklist of applicable roles, states, rules, exceptions, and closure conditions, tied to supplied sources. Do not force irrelevant checklist items onto a product.
- Separate MISSING_RULE (relevant but undefined behavior), MISSING_MATERIAL (referenced evidence absent), CONFLICT, N/A (evidenced scope exclusion), and COMPLETE.
- Give requirement ID, missing content, affected scenarios, blockage, owner, and minimal clarification. An unseen field or empty document does not by itself prove a product defect.
- Close only with authoritative added rules/source version and testable expectations, updating traceability. Unapproved suggestions remain proposals; complete controls must not receive invented gaps.
Core Constraints
- do not fill business decisions for stakeholders
- separate facts, inferences, and questions
- prioritize gaps likely to cause rework or incidents
- Never invent system behavior, fields, data, metrics, or root causes absent from the evidence.
- Link important conclusions to evidence; mark unsupported conclusions as hypotheses with a verification method.
- Explain priority using business impact, likelihood, or detectability.
Delivery Checklist
- Covered: goals and scope, roles, rules, states, failures, data, permissions, dependencies, non-functional needs, acceptance and rollback.
- Separated facts, assumptions, gaps, and recommendations.
- Gave high-risk items a priority, evidence basis, owner or next action.
- Defined verifiable decision criteria instead of generic advice.
- Performed no unauthorized production writes or destructive actions.
Common Pitfalls
- Listing checks without preconditions, expected outcomes, or evidence.
- Marking everything high priority and avoiding tradeoffs.
- Substituting tool names or generic theory for domain reasoning.
- Refusing incomplete input, or pretending incomplete evidence supports certainty.
Best Practices
- Start with paths most likely to cause business loss, safety issues, or release blockage.
- Reduce uncertainty through the smallest verifiable experiment and record reproduction conditions.
- Make the artifact executable and independently reviewable by another engineer.
How can the creator link this skill?
Add the canonical catalog link to the repository README so users can inspect current installs and available audits. The publishing guide covers the complete discovery path.
<a href="https://skillzs.dev/skills/naodeng/awesome-qa-skills/requirement-gap-analysis">View requirement-gap-analysis on skillZs</a>