speckit-checklist

You can validate feature requirements by generating unit-test style checklists that check completeness, clarity, consistency, measurability, and coverage before implementation begins. This structured approach turns informal specifications into measurable validation criteria.

To generate requirement checklists inside a spec-kit project, the Skill reads repository feature context from the .specify directory and writes or appends domain-specific markdown files under FEATURE_DIR/checklists/[domain].md while preserving existing content.

A unit-test style checklist for requirements is a validation mechanism that evaluates written feature specifications for clarity, consistency, and measurability. It ensures high-risk items are prioritized and coverage rules are met before development starts.

Yes, you can append new checklist items without overwriting existing validation files. The Skill preserves existing content and automatically continues CHK IDs when writing or appending to markdown files under the feature directory.

Yes, requirement validation works for specific domains including api, security, performance, and ux. The Skill produces domain-specific checklists tailored to the unique validation rules and coverage needs of each technical area.

To scope requirement checklists for large feature specifications, the Skill dynamically generates up to three targeted clarifying questions. This process prioritizes high-risk items and ensures the output remains focused and manageable.