speckit-checklist

Generate requirements-quality checklists from feature specifications.

4|Updated Apr 4, 2026
One-click install
npx skills add https://github.com/ghbvf/gocell --skill speckit-checklist-ghbvf
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-checklist
Source: https://github.com/ghbvf/gocell/tree/main/.claude/skills/speckit-checklist
Command: npx skills add https://github.com/ghbvf/gocell --skill speckit-checklist-ghbvf

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Speckit-checklist automatically generates structured quality checklists from feature specifications, helping teams validate the quality of written requirements and catch gaps early.

Core Features & Use Cases

  • Generates unit-test-for-requirements style checklists focused on completeness, clarity, consistency, measurability, coverage, and edge cases.
  • Reads spec-kit project structure (e.g., .specify/) and loads context selectively from spec/plan/tasks to tailor prompts and checks.
  • Produces per-domain checklists (ux, api, security) and appends to existing files, preserving history.

Quick Start

Apply this skill to generate a tailored requirements-quality checklist from the current feature specification.

Frequently Asked Questions about speckit-checklist

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

FAQPage Schema
How do I validate the quality of feature requirements before implementation?

You validate feature requirements by generating structured quality checklists from your specifications to catch gaps early. This enforces completeness, clarity, consistency, and measurability before development begins.

What is a requirements quality checklist and what does it cover?

A requirements quality checklist is a validation mechanism that objectively assesses written specs. It covers completeness, clarity, consistency, measurability, coverage, edge cases, non-functional requirements, dependencies, and traceability.

How do I generate per-domain checklists for UX, API, and security from a spec?

You generate per-domain checklists by reading the spec-kit project structure and selectively loading context. It tailors prompts to produce checks for specific domains like UX, API, and security while preserving file history.

Does this checklist generation work with spec-kit project structures?

Yes, it works with spec-kit project structures by reading directories like .specify/. It selectively loads context from spec, plan, and tasks to tailor the generated requirement quality checks accurately.

When do I need an objective quality gate for user stories and PRDs?

You need an objective quality gate when teams produce PRDs, specs, or user stories and require validation before implementation. It enforces requirement completeness, clarity, and traceability to prevent downstream development gaps.