Skip to content
cccskills
FreePublished on GitHub

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.

The English summary is being prepared. Showing the original description.

Run score Not tested

See how to install

Files included (1)

  • SKILL.md3.1 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

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
  • Acceptance criteria - Success conditions

2. Design Coverage Analysis

Map requirements to design elements:

  • Architecture decisions - System structure
  • Component specifications - Module designs
  • Interface definitions - API contracts
  • Data models - Database schemas
  • Workflow diagrams - Process flows
  • UML diagrams - Class/sequence/state diagrams

3. Implementation Coverage Analysis

Verify code implements requirements:

  • Feature implementation - Functionality exists
  • API endpoints - Required interfaces present
  • Business logic - Rules implemented
  • Data persistence - Storage implemented
  • Error handling - Edge cases handled
  • Integration points - Connections implemented

4. Test Coverage Analysis

Ensure tests validate requirements:

  • Unit tests - Component-level validation
  • Integration tests - Interaction validation
  • Acceptance tests - Requirement validation
  • Scenario tests - User story coverage
  • Edge case tests - Boundary condition coverage
  • Performance tests - Non-functional validation

Coverage Checking Workflow

Step 1: Extract Requirements

Identify all requirements from source documents.

Step 2: Map to Design Elements

Check if requirements appear in design.

Step 3: Verify Implementation

Check if code implements design.

Step 4: Validate Test Coverage

Ensure tests verify requirements.

Step 5: Generate Coverage Report

Produce comprehensive coverage analysis.

Best Practices

  1. Start with requirements - Ensure requirements are clear and complete
  2. Use unique IDs - Every requirement needs traceable identifier
  3. Check all levels - Verify design, code, and tests
  4. Be systematic - Use checklists and matrices
  5. Document gaps - Record what's missing and why
  6. Prioritize fixes - Address critical gaps first
  7. Automate when possible - Use tools for traceability
  8. Update regularly - Check coverage as project evolves
  9. Include stakeholders - Review coverage with team
  10. Track over time - Monitor coverage trends

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Applies abstract interpretation using different abstract domains (intervals, octagons, polyhedra, sign, congruence) to statically analyze program variables and infer invariants, value ranges, and relationships. Use when analyzing program properties, inferring loop invariants, detecting potential errors, or understanding variable relationships through static analysis.

The English summary is being prepared. Showing the original description.

ArabelaTso/Skills-4-SE258Updated Aug 21, 2026

Uses abstract interpretation to automatically infer loop invariants, function preconditions, and postconditions for formal verification. Generates invariants that capture program behavior and support correctness proofs in Dafny, Isabelle, Coq, and other verification systems. Use when adding formal specifications to code, generating verification conditions, inferring contracts for functions, or discovering loop invariants for proofs.

The English summary is being prepared. Showing the original description.

ArabelaTso/Skills-4-SE258Updated Aug 21, 2026

Performs abstract interpretation over source code to infer possible program states, variable ranges, and data properties without executing the program. Reports potential runtime errors including out-of-bounds accesses, null dereferences, type inconsistencies, division by zero, and integer overflows. Use when analyzing code for potential runtime errors, performing static analysis, checking safety properties, or verifying program behavior without execution.

The English summary is being prepared. Showing the original description.

ArabelaTso/Skills-4-SE258Updated Aug 21, 2026

Performs abstract interpretation to produce summarized execution traces and high-level program behavior representations. Highlights key control flow paths, variable relationships, loop invariants, function summaries, and potential runtime states using abstract domains (intervals, signs, nullness, etc.). Use when analyzing program behavior, understanding execution paths, computing loop invariants, tracking variable ranges, detecting potential runtime errors, or generating program summaries without concrete execution.

The English summary is being prepared. Showing the original description.

ArabelaTso/Skills-4-SE258Updated Aug 21, 2026

Create ACSL (ANSI/ISO C Specification Language) formal annotations for C/C++ programs. Use this skill when working with formal verification, adding function contracts (requires/ensures), loop invariants, assertions, memory safety annotations, or any ACSL specifications. Supports Frama-C verification and generates comprehensive formal specifications for C/C++ code.

The English summary is being prepared. Showing the original description.

ArabelaTso/Skills-4-SE258Updated Aug 21, 2026

CLI-based browser automation with persistent page state using ref-based element interaction. Use when users ask to navigate websites, interact with web pages, fill forms, take screenshots, test web applications, or extract information from web pages.

The English summary is being prepared. Showing the original description.

ArabelaTso/Skills-4-SE258Updated Aug 21, 2026

See all skills by ArabelaTso

Report a problem with this skill