speckit-checklist

Generate requirements-quality checklists for spec-kit feature specifications.

Updated Sep 13, 2026
One-click install
npx skills add https://github.com/secrakib/rag-eval-project --skill speckit-checklist-secrakib
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: speckit-checklist
Source: https://github.com/secrakib/rag-eval-project/tree/main/.agents/skills/speckit-checklist
Command: npx skills add https://github.com/secrakib/rag-eval-project --skill speckit-checklist-secrakib

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing clear, complete, and testable requirements is hard, and gaps or ambiguities in specs often surface only during implementation. This Skill generates custom checklists that act as unit tests for requirements, validating the quality of your feature specifications before coding begins. ## Core Features & Use Cases - Requirements Quality Validation: Generates checklist items that test completeness, clarity, consistency, measurability, and coverage of requirements rather than implementation behavior. - Domain-Specific Checklists: Creates or appends to themed checklist files (e.g., ux.md, api.md, security.md) inside the feature's checklists directory with sequential CHK IDs. - Interactive Clarification: Derives up to three contextual clarifying questions from the user's input and spec signals to calibrate scope, depth, and audience. - Use Case: Before implementing a new API feature in a spec-kit project, run this Skill to produce an api.md checklist confirming that error response formats, rate limits, and authentication requirements are fully specified. ## Quick Start Ask the agent to generate a security requirements checklist for the current feature using the speckit-checklist skill.

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 for a spec-kit feature?▼

Invoke the speckit-checklist skill with a domain focus such as ux, api, or security. It reads spec.md, plan.md, and tasks.md from the feature directory, asks clarifying questions, then writes a checklist file under the feature's checklists folder.

What makes a spec-kit checklist different from a test plan?▼

These checklists test the quality of the requirements themselves, not the implementation. Items ask whether requirements are defined, quantified, and consistent, rather than verifying that buttons click or APIs return correct responses.

Does speckit-checklist require a specific project structure?▼

Yes, it requires a spec-kit project with a .specify directory containing scripts, templates, and optionally memory and extensions.yml files. It runs check_prerequisites.py to locate the feature directory and template content.

Can I add items to an existing checklist file?▼

Yes, when the target checklist file already exists, the skill appends new items continuing from the last CHK identifier. Existing content is never deleted or replaced, and new items are always left unchecked.

Why are generated checklist items left unchecked?▼

Checkbox state belongs to the reviewer, not the generator. A checked box means a reviewer confirmed the requirements-quality criterion is satisfied, so the skill must never mark generated items as complete.