Generate requirement-quality checklists from spec.md with traceability markers.
npx skills add https://github.com/ahgraber/skills --skill spec-kit-checklist
Please help me install this Agent Skill. Skill: spec-kit-checklist Source: https://github.com/ahgraber/skills/tree/main/skills/spec-kit-checklist Command: npx skills add https://github.com/ahgraber/skills --skill spec-kit-checklist
Spec Kit features often lack a structured, testable requirements quality gate. This skill provides a systematic approach to generate domain-specific checklists that evaluate clarity, completeness, consistency, measurability, and coverage of spec artifacts.
Describe the feature's spec.md and run the checklist generator to create a new checklist file under specs/<feature>/checklists/.
High-intent search queries and answers about installing and using this skill.
To generate a requirements quality checklist, provide the feature's spec.md file and optionally plan.md or tasks.md. The tool analyzes these artifacts to surface ambiguity, gaps, and measurable acceptance criteria, outputting a new checklist file under specs/<feature>/checklists/.
A requirements quality checklist evaluates the clarity, completeness, consistency, measurability, and coverage of spec artifacts. It systematically identifies ambiguity, missing coverage, and conflicting or vague requirements within the provided documentation.
You trace requirement gaps and ambiguity by generating a checklist with traceability markers. The tool anchors checklist items to specific artifacts using tags like [Spec §], [Gap], [Ambiguity], [Conflict], and [Assumption] for clear tracking.
No, you cannot include runtime tests in a Spec Kit requirements checklist. The generated checklist specifically focuses on requirement quality and traceability, explicitly ensuring that no runtime tests are included in the output file.
No, you do not need plan.md and tasks.md to create a requirements checklist. While the tool can analyze these optional files alongside spec.md to provide deeper insights, only spec.md is required to generate the quality checklist.
Spec Kit features often lack a structured, testable requirements quality gate. Generating a domain-specific checklist provides a systematic approach to evaluate requirement clarity and completeness, ensuring measurable acceptance criteria are established.
burningddolGenerate domain-aligned requirement checklists from spec-kit feature files.
avansoverGenerate requirements-quality checklists with traceability references from spec content.
EzekTec-IncGenerate requirement quality checklists for spec-kit feature workflows.
intent-integrity-chainGenerate domain-specific requirement quality checklists from spec.md, plan.md, and tasks.md.
