spec-checklist

Validate technical specifications for ambiguity, missing edge cases, and measurable criteria.

Updated Jul 7, 2026
One-click install
npx skills add https://github.com/eavichay/mycli --skill spec-checklist-eavichay
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spec-checklist
Source: https://github.com/eavichay/mycli/tree/main/.cursor/skills/spec-checklist
Command: npx skills add https://github.com/eavichay/mycli --skill spec-checklist-eavichay

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill addresses the common issue of ambiguous, incomplete, or unmeasurable requirements by treating them as code that requires unit testing.

Core Features & Use Cases

  • Requirement Quality Validation: Evaluates specs for clarity, completeness, and measurability using a structured checklist approach.
  • Mission-Brief Adequacy: Automatically scores project mission briefs against oracle adequacy standards.
  • Use Case: Before starting implementation on a new feature, run this skill to identify gaps in your spec, such as missing edge cases or non-quantified performance requirements.

Quick Start

Run the spec-checklist skill to generate a quality review for the current feature requirements.

Frequently Asked Questions about spec-checklist

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

FAQPage Schema
How do I validate the quality and completeness of technical specifications?

Validate technical specifications by applying rigorous checklist-based unit testing to requirement documentation. This process identifies ambiguities, missing edge cases, and non-measurable acceptance criteria within your project specs.

What is checklist-based unit testing for requirement documentation?

Checklist-based unit testing for requirement documentation treats specifications as code, enforcing traceability and consistency standards. It scores mission briefs against oracle adequacy standards to ensure clarity and measurability.

How do I check spec.md and plan.md files for missing edge cases?

Check spec.md and plan.md files for missing edge cases by running automated quality reviews within feature-specific directories. This evaluates requirement documentation for completeness and identifies gaps before implementation.

Does requirement validation work with existing project planning documents?

Requirement validation works directly with existing project planning documents like spec.md and plan.md. It operates within feature-specific directories to enforce traceability and consistency standards across your files.

When should I run a requirement quality validation check?

Run requirement quality validation before starting implementation on a new feature. This identifies gaps in your spec, such as missing edge cases or non-quantified performance requirements, preventing costly downstream errors.