speckit-checklist

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

Updated Aug 28, 2026
One-click install
npx skills add https://github.com/B18Bu/Refund-Agent --skill speckit-checklist-b18bu
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: speckit-checklist
Source: https://github.com/B18Bu/Refund-Agent/tree/main/.agents/skills/speckit-checklist
Command: npx skills add https://github.com/B18Bu/Refund-Agent --skill speckit-checklist-b18bu

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 a feature specification before coding begins. ## Core Features & Use Cases - Requirements Quality Validation: Produces checklist items that test completeness, clarity, consistency, measurability, and scenario coverage of the spec itself, never the implementation. - Context-Aware Generation: Reads spec.md, plan.md, and tasks.md from the spec-kit feature directory, asks up to three clarifying questions, and appends items with incrementing CHK IDs to domain-named files like ux.md or security.md. - Extension Hook Support: Executes optional or mandatory before/after hooks declared in .specify/extensions.yml. - Use Case: Before implementing a checkout feature, run this Skill with the focus area 'api' to generate an api.md checklist verifying that error responses, rate limits, and versioning requirements are explicitly specified. ## Quick Start Ask the assistant 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 command with a domain argument such as ux, api, or security. The Skill loads the feature's spec, plan, and tasks files, asks clarifying questions, then creates or appends to a checklist file under the feature's checklists directory.

What makes a good requirements quality checklist item?▼

Good items test the requirements themselves, asking whether something is defined, quantified, or consistent, such as 'Is fast loading quantified with specific timing thresholds?' They never verify implementation behavior like clicking, rendering, or API responses.

Does speckit-checklist require a spec-kit project structure?▼

Yes, it requires a .specify directory with the check-prerequisites PowerShell script and the checklist template. It reads feature documents from the FEATURE_DIR path returned by that script.

Can I run the checklist command multiple times on the same feature?▼

Yes, repeated runs append new items to the existing domain file, continuing CHK numbering from the last item. Existing content is never deleted or replaced, and new items are always left unchecked for the reviewer.

Why should checklist items not be marked as complete by the generator?▼

Checkbox state belongs to the reviewer, since [x] means a human confirmed the requirements-quality criterion is satisfied. The Skill only generates or appends items and must leave every new item unchecked.