speckit.checklist

Generate requirements-quality checklists from feature specs, plans, and tasks.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing good requirements is hard to verify. This Skill generates custom checklists that act as unit tests for your specification documents, validating that requirements are complete, clear, consistent, and measurable before implementation begins. ## Core Features & Use Cases - Requirements Quality Validation: Produces checklist items that test completeness, clarity, consistency, measurability, and coverage of your spec rather than testing implementation behavior. - Context-Aware Generation: Reads spec.md, plan.md, and tasks.md from the current feature directory and asks up to three dynamic clarifying questions to tailor the checklist's focus, depth, and audience. - Traceable Output: Creates a new markdown file in the feature's checklists/ directory with sequentially numbered items (CHK001+) referencing spec sections and gap markers. - Use Case: Before handing a feature spec to developers, run this Skill to produce a security.md or ux.md checklist that surfaces ambiguities, missing edge cases, and undocumented assumptions. ## Quick Start Ask the assistant to run the speckit checklist command with a focus area such as security or UX for the current feature.

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

Run the checklist command with an optional focus area like security, UX, API, or performance. The Skill reads spec.md, plan.md, and tasks.md from the feature directory and writes a new markdown file into the checklists folder with numbered quality items.

What is a requirements quality checklist versus a test checklist?▼

A requirements checklist validates whether the specification itself is complete, clear, and measurable, not whether the implementation works. Items ask questions like whether vague terms are quantified or edge cases are documented, rather than verifying runtime behavior.

Does the checklist command overwrite existing checklist files?▼

No, each run creates a new file named after its domain, such as ux.md or security.md, inside the feature's checklists directory. If a file with that name exists, items are appended rather than overwritten.

What inputs does the checklist generator need?▼

It needs a feature directory containing spec.md, and optionally plan.md and tasks.md, discovered via the check-prerequisites script. You can also pass free-text arguments describing the checklist theme and must-have items.

When should I not use a requirements checklist?▼

Avoid it when you need to verify that code behaves correctly, since the checklist explicitly prohibits implementation-testing items. Use unit tests, integration tests, or QA procedures for behavioral verification instead.