speckit-checklist

Yes, you can create review checklists for UX, API, security, and performance domains. The checklist generation evaluates written requirements to identify missing scenario coverage and acceptance issues specific to your chosen review workflow.

A spec quality checklist is used to turn vague or incomplete feature requirements into structured evaluations that expose conflicts and missing acceptance criteria. It helps teams identify unclear requirements before implementation moves forward.

Checklist generation handles gaps in acceptance criteria by analyzing feature spec, plan, and task documents to produce traceable checklist items with section references or gap markers. It identifies measurable acceptance issues and missing scenario coverage.

Yes, checklist generation works with existing plan and task documents by using spec-aware review support to evaluate requirement quality. It reads the .specify project context to generate traceable checklist items based on your governance context.

You need to answer clarifying questions before generating a requirements checklist because an adaptive clarification flow tunes the checklist scope, depth, risk emphasis, and audience. This ensures the generated checklist focuses on your specific requirements review needs.