speckit-checklist

Acceptance criteria measurability is checked by generating scenario-focused checklist items that verify if requirements are clear, consistent, and measurable. It flags ambiguous or conflicting entries with [Ambiguity] or [Conflict] tags.

Requirements traceability is established by generating checklist entries that reference specific spec, plan, and task sections. It validates scenario coverage and marks missing or ambiguous requirements with [Gap] or [Conflict] tags.

Spec-kit structured projects are supported by loading the active feature context including spec, plan, and tasks. It generates scenario-focused requirement items and creates or appends checklist markdown under the feature's checklists directory.

Missing or ambiguous requirements are marked with [Gap], [Ambiguity], or [Conflict] tags within the generated checklist. This highlights where completeness and consistency fail before implementation begins.

Yes, custom extension hooks are supported via a project `.specify/extensions.yml` file. This allows defining pre- and post-checklist generation hooks to integrate additional validation logic into the workflow.