skills.rest
ldilov
ldilovCOMMUNITY
Explore all skills by this author →
GitHub

speckit-checklist

Generate structured requirement quality checklists from SPEC-kit documentation.

3|Updated Mar 24, 2026
Search Tags:#documentation#checklist#specification#requirements#qa#quality#speckit
One-click install
npx skills add https://github.com/ldilov/harness-forge --skill speckit-checklist-ldilov
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: speckit-checklist
Source: https://github.com/ldilov/harness-forge/tree/main/.agents/skills/speckit-checklist
Command: npx skills add https://github.com/ldilov/harness-forge --skill speckit-checklist-ldilov

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Converts natural-language requirements into structured, test-focused checklists to validate the quality of software requirements rather than implementations.

Core Features & Use Cases

  • Generates unit-tests for requirements quality (Completeness, Clarity, Consistency, Measurability, Coverage)
  • Loads SPEC-kit style documentation from a feature directory (.specify) and progressively discloses relevant content (spec.md, plan.md, tasks.md)
  • Creates or appends to checklists under checklists/ while preserving existing items

Quick Start

Run the speckit-checklist command from the repository root to generate a new requirement quality checklist for the active feature.

Frequently Asked Questions about speckit-checklist

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

FAQPage Schema
Can I append new checklist items to existing files without losing previous requirements?▼

Yes, you can append new requirement quality checklist items to existing files under the checklists/ directory. The tool preserves your existing checklist entries while adding newly generated items focused on consistency, measurability, and coverage.

Do I need a .specify directory to use the SPEC-kit checklist generation?▼

A specification quality checklist validates software requirements rather than implementations, covering completeness, clarity, consistency, measurability, coverage, edge cases, and non-functional areas. It converts natural-language requirements into structured, test-focused validation items.

What's the best way to validate software requirements quality for non-functional areas?▼

Yes, you need a .specify directory containing spec.md, plan.md, and tasks.md files to use the SPEC-kit checklist generation. The tool targets SPEC-kit style projects and progressively loads these files to focus on specific quality axes.

Why does my generated checklist not include items for edge cases?▼

The best way to validate software requirements quality for non-functional areas is using an automated checklist generator that ensures canonical template adherence. It systematically converts natural-language specifications into structured checklist items covering non-functional requirements.

Why does my generated checklist not include items for edge cases?▼

Your generated checklist might miss edge case items if your feature documentation in spec.md, plan.md, or tasks.md lacks sufficient detail. The tool extracts requirement quality axes from these files to ensure checklist items comprehensively cover edge cases and non-functional areas.

Related Skills

Explore More Software Engineering Skills→
AhmedMohammedSaadAhmedMohammedSaad

speckit-checklist

Generate a structured markdown checklist from spec-kit feature specification files.

Community
Intermediate
AustinZ21AustinZ21
4

speckit-checklist

Generate custom checklists to validate feature requirement quality in spec-kit projects.

Community
Advanced
estaciolimaestaciolima

speckit-specify

Generate structured feature specifications from natural language descriptions.

Community
Advanced
ztwosoneztwosone

speckit-checklist

Generate structured checklists validating software requirements document quality.

Community
Advanced