speckit-checklist

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

Updated Sep 12, 2026
One-click install
npx skills add https://github.com/AndyRace/heart-rate-graph --skill speckit-checklist-andyrace
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-checklist
Source: https://github.com/AndyRace/heart-rate-graph/tree/main/.github/skills/speckit-checklist
Command: npx skills add https://github.com/AndyRace/heart-rate-graph --skill speckit-checklist-andyrace

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 custom checklists that act as unit tests for requirements, validating the quality of your feature specifications before coding begins. ## Core Features & Use Cases - Requirements Quality Validation: Generates checklist items that test completeness, clarity, consistency, measurability, and coverage of requirements rather than implementation behavior. - Dynamic Clarification: Derives up to three contextual clarifying questions from your input and spec signals to calibrate checklist focus, depth, and audience. - Append-Safe File Management: Creates or appends to domain-specific checklist files (e.g., ux.md, security.md) in the feature's checklists directory with globally incrementing CHK IDs. - Use Case: Before implementing a new API feature, run this Skill to produce an api.md checklist confirming that error response formats, rate limits, and authentication requirements are fully specified in the spec. ## Quick Start Ask the agent 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 feature spec?

Invoke the speckit-checklist command with your focus area, such as security or UX. The Skill reads your spec.md, plan.md, and tasks.md, asks clarifying questions, then creates or appends to a checklist file in the feature's checklists directory.

What makes a requirements checklist different from a test plan?

A requirements checklist tests the quality of the written requirements themselves, asking whether items are complete, clear, and measurable. It never verifies implementation behavior like button clicks or API responses, which belong to QA test plans.

Does speckit-checklist work without a spec-kit project structure?

No, it requires a spec-kit project with a .specify directory containing the check-prerequisites script and checklist template. It also reads feature documents like spec.md from the feature directory resolved by that script.

Can I create multiple checklists for the same feature?

Yes, each invocation uses a short domain-based filename like ux.md, api.md, or security.md. If the file already exists, new items are appended with continuing CHK IDs rather than replacing existing content.

Why are generated checklist items left unchecked?

Checklists are reviewer-owned artifacts where a checked box means the reviewer confirmed the requirement quality criterion is satisfied. The generating agent must not mark items complete, since that judgment belongs to the human reviewer.