speckit-checklist

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

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing clear, complete, and testable requirements is hard, and gaps or ambiguities in a spec 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: Creates CHK-numbered checklist items grouped by quality dimensions such as completeness, clarity, consistency, coverage, and edge cases, with traceability references to spec sections. - Spec-Kit Integration: Reads the feature's spec.md, plan.md, and tasks.md from the .specify project structure, runs prerequisite scripts, and respects constitution principles and extension hooks. - Interactive Clarification: Derives up to five targeted clarifying questions about scope, depth, audience, and risk before generating the checklist. - Use Case: Before implementing a new API feature, run the checklist command with a security focus to produce security.md in the feature's checklists folder, surfacing gaps like missing rate-limiting or authentication requirements. ## 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 command with an optional focus such as ux, api, security, or performance. The skill reads the feature's spec.md, plan.md, and tasks.md, asks clarifying questions, then creates or appends to a checklist file in the feature's checklists folder.

What makes a good requirements checklist item?

Good items test the requirements themselves, not the implementation. They ask whether requirements are defined, quantified, consistent, and measurable, using markers like [Gap], [Ambiguity], or [Spec §X.Y] for traceability, rather than verifying that code works.

Does speckit-checklist work without a .specify directory?

No, it requires a spec-kit project structure with a .specify directory containing the prerequisite scripts and feature folders. Without that structure, the setup step that resolves FEATURE_DIR and available documents cannot run.

Can I create multiple checklists for the same feature?

Yes, each invocation uses a short domain-based filename like ux.md or security.md in the checklists folder. If the file already exists, new items are appended with continuing CHK IDs instead of overwriting existing content.

Why does the checklist avoid items like 'verify the button works'?

Those items test implementation behavior, not requirement quality. The checklist is designed as unit tests for English requirements, so it checks whether behaviors and edge cases are specified in the spec, not whether the built system performs them.