speckit-checklist

Generate unit-test style checklists to validate software feature requirements quality.

12|1|Updated Apr 15, 2026
One-click install
npx skills add https://github.com/reason-healthcare/rh-skills --skill speckit-checklist-reason-healthcare
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-checklist
Source: https://github.com/reason-healthcare/rh-skills/tree/main/.agents/skills/speckit-checklist
Command: npx skills add https://github.com/reason-healthcare/rh-skills --skill speckit-checklist-reason-healthcare

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Creating high-quality requirements is hard; this Skill automatically generates a structured set of unit-test style checklists to verify requirements quality, ensuring they are complete, clear, consistent, and testable.

Core Features & Use Cases

  • Generates "Unit Tests for Requirements" that assess completeness, clarity, consistency, measurability, coverage, and edge cases against feature requirements.
  • Organizes items into domain-focused CHECK IDs (e.g., CHK001) and supports traceability by referencing spec sections like [Spec §X.Y].
  • Manages a checklists repository by creating or appending to checklists/ subdirectories, according to the current feature directory and template guidelines.

Quick Start

Run speckit-checklist to generate a requirements-quality checklist for the 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 write unit tests for software requirements to check quality?

Generate unit-test style checklists for software requirements to validate quality attributes like completeness, clarity, consistency, and testability. These checklists assess your feature descriptions against specific quality criteria.

What is a requirements quality checklist and when do I need one?

A requirements quality checklist is a structured set of validation items ensuring software specifications are complete, clear, consistent, and measurable. You need one when finalizing feature requirements to catch gaps before implementation.

How do I generate a checklist from a feature specification?

Apply the checklist generator to a feature description within a FEATURE_DIR. It loads spec.md, plan.md, and tasks.md when present to derive context and produce targeted checklist items with traceability references.

Can I append new checklist items to an existing checklists directory?

Yes, the tool manages a checklists repository by creating or appending to checklists subdirectories. It organizes items into domain-focused CHK IDs and references spec sections using a unified template.

Does generating requirements checklists require a specific project structure?

The tool expects a FEATURE_DIR containing a feature description, and optionally loads spec.md, plan.md, and tasks.md files. It uses these files to derive context and output targeted checklist items.

What is the best way to trace checklist items back to specification sections?

Use generated checklists that include CHK IDs and traceability references like [Spec §X.Y]. This links every unit-test style validation item directly to the relevant specification section.