speckit-checklist

Generate unit-test style checklists to validate feature requirements.

4|11|Updated Dec 14, 2025
One-click install
npx skills add https://github.com/Obsidian-Owl/floe --skill speckit-checklist-obsidian-owl
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-checklist
Source: https://github.com/Obsidian-Owl/floe/tree/main/.claude/skills/speckit-checklist
Command: npx skills add https://github.com/Obsidian-Owl/floe --skill speckit-checklist-obsidian-owl

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Requirements written for features are often vague or incomplete. speckit-checklist generates quality validation artifacts in the form of unit-test style checklists that ensure requirements are complete, clear, and traceable.

Core Features & Use Cases

  • Generates Unit-Test style checklists that assess requirement completeness, clarity, consistency, and traceability.
  • Guides mapping of checklist items to spec sections and defined terms to support traceability.
  • Creates new checklists under the FEATURE_DIR/checklists/ directory with a domain-based, unique filename and appends to existing files when appropriate.

Quick Start

Run the speckit-checklist skill to generate a new requirements-quality checklist for your feature.

Frequently Asked Questions about speckit-checklist

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

FAQPage Schema
How do I turn feature requirements into unit tests for validation?

You can turn feature requirements into unit tests by generating structured, unit-test style checklists that assess requirement completeness, clarity, consistency, and traceability. This validates that specifications are unambiguous and fully defined.

What is a unit-test style checklist for feature specifications?

A unit-test style checklist is a quality validation artifact that checks if requirements are complete, clear, and traceable. It maps checklist items directly to spec sections and defined terms to support rigorous traceability across the feature plan.

How do I generate requirement checklists and where are they stored?

To generate requirement checklists, run the skill against your feature specifications. It creates new checklists under the FEATURE_DIR/checklists/ directory, applying a canonical template with domain-based, unique filenames and appending to existing files when appropriate.

Does this checklist approach work with existing feature plans and specifications?

Yes, this checklist approach works directly with existing feature specifications and plans. It validates that your current requirements are complete, unambiguous, and traceable across all sections without requiring additional dependencies.

How do I ensure traceability across my feature specification sections?

You ensure traceability by mapping generated checklist items to specific spec sections and defined terms. This guided mapping process validates that every requirement is consistently tracked and accounted for across the entire specification.