spec-checklist

To generate a requirements checklist, run the skill against your feature directory containing spec.md, plan.md, and tasks.md. It analyzes these files to produce a Markdown checklist evaluating completeness, clarity, consistency, coverage, and measurability.

To ensure requirements are testable, use a checklist validation process that evaluates requirement quality across completeness, clarity, consistency, coverage, and measurability. This skill automatically generates focused unit test checklists identifying ambiguities in your specifications.

Yes, generating a requirements checklist preserves existing work. The skill outputs a new or appended Markdown file under specs/<branch>/checklists/ without altering existing content in your source specification documents.

Checklist items are traceable because the skill enforces that each generated item references specific spec sections. It outputs files with incremental CHK IDs under specs/<branch>/checklists/ to maintain strict traceability between tests and requirements.

Yes, you can append new checklist items to an existing file. The skill reads existing feature context and appends incremental CHK IDs to the Markdown checklist located under specs/<branch>/checklists/ without altering previous content.

Before validating requirements, you need feature context files including spec.md, plan.md, and tasks.md in your feature directory. The skill reads these Markdown files to tailor the generated checklist to your current feature.