speckit-checklist

Generate a requirements-quality checklist for spec-kit feature specifications.

Updated Mar 16, 2026
One-click install
npx skills add https://github.com/B0yZ4kr14/OrthoPlus-Enterprise --skill speckit-checklist-b0yz4kr14
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-checklist
Source: https://github.com/B0yZ4kr14/OrthoPlus-Enterprise/tree/main/.specify-backups/20260518-141826/_agents/skills/speckit-checklist
Command: npx skills add https://github.com/B0yZ4kr14/OrthoPlus-Enterprise --skill speckit-checklist-b0yz4kr14

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you turn feature specifications into measurable “unit tests” for requirement-writing quality, so gaps, ambiguities, conflicts, and missing edge cases are caught early.

Core Features & Use Cases

  • Requirement-quality checklist generation: Produces a structured checklist that evaluates whether the spec is complete, clear, consistent, and measurable.
  • Scenario and edge-case coverage: Validates that primary, alternate, exception/error, recovery, and non-functional requirements are covered and not accidentally omitted.
  • Traceability-focused items: Encourages each checklist item to reference spec sections (or mark [Gap]/[Ambiguity]/[Conflict]/[Assumption]) to support review workflows.

Quick Start

Run speckit-checklist from your repo’s spec-kit context to generate and append a new checklist for the current feature based on your requirements input.

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 completeness and clarity before development?

You validate feature specification completeness by generating a requirements-quality checklist that evaluates clarity, consistency, and acceptance-criteria measurability to catch gaps and ambiguities early.

What is the best way to ensure scenario and edge-case coverage in spec-kit projects?

To ensure scenario and edge-case coverage, you can generate a checklist that validates primary, alternate, exception, recovery, and non-functional requirements are fully covered within your feature specification.

How do I maintain requirements traceability across spec.md, plan.md, and tasks.md files?

You maintain requirements traceability by generating checklist items that reference specific spec section IDs, or by using [Gap], [Ambiguity], [Conflict], and [Assumption] markers to flag missing or conflicting details.

Can I execute custom extension hooks when generating a requirements checklist?

Yes, you can execute custom extension hooks during checklist generation if your spec-kit project defines them within the .specify/extensions.yml configuration file in your repository.

Does requirements traceability validation work without a .specify directory structure?

No, requirements traceability validation requires a spec-kit project context using the .specify directory structure to read feature context from spec.md, plan.md, and tasks.md files.