spec-verifying

Verify EARS specification coverage against Dart test files.

Updated Nov 2, 2025
One-click install
npx skills add https://github.com/3balljugglerYu/ai_coordinate --skill spec-verifying
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spec-verifying
Source: https://github.com/3balljugglerYu/ai_coordinate/tree/main/.agents/skills/spec-verifying
Command: npx skills add https://github.com/3balljugglerYu/ai_coordinate --skill spec-verifying

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill ensures that your implemented tests accurately reflect your EARS specifications, preventing gaps in test coverage and identifying discrepancies between documentation and code.

Core Features & Use Cases

  • Test Coverage Reporting: Generates a detailed report showing the percentage of specifications covered by implemented tests.
  • Discrepancy Identification: Highlights unimplemented specifications, tests without corresponding specs (orphan tests), and tests that violate naming conventions.
  • Use Case: After writing new specifications for a feature, use this skill to verify that all required test cases have been implemented, ensuring the feature is robustly tested before release.

Quick Start

Run the spec-verifying skill to check the test coverage for the 'AuthViewModel' class.

Frequently Asked Questions about spec-verifying

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

FAQPage Schema
How do I verify EARS specification coverage in a Flutter project?

To verify EARS specification coverage in a Flutter project, parse your YAML specification files and Dart test files to generate a comprehensive report. This report identifies test coverage gaps, flags naming convention violations, and detects orphan tests lacking specification linkage.

What are orphan tests in Dart and how do I find them?

Orphan tests in Dart are implemented test files lacking corresponding EARS specification linkage. You can find them by parsing your Dart test files alongside your YAML specifications to detect discrepancies and flag tests without matching specification entries.

Can I check if my Dart tests align with EARS naming conventions?

Yes, you can check Dart test alignment with EARS naming conventions by parsing the test files and comparing them against your YAML specifications. The verification process specifically flags naming convention violations and highlights discrepancies between documentation and code.

What is the best way to find unimplemented specifications in a Dart codebase?

The best way to find unimplemented specifications in a Dart codebase is to verify consistency between your EARS specification files and implemented test files. This verification generates a detailed report showing the percentage of specifications covered by implemented tests and highlights missing test cases.

Does spec-verifying work without external dependencies?

Yes, spec-verifying works without external dependencies. It directly parses your existing YAML specification files and Dart test files within your Flutter project to identify coverage gaps, naming convention violations, and orphan tests to ensure documentation and code consistency.