speckit-checklist

To generate a requirements quality checklist, provide a focus area or domain to produce unit-test-like validation items that evaluate spec completeness, clarity, consistency, and measurability. The checklist appends to or creates files under checklists/ for your feature.

Requirements traceability validates acceptance criteria by mapping checklist items to spec section references and explicit gap markers. This ensures scenario coverage, edge cases, and non-functional requirements are tracked back to the original feature requirements.

You check non-functional requirements and edge cases by generating a focused checklist that prompts coverage across these dimensions. The checklist evaluates the spec itself for scenario completeness and ambiguity markers rather than testing implementation behavior.

Yes, you can load feature context from spec/plan/tasks directories. The checklist generation reads this context to validate dependencies and ambiguities, and supports optional pre-hooks from .specify/extensions.yml to customize the validation process.

The best way to find ambiguities and gaps is using traceability-aware checklist validation that flags explicit gap markers and evaluates consistency. This approach treats requirements as unit tests, systematically checking clarity and scenario coverage across the spec.

Yes, speckit-checklist supports optional pre-hooks defined in .specify/extensions.yml for custom spec quality validation. This allows you to tailor the checklist generation process before appending or creating checklist files under checklists/.