test-coverage-design

Derive test coverage gaps from code and specs into a minimal edge-case-first test plan.

14|Updated May 28, 2026
One-click install
npx skills add https://github.com/Redtropig/harness-anchor --skill test-coverage-design
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: test-coverage-design
Source: https://github.com/Redtropig/harness-anchor/tree/main/skills/test-coverage-design
Command: npx skills add https://github.com/Redtropig/harness-anchor --skill test-coverage-design

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams identify gaps in test coverage by deriving obligations from code and specs, then highlighting where tests are missing before a feature is considered complete.

Core Features & Use Cases

  • Derives black-box obligations from the spec and code to reveal risk areas.
  • Designs a minimal, edge-case-first test set that exercises critical paths and boundaries.
  • Dispatches the coverage-analyst subagent to generate, validate, and document the test plan.
  • Language-agnostic approach suitable for any project.

Quick Start

Provide the feature spec and code to the coverage-analyst to generate a targeted test plan.

Frequently Asked Questions about test-coverage-design

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I identify test coverage gaps from feature specs and code?

To identify test coverage gaps, derive black-box obligations from the spec and code to reveal risk areas, then highlight where tests are missing before a feature is considered complete.

What is risk-based test design for edge cases?

Risk-based test design for edge cases is a method that derives black-box obligations from specs and code to reveal risk areas, then designs a minimal, edge-case-first test set to close those gaps.

Can I use this test coverage analysis for any programming language?

Yes, you can use this test coverage analysis for any programming language because it applies a language-agnostic approach suitable for any project to generate a targeted test plan.

What's the best way to design a minimal test set for critical paths?

The best way to design a minimal test set for critical paths is to dispatch a coverage-analyst to derive obligations from code and specs, designing an edge-case-first test set that exercises boundaries.

Do I need to provide both the spec and code to generate a test plan?

Yes, you need to provide both the feature spec and code to the coverage-analyst to generate a targeted test plan that aligns with the spec and provides concrete run-scope guidance.