speckit-checklist

To generate a requirement quality checklist, provide the feature directory containing your spec.md, plan.md, and tasks.md files to automatically derive unit-test-like checks evaluating completeness, clarity, consistency, coverage, and edge cases.

A specification checklist provides unit-test-like items that evaluate written requirements rather than implementation details, using traceability references to link each generated check directly to relevant spec sections for alignment and review readiness.

Yes, you can append new checklist items to existing domain-based files without overwriting prior content, preserving previous checks while adding new items with unique CHK### item IDs to maintain a continuous requirements quality audit trail.

No, the checklist generator specifically evaluates the quality of written requirements rather than implementation details, analyzing spec.md, plan.md, and tasks.md files to produce focused checks preventing gaps and ambiguities before coding begins.

The best way to organize requirement checklists is using a centralized FEATURE_DIR/checklists/ folder, creating domain-based files like ux.md and api.md to categorize unit-test-like quality checks by specific feature domains.

You need to prepare a feature directory containing structured spec.md, plan.md, and tasks.md files as input data, ensuring written requirements exist so the tool can analyze them and produce focused checklist items.