speckit-checklist

Generates a domain-specific quality checklist from spec.md, plan.md, and tasks.md.

22|4|Updated Oct 28, 2025
One-click install
npx skills add https://github.com/ivfarias/ceo --skill speckit-checklist-ivfarias
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-checklist
Source: https://github.com/ivfarias/ceo/tree/main/.gemini/skills/speckit-checklist
Command: npx skills add https://github.com/ivfarias/ceo --skill speckit-checklist-ivfarias

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Speckit-Checklist helps ensure requirements quality by producing a focused checklist that validates specification quality rather than implementation details.

Core Features & Use Cases

  • Clarifies intent and stakeholders for a feature
  • Loads context from spec.md, plan.md, and tasks.md to tailor the checklist
  • Generates a "unit tests for requirements" style checklist with domain-specific items
  • Creates a unique filename based on the feature domain for traceability
  • Validates that the checklist pattern aligns with the Speckit workflow

Quick Start

Run check-prerequisites.sh to locate feature artifacts and generate a domain-specific requirements quality checklist.

Frequently Asked Questions about speckit-checklist

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

FAQPage Schema
How do I validate feature specification quality from spec.md and tasks.md files?

A requirements quality checklist serves as unit tests for your requirements, validating specification completeness, clarity, and consistency rather than implementation details, ensuring your feature intent and stakeholder needs are fully captured before development begins.

How do I generate a domain-specific checklist for feature validation workflows?

You can generate a domain-specific checklist by running the prerequisite script to locate your feature artifacts, which then computes a tailored validation set based on the specific domain extracted from your specification files and outputs a traceable markdown file.

Do I need a Speckit workflow to use requirements quality checklists?

Unlike implementation testing, a requirements checklist validates specification quality by focusing on feature intent and stakeholder clarity, producing domain-specific checks that verify completeness and consistency across multiple planning artifacts rather than testing code behavior.

What limitations exist when validating requirements across multiple markdown artifacts?

Yes, a requirements checklist creates a unique filename based on the feature domain, ensuring traceability across your product development workflow and allowing teams to track validation coverage for each specific feature specification independently.