speckit-checklist

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

Updated Jul 26, 2026
One-click install
npx skills add https://github.com/gkuga/monit-rs --skill speckit-checklist-gkuga
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-checklist
Source: https://github.com/gkuga/monit-rs/tree/main/.claude/skills/speckit-checklist
Command: npx skills add https://github.com/gkuga/monit-rs --skill speckit-checklist-gkuga

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 your requirements, validating completeness, clarity, consistency, and coverage 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. - 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 the checklist to your domain and audience. - Incremental Checklist Files: Creates or appends to domain-named files like ux.md, api.md, or security.md under the feature's checklists folder with sequential CHK identifiers. - Use Case: Before implementing an authentication feature, run the checklist command with a security focus to surface missing requirements such as undefined session timeout behavior or unspecified failure responses. ## Quick Start Ask the assistant to generate a security-focused requirements checklist for the current spec-kit 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 spec-kit feature?

Invoke the checklist command with a domain or focus area as the argument, such as security or ux. The skill reads your feature's spec.md, plan.md, and tasks.md, asks up to three clarifying questions, then writes a checklist file into the feature's checklists directory.

What is a requirements quality checklist versus a test checklist?

A requirements quality checklist tests whether the specification itself is complete, clear, and consistent, 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 require a spec-kit project structure?

Yes, it requires a spec-kit project with a .specify directory. The setup step runs check-prerequisites.sh to resolve the feature directory and available documents, so the command will not work outside that structure.

What happens if the checklist file already exists?

Existing checklist files are never overwritten. New items are appended to the file with CHK identifiers continuing from the last existing number, so running the command multiple times accumulates items safely.

Why does the checklist command ask clarifying questions first?

The questions pin down scope, depth, audience, and risk emphasis so the generated items match your actual intent. Up to three initial questions are derived from your input and the feature documents, and defaults apply if interaction is not possible.