speckit-checklist

Name: speckit-checklist
Availability: InStock
Author: burningddol

Generate domain-aligned requirement checklists from spec-kit feature files.

Updated Apr 3, 2026

Search Tags:#checklist #requirements #qa #engineering #speckit #spec-kit #unit-tests

Ready to run

npx skills add https://github.com/burningddol/epigram --skill speckit-checklist-burningddol

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Generate a structured, high-quality checklist from feature specs to validate completeness, clarity, consistency, traceability, and coverage of requirements.

Core Features & Use Cases

Generates unit-test-style checklist items aligned to the specified requirements quality dimensions (Completeness, Clarity, Consistency, Measurability, Coverage, Edge Case, Non-Functional).
Loads feature context from a standard spec-kit project structure (with a .specify/ directory) and extracts relevant sections from spec.md, plan.md, and tasks.md.
Outputs to FEATURE_DIR/checklists/[domain].md, appending to existing files or creating new ones with incremental IDs.

Quick Start

Run the speckit-checklist command from the repo root with the active FEATURE_DIR to generate or update a domain-specific checklist.

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 spec-kit project?▼

To generate a requirements checklist from a spec-kit project, use a tool that parses the .specify directory containing spec.md, plan.md, and tasks.md to extract focus areas and output structured quality criteria.

What quality dimensions should a feature requirements checklist cover?▼

A feature requirements checklist should cover completeness, clarity, consistency, measurability, coverage, edge cases, and non-functional requirements to validate the overall quality and traceability of the specifications.

How do I append new checklist items to existing markdown files without overwriting content?▼

To append new checklist items to existing markdown files without overwriting content, use a generation tool that preserves existing file data and assigns incremental IDs to new entries for full traceability.

Can I output domain-specific checklists into separate markdown files per feature?▼

Yes, you can output domain-specific checklists into separate markdown files by writing the generated items to a checklists subdirectory within the active feature directory, naming each file by its domain.

Do I need unit tests to validate feature requirement quality criteria?▼

You do not need actual unit tests to validate feature requirement quality criteria; instead, you can generate unit-test-style checklist items that align with specified requirements to verify completeness and coverage.

Why does my generated checklist lack traceability for feature specs?▼

A generated checklist lacks traceability for feature specs when the tool fails to assign incremental IDs or does not properly map the extracted focus areas from the spec.md, plan.md, and tasks.md files.