Name: checklist
Author: debate-timer

Prompt file imported from debate-timer/debate-timer-fe (.codex/prompts/checklist.md). Copyright stays with the author.

Generate a custom checklist for the current feature — "unit tests for requirements writing."

Checklists validate the QUALITY of requirements (completeness, clarity, consistency, measurability), NOT implementation behavior.

Steps

Run .specify/scripts/bash/check-prerequisites.sh --json to get FEATURE_DIR
Ask up to 3 clarifying questions about scope, depth, audience
Load spec.md, plan.md (if exists), tasks.md (if exists)
Generate checklist items grouped by: Completeness, Clarity, Consistency, Acceptance Criteria, Scenario Coverage, Edge Cases, Non-Functional, Dependencies
Write to FEATURE_DIR/checklists/{domain}.md (e.g., ux.md, api.md, security.md)

Item Format

Items ask about REQUIREMENT QUALITY, not implementation:
- YES: "Are error handling requirements defined for all API failure modes? [Gap]"
- NO: "Verify the button clicks correctly"
Include traceability: [Spec §X.Y], [Gap], [Ambiguity], [Conflict]
Sequential IDs: CHK001, CHK002, ...

Context

Full workflow details: .claude/commands/speckits/checklist.md

Generate a custom checklist for the current feature — "unit tests for requirements writing." Checklists validate the QUALITY of requirements (completeness, clarity, consistency, measurability), NOT implementation behavior. ## Steps 1. Run `.specify/scripts/bash/check-prerequisites.sh --json` to get FEATURE_DIR 2. Ask up to 3 clarifying questions about scope, depth, audience 3. Load spec.md, plan.md (if exists), tasks.md (if exists) 4. Generate checklist items grouped by: Completeness, Clarity, Consistency, Acceptance Criteria, Scenario Coverage, Edge Cases, Non-Functional, Dependencies 5. Write to `FEATURE_DIR/checklists/{domain}.md` (e.g., `ux.md`, `api.md`, `security.md`) ## Item Format - Items ask about REQUIREMENT QUALITY, not implementation: - YES: "Are error handling requirements defined for all API failure modes? [Gap]" - NO: "Verify the button clicks correctly" - Include traceability: `[Spec §X.Y]`, `[Gap]`, `[Ambiguity]`, `[Conflict]` - Sequential IDs: CHK001, CHK002, ... ## Context - Full workflow details: `.claude/commands/speckits/checklist.md`

{ "prompt": "Generate a custom checklist for the current feature — \"unit tests for requirements writing.\"\n\nChecklists validate the QUALITY of requirements (completeness, clarity, consistency, measurability), NOT implementation behavior.\n\n## Steps\n\n1. Run `.specify/scripts/bash/check-prerequisites.sh --json` to get FEATURE_DIR\n2. Ask up to 3 clarifying questions about scope, depth, audience\n3. Load spec.md, plan.md (if exists), tasks.md (if exists)\n4. Generate checklist items grouped by: Completeness, Clarity, Consistency, Acceptance Criteria, Scenario Coverage, Edge Cases, Non-Functional, Dependencies\n5. Write to `FEATURE_DIR/checklists/{domain}.md` (e.g., `ux.md`, `api.md`, `security.md`)\n\n## Item Format\n\n- Items ask about REQUIREMENT QUALITY, not implementation:\n - YES: \"Are error handling requirements defined for all API failure modes? [Gap]\"\n - NO: \"Verify the button clicks correctly\"\n- Include traceability: `[Spec §X.Y]`, `[Gap]`, `[Ambiguity]`, `[Conflict]`\n- Sequential IDs: CHK001, CHK002, ...\n\n## Context\n\n- Full workflow details: `.claude/commands/speckits/checklist.md`", "variables": [], "notes": "Generate a custom checklist for the current feature — \"unit tests for requirements writing.\"", "metadata": { "source": { "provider": "github-codex-prompts", "repository": "https://github.com/debate-timer/debate-timer-fe", "path": ".codex/prompts/checklist.md", "ref": "30a7859911ca502c4e72c1a8c50cddd4150270c1", "url": "https://github.com/debate-timer/debate-timer-fe/blob/30a7859911ca502c4e72c1a8c50cddd4150270c1/.codex/prompts/checklist.md", "key": "debate-timer/debate-timer-fe/.codex/prompts/checklist.md" } } }

checklist

About

Steps

Item Format

Context

Use it

Manifest

Reviews