speckit-checklist

Generate requirement-quality checklists from feature specs with traceability markers.

Updated May 3, 2026
One-click install
npx skills add https://github.com/Mohsen3-5/Trader --skill speckit-checklist-mohsen3-5
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-checklist
Source: https://github.com/Mohsen3-5/Trader/tree/main/Trader/.claude/skills/speckit-checklist
Command: npx skills add https://github.com/Mohsen3-5/Trader --skill speckit-checklist-mohsen3-5

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you turn a feature spec written in plain English into a systematically reviewable set of requirements by ensuring completeness, clarity, consistency, measurability, and scenario coverage.

Core Features & Use Cases

  • Requirement “unit tests”: Generates checklist items that evaluate the requirements themselves rather than the eventual implementation.
  • Scenario and quality dimensions: Covers core requirement quality dimensions (completeness, clarity, consistency, acceptance criteria quality, measurability) plus scenario, edge case, and non-functional requirements.
  • Spec traceability prompts: Encourages each checklist item to reference spec sections or mark explicit [Gap]/[Ambiguity]/[Conflict]/[Assumption] when requirements are missing or unclear.

Quick Start

Run speckit-checklist with your focus domain so it generates a domain-named checklist in the feature’s checklists folder.

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 review requirement quality from a feature spec?

To generate a requirement quality checklist, run the skill with a specified focus domain to evaluate feature specs for completeness, clarity, consistency, measurability, and scenario coverage. It produces an appended or newly created checklist file within the feature's checklists directory.

What is requirement traceability and how does it apply to spec review?

Requirement traceability in spec review ensures each checklist item references specific spec sections. When requirements are missing or unclear, the checklist enforces explicit markers like [Gap], [Ambiguity], [Conflict], or [Assumption] to highlight issues.

How do I check if my acceptance criteria cover edge cases and non-functional requirements?

To check acceptance criteria coverage, the skill evaluates feature specs across core quality dimensions and scenario classes. It systematically generates checklist items that target edge cases and non-functional requirements to ensure comprehensive coverage.

Can I use spec-kit projects to validate feature context and requirement clarity?

Yes, this skill applies to spec-kit projects where feature context is stored under the feature directory. It validates requirement clarity by running optional extension hooks before and after generating the review checklist.

Why does my generated checklist include [Gap] markers for missing requirements?

Generated checklists include [Gap] markers to explicitly identify missing or ambiguous requirements during the spec review process. This enforces traceability and highlights incomplete sections within your feature specification.