speckit-checklist.agent

Generate requirement-focused checklists from feature specifications with traceability references.

1|Updated Nov 20, 2025
One-click install
npx skills add https://github.com/stribus/pygerengastos --skill speckit-checklist-agent-stribus
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-checklist.agent
Source: https://github.com/stribus/pygerengastos/tree/main/.github/skills/speckit-checklist.agent
Command: npx skills add https://github.com/stribus/pygerengastos --skill speckit-checklist-agent-stribus

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Generating high-quality, requirement-focused checklists automatically from feature specs to validate completeness, clarity, and traceability.

Core Features & Use Cases

  • Derives initial clarifying questions to refine scope and risk.
  • Loads feature context from .specify/ directories and feature docs to generate targeted checklists.
  • Creates new, uniquely named checklists under checklists/ with domain-based filenames (e.g., ux.md, api.md), preserving existing checklists.
  • Adheres to a canonical template, with CHKIDs starting from CHK001 and categorization for completeness, clarity, consistency, acceptance criteria, coverage, edge cases, non-functional requirements, dependencies & assumptions, ambiguities & conflicts.
  • Ensures traceability by referencing spec sections or gap markers in checklist items.
  • Supports multiple checklist types per feature, enabling progressive refinement over time.

Quick Start

Provide the feature requirements and run the Speckit agent to generate a new checklist file under checklists/.

Frequently Asked Questions about speckit-checklist.agent

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

FAQPage Schema
How do I generate requirement-focused checklists from feature specifications?

Generate requirement-focused checklists by loading feature context from .specify/ directories and feature docs to automatically create targeted validation lists for completeness, clarity, and traceability. This ensures structured PR reviews and requirements validation.

What is requirement traceability in checklist generation?

Requirement traceability in checklist generation references specific spec sections or gap markers within each checklist item. This ensures every completeness, clarity, and acceptance criteria validation item explicitly links back to the original feature specification.

How do I structure checklists for PR reviews and requirements validation?

Structure checklists for PR reviews using a canonical template with sequential IDs starting from CHK001 and categorization for edge cases, non-functional requirements, and ambiguities. This provides structured requirements validation and explicit traceability references.

Does generating checklists from feature specs overwrite existing validation files?

Generating checklists from feature specs does not overwrite existing files. It creates new, uniquely named checklists under the checklists/ directory with domain-based filenames like ux.md and api.md, preserving existing checklists while supporting progressive refinement.

Can I generate multiple checklist types for a single feature specification?

You can generate multiple checklist types for a single feature specification, enabling progressive refinement over time. The system derives initial clarifying questions to refine scope and risk before creating domain-based checklist files.