speckit-checklist

Generate requirement unit-test checklists from feature specifications.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It converts a feature’s user requirements into a structured checklist you can use to validate whether the specification is complete, clear, consistent, and measurable—before anyone implements it.

Core Features & Use Cases

  • Requirement quality validation: Identifies gaps in completeness, clarity, consistency, coverage, measurability, and edge-case handling.
  • Scenario-focused coverage: Ensures primary, alternate, exception/error, recovery, and non-functional dimensions are addressed.
  • Traceability-first output: Encourages checklist items to reference the spec sections, or explicitly mark gaps, ambiguities, conflicts, or assumptions.

Quick Start

Generate a checklist for the current feature by running speckit-checklist in your repo context with your feature intent provided as arguments.

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 testable checklist from a feature specification?

Generating a testable checklist from a feature specification involves analyzing spec, plan, and tasks content alongside your feature intent. The tool produces an append-safe checklist file validating requirement quality across UX, API, and security dimensions.

What is requirement quality validation for feature specifications?

Requirement quality validation is the process of identifying gaps in completeness, clarity, consistency, and measurability within a feature specification. It ensures edge-case handling and scenario coverage are addressed before implementation begins.

How do you ensure traceability in requirement acceptance criteria?

Traceability in requirement acceptance criteria is achieved by linking checklist items directly to spec sections. The checklist explicitly marks any identified gaps, ambiguities, conflicts, or assumptions for further review.

Does generating a requirement checklist work for non-functional and scenario coverage?

Generating a requirement checklist works for non-functional and scenario coverage by validating primary, alternate, exception, error, and recovery dimensions. It ensures your specification addresses both functional paths and non-functional requirements.

What are the limitations of automated requirement quality checklists?

Automated requirement quality checklists rely on the provided spec content and user-defined intent. They cannot infer unstated business logic or external constraints, marking them as assumptions or gaps rather than resolving them automatically.