ai-platform-engineering: Skill for Claude Code

.claude/skills/speckit.checklist/SKILL.md

speckit.checklist is a skill for Claude Code from caipe-io/ai-platform-engineering. It costs 0 tokens per session (3,826 once invoked), scanned A, a copy of speckit-checklist, Apache-2.0.

A checklist generator for reviewing whether written requirements are clear, complete, consistent, and ready to implement. TDD, or test-driven development, is a software practice; here the phrase means testing requirements in writing, not testing code.

In plain words
What is it for?
Use it to create review checklists for product or feature specifications, including visual, interaction, accessibility, and failure-state requirements.
Why use it?
It helps find vague wording, missing edge cases, inconsistent rules, and absent accessibility details before implementation begins.

Skill for Claude Code

Written for Claude Code: $ARGUMENTS substitution.

This is caipe-io/ai-platform-engineering's own configuration. It tells Claude Code how to work on ai-platform-engineering itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything ai-platform-engineering configures →

Reuse

Borrowing it

Nothing to install: this file belongs to caipe-io/ai-platform-engineering. 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/caipe-io/ai-platform-engineering/main/.claude/skills/speckit.checklist/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/caipe-io/ai-platform-engineering

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.

agentmods badge for speckit.checklist

README.md
[![agentmods](https://agentmods.dev/badge/skills/caipe-io/ai-platform-engineering/speckit.checklist/github.svg)](https://agentmods.dev/skills/caipe-io/ai-platform-engineering/speckit.checklist)
Your own site
<a href="https://agentmods.dev/skills/caipe-io/ai-platform-engineering/speckit.checklist"><img src="https://agentmods.dev/badge/skills/caipe-io/ai-platform-engineering/speckit.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.

agentmods 80×15 button for speckit.checklist

Your own site · 80×15
<a href="https://agentmods.dev/skills/caipe-io/ai-platform-engineering/speckit.checklist"><img src="https://agentmods.dev/badge/skills/caipe-io/ai-platform-engineering/speckit.checklist.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,826 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 81% 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00000 $0.03826
Opus 5 $0.00000 $0.01913
Sonnet 5 $0.00000 $0.00765
Haiku 4.5 $0.00000 $0.00383

Measured 9d ago against content hash 8b5559391c97, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

speckit.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 9d 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

81% identical to speckit-checklist — 86 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/skills/speckit.checklist/SKILL.md · 301 lines

How it starts

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


description: Generate a custom checklist for the current feature based on user requirements.

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

  1. Setup: Run .specify/scripts/bash/check-prerequisites.sh --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").
  2. 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 · 301 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.

  1. 9d ago First seen · 301 lines · 0 tokens per session scan A 8b5559391c97

Subscribe to this mod's changes

speckit.checklist is a skill published in the GitHub repository caipe-io/ai-platform-engineering (407 stars, last pushed today), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 3,826 tokens. A static security scan graded it A with 0 findings. It is 81% identical to speckit-checklist, differing in 86 lines, and is treated as a copy.