speckit-checklist

Generate structured checklists that validate feature specification quality and completeness.

Updated Jul 17, 2026

Search Tags:#quality assurance #documentation #checklist #specification #requirements #validation

Ready to run

npx skills add https://github.com/fmbetancourt/famifinances --skill speckit-checklist-fmbetancourt

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: speckit-checklist
Source: https://github.com/fmbetancourt/famifinances/tree/main/.agents/skills/speckit-checklist
Command: npx skills add https://github.com/fmbetancourt/famifinances --skill speckit-checklist-fmbetancourt

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill addresses the ambiguity and incompleteness in feature specifications by treating requirements as code that requires unit testing, ensuring that documentation is clear, measurable, and ready for implementation.

Core Features & Use Cases

Requirements Validation: Automatically generates a checklist to test the quality, clarity, and completeness of your feature specs.
Traceability & Coverage: Ensures that all scenarios, including edge cases and non-functional requirements, are explicitly defined and measurable.
Use Case: Before starting development on a new API endpoint, use this Skill to generate a checklist that identifies missing error handling definitions or ambiguous success criteria in your spec.

Quick Start

Invoke the speckit-checklist skill to generate a quality validation checklist for the current feature specification.

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 specification quality before starting development?▼

Feature specification validation is done by generating structured checklists that act as unit tests for requirements, analyzing spec, plan, and task documents to identify ambiguity, consistency issues, and coverage gaps before implementation begins.

What is the best way to check requirements for ambiguity and missing edge cases?▼

Checking requirements for ambiguity involves treating documentation as code and applying automated checklist validation to ensure all scenarios, including edge cases and non-functional requirements, are explicitly defined and measurable.

Can I use an automated checklist to ensure spec coverage and traceability?▼

Automated checklists ensure spec coverage and traceability by analyzing spec-kit project structures to verify that all requirements are measurable, documented, and aligned with project principles.

How do I test that my API endpoint specifications include error handling definitions?▼

Testing API endpoint specifications involves generating a validation checklist that identifies missing error handling definitions or ambiguous success criteria within your feature spec documentation.

Do I need a spec-kit project structure to validate requirements documentation?▼

A spec-kit project structure is required to validate requirements documentation, as the checklist operates within this environment to analyze spec, plan, and task documents for quality and completeness.

When should I not use automated unit tests for requirements validation?▼

Automated unit tests for requirements validation should not be used after implementation begins, as the tool is designed to ensure documentation is clear, measurable, and ready for development prior to coding.