speckit-checklist

Generate requirement unit-test checklists for feature domains with traceability and gap labels.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Speckit-checklist helps you detect missing, unclear, inconsistent, or unmeasurable requirements in a feature spec before implementation starts.

Core Features & Use Cases

  • Requirements unit testing: Evaluates whether spec writing quality is complete, clear, consistent, and objectively verifiable.
  • Scenario coverage: Prompts for Primary, Alternate, Exception/Error, Recovery, and Non-Functional requirement coverage, including explicit edge cases and gaps.
  • Traceability-first output: Produces checklist items that reference spec sections when possible and marks gaps, ambiguities, conflicts, and assumptions.

Quick Start

Run speckit-checklist and pass the domain or focus area for the checklist to generate requirement quality checks for your current feature.

Frequently Asked Questions about speckit-checklist

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

FAQPage Schema
How do I validate feature requirements for completeness and clarity before implementation?

You generate requirement unit-test checklists that evaluate completeness, clarity, consistency, and measurability, ensuring acceptance criteria are objectively verifiable and traceable to spec sections.

What is the best way to perform gap analysis on feature acceptance criteria and scenario coverage?

Performing gap analysis on acceptance criteria involves generating checklists that prompt for Primary, Alternate, Exception, Recovery, and Non-Functional scenario coverage, explicitly marking gaps and ambiguities in the output.

How do I check scenario coverage for exception and recovery flows in a feature spec?

Checking scenario coverage for exception and recovery flows requires generating requirement checklists that prompt for these specific paths, ensuring edge cases and non-functional constraints are explicitly reviewed and labeled.

Can I trace requirement gaps and ambiguities directly within a spec-kit style directory structure?

Yes, you can trace requirement gaps and ambiguities within a spec-kit directory by loading feature context from it and producing checklist markdown entries that reference spec sections and mark traceability gaps.

Does requirement unit testing work for non-functional constraints alongside standard acceptance criteria?

Yes, requirement unit testing works for non-functional constraints by explicitly prompting for Non-Functional requirement coverage during checklist generation, ensuring these constraints are reviewed for measurability alongside standard flows.