spec-kit-checklist

Classify incomplete specs and plans by severity and emit gap reports.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/CLOCKWORK-TEMPTATION/plugin_01UphfxAg16yZB4YodKYf1RZ --skill spec-kit-checklist-clockwork-temptation
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spec-kit-checklist
Source: https://github.com/CLOCKWORK-TEMPTATION/plugin_01UphfxAg16yZB4YodKYf1RZ/tree/main/skills/spec-kit-checklist
Command: npx skills add https://github.com/CLOCKWORK-TEMPTATION/plugin_01UphfxAg16yZB4YodKYf1RZ --skill spec-kit-checklist-clockwork-temptation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps ensure specs or plans are complete before proceeding, and routes unresolved gaps to the appropriate specialists to close them efficiently.

Core Features & Use Cases

  • Gap classification: categorize gaps by severity and downstream impact.
  • Safe auto-healing: fix only what is safe from context or approved research outputs.
  • Transparent reporting: emit gap reports that distinguish fixed, skipped, and manual-followup items.
  • Apply this in product workflow reviews to prevent stalled work and improve traceability.

Quick Start

Check a spec or plan for completeness and route gaps to the appropriate specialist.

Frequently Asked Questions about spec-kit-checklist

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I validate specs and plans for completeness before sprint planning?

To validate specs and plans, identify incomplete sections and classify gaps by severity to guide prioritization. This ensures your specs are complete before proceeding and routes unresolved gaps to appropriate specialists.

What is severity-based gap classification in product development reviews?

Severity-based gap classification categorizes spec and plan gaps by their downstream impact to guide prioritization. It helps distinguish which gaps are safe to auto-heal from context and which require manual follow-up during governance checkpoints.

Can I use spec gap analysis for governance checkpoints and workflow reviews?

Spec gap analysis applies during product development reviews, sprint planning, and governance checkpoints to evaluate specs and plans. It prevents stalled work and improves traceability by routing unresolved gaps to appropriate specialists.

What's the best way to route unresolved spec gaps to specialists?

The best way to route unresolved spec gaps is to classify them by severity and downstream impact, then emit gap reports that distinguish fixed, skipped, and manual follow-up items. This guides specialists to close gaps efficiently.

Why does spec validation skip some gaps instead of fixing them?

Spec validation skips gaps because safe auto-healing constraints only fix what is safe from context or approved research outputs. Gaps requiring manual intervention are flagged in the gap report for specialist follow-up.