speckit-checklist
Generate a custom checklist for the current feature based on user requirements.
- License 许可
- AGPL-3.0
- 最近更新
- 2026-11-05
- Stars
- ★ 1
- Forks
- 0
01 前言 Front Matter
- name
- speckit-checklist
- metadata
- { "author": "github-spec-kit", "source": "templates/commands/checklist.md" }
- description
- Generate a custom checklist for the current feature based on user requirements.
- argument-hint
- Domain or focus area for the checklist
- compatibility
- Requires spec-kit project structure with .specify/ directory
- user-invocable
- true
- disable-model-invocation
- false
02 资源文件 3
- 参考文档references/anti-examples-what-not-to-do.md1.4 KB
- 参考文档references/example-checklist-types-sample-items.md2.1 KB
- 参考文档references/project-generation.md18.7 KB
03 SKILL.md 正文
Requirements-quality checklists
Evaluate what the requirements document specifies: completeness, clarity, consistency, measurability, and scenario coverage. Do not turn the task into implementation testing. Respect the user's focus, audience, depth, and requested output; do not invent requirement values or missing project facts.
Shared rules
- Write questions about whether requirements are defined, quantified, consistent, or complete. Cover relevant primary, alternate, exception, recovery, and non-functional scenarios; flag missing requirements instead of inventing them.
- For checklist items, use
- [ ] CHK###with incrementing IDs, a question, and a bracketed quality dimension. Reference existing requirements with[Spec §ID]; use[Gap],[Ambiguity],[Conflict], or[Assumption]as appropriate. When a question identifies a missing policy or requirement, include[Gap]even when it also cites a related existing spec section. At least 80% of generated items must have a traceability reference or marker. - Custom checklists are reviewer-owned. Generate unchecked items only.
[x]means reviewer approval of requirements quality, not implementation completion. Evaluate existing items only when the reviewer asks. The built-inchecklists/requirements.mdmaintained by specify/clarify is a separate case. - When writing a checklist file, preserve every existing byte, including notes and checkbox states; append with IDs continuing after the last existing ID. Never replace or reformat prior content.
- Honor the user's requested count and allocation. When they ask for one question per topic, assign a distinct question to each topic; do not combine topics or fill the count with a question that repeats them. Consolidate duplicates only within that allocation. Without an explicit allocation, prioritize by risk if candidates exceed 40 and combine more than five low-impact edge cases.
Choose the relevant guidance
For a consultation using supplied context, answer directly using the shared rules. Do not initiate project generation just because this skill is selected. Clarify only missing information that materially changes the requested result.
For creating or appending an actual project checklist, read project-generation.md before taking project actions. It contains prerequisite/template discovery, constitution and feature context loading, clarification defaults, file structure, reporting, and the full before/after extension-hook procedure. Follow its sequence, including enabled mandatory hooks and their completion, unless the user has explicitly limited scope.
For requests for domain sample questions, or when examples are needed to resolve an item-writing ambiguity, read Example Checklist Types & Sample Items.
For requests for wrong/right examples or for correcting implementation-test wording, read Anti-Examples: What NOT To Do.
Load only the guidance relevant to the task. A linked reference is not itself a reason to read it. When quoting an example, read its source and preserve its wording.
04 同仓库更多 Skills
speckit-taskstoissues
Convert existing tasks into actionable, dependency-ordered GitHub issues for the feature based on available design artifacts.
speckit-tasks
Generate an actionable, dependency-ordered tasks.md for the feature based on available design artifacts.
speckit-specify
Create or update the feature specification from a natural language feature description.
speckit-plan
Execute the implementation planning workflow using the plan template to generate design artifacts.
speckit-implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md
speckit-converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.