Individual skill

requirement-coverage-checker

Verify that design documents, code implementations, and tests fully cover all specified requirements. Use this skill when validating requirement traceability, conducting design reviews, assessing implementation completeness, checking test coverage against requirements, performing compliance audits, or identifying missing functionality. Produces coverage reports showing which requirements are satisfied, partially satisfied, or missing.

skills/requirement-coverage-checker/SKILL.md

Read pinned source

Source commit 4f38503747e0617504bce5329283ef837d375c09

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
No
Observed behavior
Not checked yet
Last checked
Nov 6, 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)
260
Repository last updated
Aug 21, 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

# Requirement Coverage Checker

Systematically verify that design and implementation cover all specified requirements. Identifies gaps, ensures traceability, and validates that every requirement has corresponding design elements, code, and tests.

## Core Capabilities

### 1. Requirement Extraction

Parse and identify requirements from documents:
- **Functional requirements** - Feature specifications
- **Non-functional requirements** - Performance, security, usability
- **Business rules** - Constraints and policies
- **User stories** - As-a/I-want/So-that format
- **Use cases** - Actor-goal scenarios
Back to top