speckit-checklist

Generate requirements-quality checklists with traceability references from spec content.

Updated Apr 2, 2026
One-click install
npx skills add https://github.com/avansover/mathcraft --skill speckit-checklist-avansover
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-checklist
Source: https://github.com/avansover/mathcraft/tree/main/.claude/skills/speckit-checklist
Command: npx skills add https://github.com/avansover/mathcraft --skill speckit-checklist-avansover

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It turns feature requirements into a rigorous checklist that helps catch missing, unclear, inconsistent, or hard-to-measure requirement statements before implementation starts.

Core Features & Use Cases

  • Unit Tests for Requirements: Evaluates the written requirements themselves for completeness, clarity, consistency, measurability, and coverage across scenarios.
  • Scenario & Edge-Case Coverage: Checks whether primary, alternate, exception/error, recovery, and non-functional expectations are explicitly documented.
  • Traceability-First Items: Produces checklist entries that reference spec sections (or use [Gap]/[Ambiguity]/[Conflict]/[Assumption] markers) to improve reviewability and alignment.

Quick Start

Run the speckit-checklist skill with your feature’s user requirements so it generates an appended domain checklist under the feature folder.

Frequently Asked Questions about speckit-checklist

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

FAQPage Schema
How do I validate requirement quality before implementation starts?

To validate requirement quality, generate a unit-style checklist evaluating spec content for completeness, clarity, consistency, measurability, and scenario coverage to catch missing or unclear statements.

What is a unit test for requirements and how does it work?

A unit test for requirements is a checklist evaluating written spec statements for completeness, clarity, consistency, measurability, and coverage across primary, alternate, exception, and non-functional scenarios.

How do I generate a traceability checklist for feature spec review?

Generate a traceability checklist by appending entries with incrementing CHK IDs and references to spec sections, using [Gap], [Ambiguity], [Conflict], or [Assumption] markers to improve reviewability.

Does speckit-checklist require a specific directory structure to run?

Yes, speckit-checklist requires a spec-kit structure with a .specify directory and loads feature context using repo scripts to write or append checklists in the FEATURE_DIR/checklists folder.

How do I check my spec for missing edge cases and error scenarios?

Check spec content for scenario coverage to ensure primary, alternate, exception/error, recovery, and non-functional expectations are explicitly documented, flagging missing items as gaps.