speckit-checklist

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

Updated Aug 15, 2026
One-click install
npx skills add https://github.com/AhmedRagabRG/academy --skill speckit-checklist-ahmedragabrg
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: speckit-checklist
Source: https://github.com/AhmedRagabRG/academy/tree/main/frontend/.agents/skills/speckit-checklist
Command: npx skills add https://github.com/AhmedRagabRG/academy --skill speckit-checklist-ahmedragabrg

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 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 well-written, measurable, and unambiguous rather than testing implementation behavior. - Domain-Specific Checklists: Creates themed checklists such as 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 to calibrate scope, depth, audience, and risk focus before generation. - Use Case: After drafting a feature spec with spec-kit, run this Skill to produce a security checklist that asks whether authentication requirements cover all protected resources and whether failure responses are specified. ## Quick Start Ask the agent to generate a UX 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 speckit-checklist skill with an optional focus description, such as a security or UX theme. It reads the feature's spec.md, plan.md, and tasks.md, asks clarifying questions if needed, and writes a domain-named checklist file into the feature's checklists directory.

What makes a spec-kit checklist different from a test plan?▼

These checklists test the requirements themselves, not the implementation. Items ask whether requirements are complete, clear, consistent, and measurable, rather than verifying that buttons click or APIs return correct responses.

Does speckit-checklist require a specific project structure?▼

Yes, it requires a spec-kit project with a .specify directory containing scripts like check-prerequisites.sh and a feature directory holding spec.md. Without this structure the prerequisite setup step cannot resolve FEATURE_DIR.

Can I create multiple checklists for the same feature?▼

Yes, each invocation uses a short domain-based filename like ux.md or api.md. If the file already exists, new items are appended with continuing CHK IDs, so existing content is never deleted or replaced.

Why does the skill ask clarifying questions before generating?▼

The questions calibrate scope, depth, audience, and risk focus so the checklist matches your intent. They are derived dynamically from your input and the spec content, and are skipped when the answer is already unambiguous.