speckit-checklist

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

2|Updated Jun 22, 2026
One-click install
npx skills add https://github.com/Kemetra/Seshat-BI --skill speckit-checklist-kemetra
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: speckit-checklist
Source: https://github.com/Kemetra/Seshat-BI/tree/main/.claude/skills/speckit-checklist
Command: npx skills add https://github.com/Kemetra/Seshat-BI --skill speckit-checklist-kemetra

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 domain-focused checklists that act as unit tests for requirements, validating completeness, clarity, consistency, and measurability before coding begins. ## Core Features & Use Cases - Requirements Quality Checklists: Generates CHK-numbered checklist items that test whether requirements are well-written, not whether the implementation works. - Dynamic Clarification: Derives up to three contextual clarifying questions from the user's phrasing and feature documents to calibrate scope, depth, and audience. - Spec-Kit Integration: Reads spec.md, plan.md, and tasks.md from the feature directory, supports extension hooks, and appends to existing checklists with continuing IDs. - Use Case: Before implementing a new API feature, run the checklist generator with a security focus to produce security.md containing items like "Are rate limiting requirements quantified with specific thresholds?" ## Quick Start Ask the assistant to generate a security-focused 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 or focus area, such as security or UX. It reads spec.md, plan.md, and tasks.md from the feature directory, asks clarifying questions if needed, and writes a checklist file like security.md into the feature's checklists folder.

What is a requirements quality checklist in spec-kit?▼

It is a set of unit tests for requirements writing. Each item questions whether requirements are complete, clear, consistent, and measurable, rather than verifying that the implementation works. Items use CHK IDs and markers like [Gap], [Ambiguity], or [Spec §X.Y].

Does speckit-checklist work without a .specify directory?▼

No. The skill requires a spec-kit project structure with a .specify directory, since it runs the check-prerequisites script and reads feature documents from the resolved FEATURE_DIR path.

Can I create multiple checklists for the same feature?▼

Yes. Each invocation uses a short domain-based filename such as ux.md, api.md, or security.md. If the file already exists, new items are appended with continuing CHK numbers instead of overwriting existing content.

Why does the checklist avoid items like verify or test the implementation?▼

The checklist validates requirement quality, not system behavior. Items starting with verify, test, or confirm check whether code works, which belongs in QA. This skill only asks whether requirements are specified, quantified, and consistent.