speckit-checklist

Generate requirement-quality checklists with traceability references for Spec-Kit feature domains.

Updated Jan 5, 2026
One-click install
npx skills add https://github.com/demersonpolli/basic-interpreter --skill speckit-checklist-demersonpolli
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-checklist
Source: https://github.com/demersonpolli/basic-interpreter/tree/main/.agents/skills/speckit-checklist
Command: npx skills add https://github.com/demersonpolli/basic-interpreter --skill speckit-checklist-demersonpolli

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

It helps you validate that your requirements are complete, clear, consistent, and testable before implementation begins, reducing ambiguity and rework.

Core Features & Use Cases

  • Requirement Unit Testing: Produces checklist items that assess requirement quality (completeness, clarity, consistency, measurability, coverage) rather than checking whether code works.
  • Scenario Coverage: Encourages inclusion of primary, alternate, exception/error, recovery, and non-functional requirements, including edge cases and rollback expectations when state changes.
  • Append-Only Checklist Growth: Creates a domain checklist file (e.g., ux.md/api.md) or appends new items while preserving existing content and CHK numbering.
  • Traceability-First Items: Forces most checklist items to reference spec sections (e.g., [Spec §X.Y]) or explicitly mark gaps, ambiguities, conflicts, assumptions, and missing criteria.
  • Use Case Example: Use it during PR review to improve a feature spec by identifying missing acceptance criteria, undefined terms, inconsistent requirements, and unaddressed failure paths.

Quick Start

Run the speckit-checklist skill with your feature domain or focus area as the argument to generate an appended checklist for requirements quality validation.

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 checklist to validate requirement completeness and scenario coverage?

Generate a requirement validation checklist by loading feature context from the Spec-Kit structure and producing numbered items that assess completeness, clarity, consistency, measurability, and scenario coverage. The output validates primary, alternate, error, recovery, and non-functional requirements.

What is traceability-referenced checklist generation for feature specs?

Traceability-referenced checklist generation creates validation items that explicitly reference spec sections like [Spec §X.Y] or mark gaps, ambiguities, conflicts, and missing criteria. This ensures every checklist item maps directly to a requirement or highlights a specific documentation deficiency.

How do I handle missing acceptance criteria and undefined terms during PR review?

Handle missing acceptance criteria and undefined terms by running a spec validation checklist that identifies gaps, ambiguities, and inconsistent requirements. The checklist evaluates requirement quality and flags unaddressed failure paths and edge cases for resolution before implementation.

Can I append new validation items to an existing requirements checklist without losing numbering?

Append new validation items to an existing requirements checklist using an append-only persistence model. The process preserves existing content and CHK numbering while adding new scenario-based validation items to domain files like ux.md or api.md.

Does requirement validation work with Spec-Kit .specify and FEATURE_DIR files?

Requirement validation works directly with Spec-Kit structures by loading feature context from .specify and FEATURE_DIR files. This integration allows the checklist generation process to analyze written specs and produce traceability-referenced items for a specified feature domain.

When should I use scenario-based validation for requirements instead of code testing?

Use scenario-based validation for requirements before implementation begins to reduce ambiguity and rework. This approach performs requirement unit testing to assess documentation quality, completeness, and measurability rather than verifying whether code works, ensuring specs are testable.