speckit-checklist

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

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing clear, complete, and testable requirements is hard, and gaps or ambiguities in specs surface late as costly rework. This Skill generates a custom checklist that acts as unit tests for your requirements, validating completeness, clarity, consistency, and coverage before implementation begins. ## Core Features & Use Cases - Requirements Quality Validation: Produces checklist items that test whether requirements are well-written, measurable, and unambiguous rather than testing implementation behavior. - Context-Aware Generation: Reads spec.md, plan.md, and tasks.md from the spec-kit feature directory and asks up to three clarifying questions to tailor focus areas, depth, and audience. - Traceable, Appendable Output: Creates or appends to domain-named checklist files (e.g., ux.md, security.md) with CHK-numbered items carrying traceability markers like [Gap], [Ambiguity], and [Spec §X.Y]. - Use Case: Before handing a feature spec to developers, run the checklist generator to produce a security.md checklist confirming that authentication, data protection, and breach-response requirements are fully specified. ## Quick Start Ask the assistant to generate a requirements-quality checklist for the current feature, optionally specifying a focus domain such as UX, API, performance, or security.

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 an optional focus domain such as ux, api, security, or performance. The skill reads spec.md, plan.md, and tasks.md from the feature directory, asks up to three clarifying questions, then writes a CHK-numbered checklist 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 that validates whether specifications are complete, clear, consistent, and measurable. Items ask questions like whether vague terms are quantified or edge cases are addressed, rather than testing whether the implementation works.

Does the checklist skill test my code or implementation?▼

No, it explicitly prohibits implementation-testing items such as verifying clicks or API responses. Every checklist item evaluates the written requirements themselves for completeness, clarity, consistency, measurability, and scenario coverage.

What project structure does the checklist generator require?▼

It requires a spec-kit project with a .specify/ directory containing the check-prerequisites.sh script and a feature directory holding spec.md, and optionally plan.md and tasks.md. It also reads .specify/memory/constitution.md and extensions.yml hooks when present.

Can I create multiple checklists for the same feature?▼

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