speckit-checklist

Generate a requirements-quality checklist for a feature spec using the spec-kit project structure.

1|Updated May 20, 2026
One-click install
npx skills add https://github.com/sabrydawood/claude-config --skill speckit-checklist-sabrydawood
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-checklist
Source: https://github.com/sabrydawood/claude-config/tree/main/skills/speckit-checklist
Command: npx skills add https://github.com/sabrydawood/claude-config --skill speckit-checklist-sabrydawood

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill turns a feature’s written requirements into a structured checklist that validates whether the spec is complete, clear, consistent, measurable, and covers key scenarios.

Core Features & Use Cases

  • Unit-test quality for requirements: Checks the writing of requirements rather than verifying implementation behavior.
  • Scenario-focused coverage: Ensures primary, alternate/exception/recovery, and non-functional expectations are addressed with explicit gaps highlighted.
  • Appends domain checklists: Creates a checklist file in the feature directory (or appends with continuing CHK IDs) to build an accumulating audit trail.

Quick Start

Use the speckit-checklist skill to generate a requirements-quality checklist for your current feature described in spec.md.

Frequently Asked Questions about speckit-checklist

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

FAQPage Schema
How do I generate a requirements checklist from a feature spec?

To generate a requirements checklist from a feature spec, provide your domain focus and feature spec context. The Skill loads the feature directory, validates requirement completeness and clarity, and appends checklist items using the repository template.

What does validating requirement quality in a feature spec involve?

Validating requirement quality involves checking the written spec for completeness, clarity, consistency, and measurability. It ensures acceptance criteria quality, scenario coverage, edge cases, and non-functional requirements are explicitly addressed.

How do I ensure my feature spec covers edge cases and non-functional requirements?

To ensure your feature spec covers edge cases and non-functional requirements, generate a scenario-focused checklist. This validates that primary, alternate, exception, and recovery scenarios are addressed, highlighting any explicit gaps in the spec.

Can I append new checklist items to an existing feature directory audit trail?

Yes, you can append new checklist items to an existing feature directory audit trail. The Skill appends continuing CHK### ID items to the checklists file in the feature directory, building an accumulating audit trail for the spec.

Do I need a repository checklist template to validate acceptance criteria?

You do not strictly need a repository checklist template to validate acceptance criteria, but the Skill uses it when available to append formatted CHK### items to your feature directory checklists for consistent requirement quality validation.