speckit-checklist

Generate domain-focused quality checklists to validate feature requirements.

Updated Apr 29, 2026

Search Tags:#checklist #specification #requirements #validation #quality #review #traceability

Ready to run

npx skills add https://github.com/Pacheco95/marketplace --skill speckit-checklist-pacheco95

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: speckit-checklist
Source: https://github.com/Pacheco95/marketplace/tree/main/.claude/skills/speckit-checklist
Command: npx skills add https://github.com/Pacheco95/marketplace --skill speckit-checklist-pacheco95

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Generates a focused, high-quality checklist that evaluates feature requirements for completeness, clarity, and traceability, helping teams avoid ambiguous specs and miscommunications.

Core Features & Use Cases

Generate a structured, domain-specific checklist focused on requirements quality, not implementation.
Surface gaps in scope, edge cases, acceptance criteria, and non-functional aspects.
Provide guidance on traceability and formatting to align with spec-driven workflows.
Example use case: during feature scoping, PR reviews, or discovery workshops, teams use the skill to assemble a checklist that validates requirements before engineering begins.

Quick Start

Generate a concise domain-focused requirements checklist for the current feature.

Frequently Asked Questions about speckit-checklist

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

FAQPage Schema

How do I create a requirements validation checklist for feature scoping?▼

To validate feature requirements before engineering begins, generate a domain-focused checklist that evaluates specifications for completeness, clarity, consistency, and traceability. This process surfaces gaps in scope, edge cases, and acceptance criteria.

What is requirements traceability and when do I need it during PR reviews?▼

Requirements traceability ensures every feature specification maps to a clear validation point. You need it during PR reviews and discovery workshops to confirm requirements remain complete, testable, and consistent with the original scope.

How do I check if my feature specifications are complete and testable?▼

Check if feature specifications are complete and testable by applying a structured requirements checklist during scoping or discovery workshops. This validates clarity and consistency while providing guidance on non-functional considerations and edge cases.

Can I use a requirements checklist to find gaps in non-functional considerations?▼

Yes, you can use a requirements checklist to find gaps in non-functional considerations. Generating a domain-focused checklist surfaces ambiguities in scope and provides specific guidance on non-functional aspects to ensure requirements quality.

What is the best way to validate requirements quality without focusing on implementation?▼

The best way to validate requirements quality without focusing on implementation is to generate a domain-specific checklist. It evaluates specifications for completeness, clarity, and traceability, ensuring requirements are testable and formatted for spec-driven workflows.

Why does my feature specification have ambiguous acceptance criteria during discovery workshops?▼

Feature specifications have ambiguous acceptance criteria when they lack a structured validation process. Generating a requirements checklist during discovery workshops surfaces these gaps and ambiguities, ensuring criteria are complete, clear, and testable.