checklist

Generating a QA checklist involves parsing spec.md, plan.md, and tasks.md documents to extract validation criteria and merging acceptance criteria into prd.json. The skill automates this to produce a structured Markdown checklist saved to the designated feature path.

Quality gates and TDD items are mandatory validation sections enforced within every generated checklist to ensure routing compliance and test-driven development across feature workflows. They provide structured, auditable criteria for validating feature readiness before release.

Yes, you can use this skill with existing prd.json files. It specifically merges acceptance criteria from your spec, plan, and tasks documents directly into prd.json, ensuring your product requirements stay synchronized with the generated validation checklist.

To organize feature validation checklists by domain, the skill automatically creates a feature-scoped checklist with 7-10 categories tailored to the specific domain. This ensures the generated checklist covers all relevant validation areas for the feature.

No, the checklist skill does not require any dependencies to run. It operates independently to parse your spec, plan, and tasks documents and output the final Markdown checklist to the relentless/features/NNN-feature/checklist.md path.

The best way to automate quality validation checklist creation is to run the skill after creating your tasks. It automatically reads the feature documents, enforces TDD and quality gates, and saves the generated checklist to the designated feature path for easy traceability.