speckit-checklist

Name: speckit-checklist
Availability: InStock
Author: d0whc3r

Generate requirement-quality checklist items from feature specifications.

2|Updated Feb 16, 2026

Search Tags:#requirements #acceptance criteria #traceability #spec-kit #scenario coverage #checklist generation #spec validation

Ready to run

npx skills add https://github.com/d0whc3r/statsig-browser-extension --skill speckit-checklist-d0whc3r

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: speckit-checklist
Source: https://github.com/d0whc3r/statsig-browser-extension/tree/main/.trae/skills/speckit-checklist
Command: npx skills add https://github.com/d0whc3r/statsig-browser-extension --skill speckit-checklist-d0whc3r

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Converts a feature’s written specification into a requirements-quality checklist, helping teams ensure the spec is complete, clear, consistent, and testable before implementation starts.

Core Features & Use Cases

Requirement Quality Validation: Flags missing, ambiguous, inconsistent, non-measurable, and conflicted requirements using requirement-focused items rather than implementation tests.
Scenario & Edge-Case Coverage: Ensures primary, alternate, exception/error, recovery, and non-functional requirements are addressed, including explicit gap markers.
Traceability Support: Encourages referencing spec sections or using structured gap/ambiguity markers so issues can be located and resolved.

Quick Start

Run the speckit-checklist command with your feature/user requirements as the input, then review the appended checklist items for completeness, clarity, consistency, measurability, and scenario coverage.

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 specification?▼

To validate specification completeness, the tool flags missing, ambiguous, and non-measurable requirements within your feature spec. It appends structured checklist items that ensure clarity, consistency, and scenario coverage before implementation begins.

How does traceability work when validating spec-kit requirements?▼

Traceability is maintained by referencing spec sections directly or using structured gap markers within the generated checklist. This mapping allows teams to locate and resolve missing, ambiguous, or conflicting requirements identified during validation.

Can I check for edge-case and exception scenario coverage in my requirements?▼

Yes, checklist generation ensures primary, alternate, exception, error, recovery, and non-functional requirements are explicitly addressed. It flags scenario coverage gaps with structured markers to validate edge-case handling within your specifications.

Does spec validation work with the .specify directory and extensions hook?▼

Yes, spec validation processes feature inputs from the .specify directory and supports optional .specify/extensions.yml hook-aware pre and post behavior. This enables seamless integration into existing feature-driven requirement workflows.

What is requirement-ready checklist generation and when do I need it?▼

Requirement-ready checklist generation transforms written specifications into validation items verifying completeness, clarity, consistency, and measurability. You need it to ensure your spec is fully testable and coverage-ready before implementation starts.