speckit-checklist

Generate quality checklists for spec-kit requirements with traceability references.

Updated Apr 7, 2026
One-click install
npx skills add https://github.com/a2mus/smart-da3m --skill speckit-checklist-a2mus
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-checklist
Source: https://github.com/a2mus/smart-da3m/tree/main/.agents/skills/speckit-checklist
Command: npx skills add https://github.com/a2mus/smart-da3m --skill speckit-checklist-a2mus

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The speckit-checklist skill turns vague or incomplete requirement text into structured quality checklists that reveal gaps in completeness, clarity, consistency, and measurability before implementation. It helps authors and reviewers catch ambiguous language, missing acceptance criteria, and untracked assumptions so specifications are actionable and review-ready.

Core Features & Use Cases

  • Checklist generation: Produce unit-test style checklists that evaluate requirement quality (completeness, clarity, consistency, measurability, coverage) across domains such as UX, API, performance, and security.
  • Context-aware tracing: Load FEATURE_DIR spec.md, plan.md, and tasks.md to reference spec sections, include traceability markers, and prioritize high-risk gaps.
  • Review & author workflows: Use during authoring, PR review, or release gating to create CHK-prefixed files grouped by quality dimension and to highlight ambiguities, assumptions, and missing non-functional requirements.

Quick Start

Use the speckit-checklist skill to generate an 'ux.md' requirements-quality checklist from the feature documents in .specify/FEATURE_DIR.

Frequently Asked Questions about speckit-checklist

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

FAQPage Schema
How do I validate requirement specs for completeness and clarity before implementation?

To validate requirement specs, generate quality checklists that evaluate completeness, clarity, consistency, and measurability across domains like UX, API, and security. This process catches ambiguous language and missing acceptance criteria to make specifications actionable and review-ready.

How do I generate a requirements quality checklist from spec-kit project files?

Generate a requirements quality checklist by applying the skill to a spec-kit project containing .specify/FEATURE_DIR with spec.md, plan.md, and tasks.md. It produces CHK-prefixed checklist files in FEATURE_DIR/checklists/ grouped by quality dimension and domain.

Does requirement checklist generation work with spec.md and plan.md traceability?

Yes, requirement checklist generation works with spec.md and plan.md by loading these documents to include spec section references and traceability markers. This context-aware tracing highlights high-risk gaps and links validation checks directly to the original specification sections.

What is the best way to review written requirements for missing non-functional requirements?

The best way to review written requirements for missing non-functional requirements is to generate domain-specific checklists covering performance and security. These checklists highlight untracked assumptions and missing acceptance criteria during authoring or PR review workflows.

Can I use generated validation checklists for release gating in a feature workflow?

Yes, you can use generated validation checklists for release gating in a feature workflow. The produced CHK-prefixed files evaluate requirement quality across multiple domains, ensuring specifications are complete and measurable before implementation proceeds.