speckit-checklist

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

1|Updated Jul 10, 2026
One-click install
npx skills add https://github.com/360org/vuaassistant --skill speckit-checklist-360org
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: speckit-checklist
Source: https://github.com/360org/vuaassistant/tree/main/.agents/skills/speckit-checklist
Command: npx skills add https://github.com/360org/vuaassistant --skill speckit-checklist-360org

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing software requirements often leaves gaps, ambiguities, and inconsistencies that only surface during implementation. This Skill generates structured checklists that act as unit tests for your requirements, validating completeness, clarity, consistency, and measurability before coding begins. ## Core Features & Use Cases - Requirements Quality Validation: Produces checklist items that test whether requirements are complete, unambiguous, consistent, and measurable rather than testing implementation behavior. - Domain-Focused Checklists: Creates separate files like ux.md, api.md, security.md, or performance.md inside the feature's checklists directory, appending to existing files with continuous CHK numbering. - Interactive Clarification: Derives up to three contextual clarifying questions from the spec, plan, and tasks documents to calibrate scope, depth, and audience before generation. - Use Case: After drafting a feature spec with spec-kit, run the checklist command with a focus area like security to produce a reviewer-ready gate confirming every authentication, data protection, and failure-response requirement is documented. ## 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 checklist command with a domain focus such as ux, api, or security. The skill reads spec.md, plan.md, and tasks.md from the feature directory, asks up to three clarifying questions, then writes CHK-numbered items into a domain-named file under the checklists folder.

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

It is a set of unit tests for requirements writing that checks whether specifications are complete, clear, consistent, and measurable. Items ask questions like whether vague terms are quantified or edge cases are documented, rather than verifying implementation behavior.

Does the checklist skill work without a .specify directory?▼

No, the skill requires a spec-kit project structure with a .specify directory containing scripts, templates, and the feature folder. It runs check-prerequisites.sh to resolve the feature directory and available documents before generating anything.

What happens when a checklist file already exists?▼

The skill appends new items to the existing file, continuing the CHK numbering from the last item. It never deletes or replaces existing checklist content, so multiple runs accumulate items safely.

Why should checklist items avoid words like verify or test?▼

Items starting with verify, test, or confirm check implementation behavior instead of requirements quality. The checklist validates what is written in the spec, so items must ask whether requirements are defined, quantified, or consistent.