# speckit.checklist

speckit.checklist builds a checklist for reviewing feature requirements, including unclear statements and missing scenarios. Use it before implementing a feature or reviewing its spec.

- command · `type=command` · Claude Code, Codex, GitHub Copilot, Gemini CLI · ★ 117 repo stars
- Author: Chat2AnyLLM
- License: not stated · policy=link-only · description only; the file stays with the author
- Source: https://github.com/Chat2AnyLLM/awesome-claude-plugins/tree/HEAD/.claude/commands/speckit.checklist.md
- Updated: 2026-10-29
- Security check: automated, 2026-11-16 (text) — no signs of malicious code found.
- HTML: https://affpapa.org/en/nevibecode/commands/speckitchecklist

## What it does

The command starts by running `.specify/scripts/bash/check-prerequisites.sh --json`. It then reads relevant sections from `spec.md` and, when present, `plan.md` and `tasks.md`. It can ask focused questions about the checklist’s scope and intended reader; if a conversation is not possible, it follows the provided fallback choices.

The checklist goes into `FEATURE_DIR/checklists/`, with numbered items and a short topic-based filename. It assesses whether requirements are complete, clear, consistent and measurable, and whether scenarios are covered. It reviews the requirements themselves, not whether the finished code behaves correctly. The command relies on the feature directory and available-document list returned by the prerequisite script to locate project context.

## Install

### Claude Code (native platform)

**Manually: put the files in place**
- File: `.claude/commands/speckit.checklist.md` — Call it with /speckit.checklist. For all projects use ~/.claude/commands/

### Codex

**Manually: put the files in place**
- File: `~/.codex/prompts/speckit.checklist.md` — Call it with /prompts:speckit.checklist. Codex marks this format deprecated in favour of skills

### GitHub Copilot

**Manually: put the files in place**
- File: `.github/prompts/speckit.checklist.prompt.md`

### Gemini CLI

**Manually: put the files in place**
- File: `.gemini/commands/speckit.checklist.toml` — Gemini stores commands as TOML: the prompt text goes into the prompt field

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/Chat2AnyLLM/awesome-claude-plugins/tree/HEAD/.claude/commands/speckit.checklist.md

## When to use it
- spot missing feature requirements
- clarify ambiguous statements in a spec
- check whether acceptance criteria are measurable
- find scenarios or edge cases the spec does not cover

## Example prompts
- Create a checklist to review the requirements for this feature.
- Check whether the spec gives reviewers measurable acceptance criteria.
- List unclear scenarios and scope boundaries in the feature requirements.

## Similar
- [speckit-checklist](https://affpapa.org/en/nevibecode/skills/speckit-checklist.md) — skill · 1600 installs
- [speckit.clarify](https://affpapa.org/en/nevibecode/prompts/speckitclarify.md) — prompt · ★ 110 repo stars
- [speckit-analyze](https://affpapa.org/en/nevibecode/skills/speckit-analyze.md) — skill · 1600 installs
- [design-qa-checklist](https://affpapa.org/en/nevibecode/skills/design-qa-checklist.md) — skill · 2600 installs
- [launch-checklist](https://affpapa.org/en/nevibecode/skills/launch-checklist.md) — skill · 1700 installs
- [k2f-checklist](https://affpapa.org/en/nevibecode/skills/k2f-checklist.md) — skill · 681 installs

From the same set: [chat2anyllm/awesome-claude-plugins](https://affpapa.org/en/nevibecode/by/chat2anyllm/awesome-claude-plugins.md) — 9 cards

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md
