What is sp.checklist?

A requirements checklist generator. It treats each checklist item like a unit test for written requirements, checking whether a feature description is clear, complete, consistent, and ready to build.

Use it to review feature requirements, including visual rules, accessibility needs, error cases, and other details developers need before coding.

It helps find missing details and ambiguous wording before implementation begins. The checklist reviews the specification, not whether the finished code works.

How AbdullahMalik17/Voice-Assistant17 configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to AbdullahMalik17/Voice-Assistant17. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/AbdullahMalik17/Voice-Assistant17/main/.claude/commands/sp.checklist.md

Clone the repo

git clone --depth 1 https://github.com/AbdullahMalik17/Voice-Assistant17

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/commands/abdullahmalik17/voice-assistant17/sp.checklist/github.svg)](https://agentmods.dev/commands/abdullahmalik17/voice-assistant17/sp.checklist)

Your own site

<a href="https://agentmods.dev/commands/abdullahmalik17/voice-assistant17/sp.checklist"><img src="https://agentmods.dev/badge/commands/abdullahmalik17/voice-assistant17/sp.checklist/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/commands/abdullahmalik17/voice-assistant17/sp.checklist"><img src="https://agentmods.dev/badge/commands/abdullahmalik17/voice-assistant17/sp.checklist.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 13 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 4,148 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin 89% copy Near-identical to another mod in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00013	$0.04148
Opus 5.5	$0.00005	$0.01659
Sonnet 5.5	$0.00003	$0.00830
Haiku 4.5	$0.00001	$0.00415

Measured 2mo ago against content hash e35f50a68b8c, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

sp.checklist scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

Origin

This is a copy

89% identical to checklist — 699 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.claude/commands/sp.checklist.md · 321 lines

How it starts

The opening of the file, as written. The whole thing — 321 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Checklist Purpose: "Unit Tests for English"

CRITICAL CONCEPT: Checklists are UNIT TESTS FOR REQUIREMENTS WRITING - they validate the quality, clarity, and completeness of requirements in a given domain.

NOT for verification/testing:

❌ NOT "Verify the button clicks correctly"
❌ NOT "Test error handling works"
❌ NOT "Confirm the API returns 200"
❌ NOT checking if code/implementation matches the spec

FOR requirements quality validation:

✅ "Are visual hierarchy requirements defined for all card types?" (completeness)
✅ "Is 'prominent display' quantified with specific sizing/positioning?" (clarity)
✅ "Are hover state requirements consistent across all interactive elements?" (consistency)
✅ "Are accessibility requirements defined for keyboard navigation?" (coverage)
✅ "Does the spec define what happens when logo image fails to load?" (edge cases)

Metaphor: If your spec is code written in English, the checklist is its unit test suite. You're testing whether the requirements are well-written, complete, unambiguous, and ready for implementation - NOT whether the implementation works.

User Input

$ARGUMENTS

You MUST consider the user input before proceeding (if not empty).

Execution Steps

Setup: Run .specify/scripts/powershell/check-prerequisites.ps1 -Json from repo root and parse JSON for FEATURE_DIR and AVAILABLE_DOCS list.
- All file paths must be absolute.
- For single quotes in args like "I'm Groot", use escape syntax: e.g 'I'''m Groot' (or double-quote if possible: "I'm Groot").
Clarify intent (dynamic): Derive up to THREE initial contextual clarifying questions (no pre-baked catalog). They MUST:
- Be generated from the user's phrasing + extracted signals from spec/plan/tasks
- Only ask about information that materially changes checklist content
- Be skipped individually if already unambiguous in $ARGUMENTS
- Prefer precision over breadth

Read the full file on GitHub · 321 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

2mo ago First seen · 321 lines · 13 tokens per session scan A e35f50a68b8c

Subscribe to this mod's changes

sp.checklist is a command published in the GitHub repository AbdullahMalik17/Voice-Assistant17 (11 stars, last pushed 4mo ago), licensed MIT. It adds 13 tokens to every session and 4,148 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 89% identical to checklist, differing in 699 lines, and is treated as a copy.

Planning

sp.checklist next to 6 commands from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
sp.checklistAbdullahMalik17/Voice-Assistant17	Command	11	4mo ago	MIT	A	13	Claude Code
checklistgithub/spec-kit	Command	148k	yesterday	MIT	A	13	Claude Code
clarifygithub/spec-kit	Command	148k	yesterday	MIT	A	27	Claude Code
specifygithub/spec-kit	Command	148k	yesterday	MIT	A	13	Claude Code
analyzegithub/spec-kit	Command	148k	yesterday	MIT	A	26	Claude Code
convergegithub/spec-kit	Command	148k	yesterday	MIT	A	35	Claude Code
implementgithub/spec-kit	Command	148k	yesterday	MIT	A	14	Claude Code

Voice-Assistant17: Command for Claude Code