speckit-checklist

Generate quality checklists that validate requirements completeness and clarity in spec-kit projects.

Updated Jul 3, 2026
One-click install
npx skills add https://github.com/alex-jordan547/agent-setup --skill speckit-checklist-alex-jordan547
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-checklist
Source: https://github.com/alex-jordan547/agent-setup/tree/main/archive/speckit-checklist
Command: npx skills add https://github.com/alex-jordan547/agent-setup --skill speckit-checklist-alex-jordan547

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Specs written in natural language often contain vague, incomplete, or conflicting requirements that only surface during implementation. This Skill generates structured checklists that act as unit tests for requirements, catching quality issues before coding begins. ## Core Features & Use Cases - Requirements Quality Validation: Produces checklist items that test completeness, clarity, consistency, measurability, and coverage of the spec itself, never the implementation. - Context-Aware Clarification: Derives up to three targeted clarifying questions from the user's phrasing and signals extracted from spec.md, plan.md, and tasks.md. - Traceable Checklist Files: Creates uniquely named files (e.g., ux.md, api.md, security.md) under the feature's checklists directory with sequentially numbered CHK items and spec section references. - Use Case: Before implementing a new feature in a spec-kit project, run the checklist flow to produce a security.md checklist verifying that authentication, data protection, and breach-response requirements are fully specified. ## Quick Start Ask the agent to generate a UX requirements quality checklist for the current feature spec in your spec-kit project.

Frequently Asked Questions about speckit-checklist

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a requirements quality checklist for a spec?

Run the checklist flow inside a spec-kit project; it reads spec.md, plan.md, and tasks.md from the feature directory, asks up to three clarifying questions, then writes a domain-named file like ux.md or security.md under the feature's checklists folder.

What is the difference between a requirements checklist and a test plan?

A requirements checklist tests whether the spec is well-written, complete, and unambiguous, while a test plan verifies whether the implementation works. Checklist items ask questions like whether terms are quantified, never whether buttons click correctly.

Does this checklist skill require a spec-kit project structure?

Yes, it requires a spec-kit project with a .specify directory. It runs check-prerequisites.sh to resolve the feature directory and loads spec.md, plan.md, and tasks.md from there.

Can I generate multiple checklists for the same feature?

Yes, each run creates a new file named by domain such as api.md, performance.md, or security.md in the checklists folder. Existing files are appended to rather than overwritten, so multiple checklist types can coexist.

What makes a good requirements checklist item?

A good item asks whether a requirement is defined, quantified, consistent, or measurable, and includes a quality dimension tag like [Clarity] or [Gap] plus a spec section reference. It never starts with Verify, Test, or Confirm about system behavior.