ai-platform-engineering: Skill for Claude Code

.claude/skills/speckit.analyze/SKILL.md

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

A read-only review of three project documents: a specification, an implementation plan, and a task list. It looks for contradictions, duplicates, unclear wording, and missing detail before coding starts.

In plain words
What is it for?
Use it after the task list has been created to check that the project's intended behavior, technical plan, and work items agree.
Why use it?
It helps find planning problems before they turn into implementation work. The report does not change the files.

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.analyze/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.analyze

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/caipe-io/ai-platform-engineering/speckit.analyze"><img src="https://agentmods.dev/badge/skills/caipe-io/ai-platform-engineering/speckit.analyze.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 1,577 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 75% 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.01577
Opus 5 $0.00000 $0.00788
Sonnet 5 $0.00000 $0.00315
Haiku 4.5 $0.00000 $0.00158

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

Security

Grade A, and why

speckit.analyze 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

75% identical to speckit-analyze — 91 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.analyze/SKILL.md · 190 lines

How it starts

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


description: Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.

User Input

$ARGUMENTS

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

Goal

Identify inconsistencies, duplications, ambiguities, and underspecified items across the three core artifacts (spec.md, plan.md, tasks.md) before implementation. This command MUST run only after /speckit.tasks has successfully produced a complete tasks.md.

Operating Constraints

STRICTLY READ-ONLY: Do not modify any files. Output a structured analysis report. Offer an optional remediation plan (user must explicitly approve before any follow-up editing commands would be invoked manually).

Constitution Authority: The project constitution (.specify/memory/constitution.md) is non-negotiable within this analysis scope. Constitution conflicts are automatically CRITICAL and require adjustment of the spec, plan, or tasks—not dilution, reinterpretation, or silent ignoring of the principle. If a principle itself needs to change, that must occur in a separate, explicit constitution update outside /speckit.analyze.

Execution Steps

1. Initialize Analysis Context

Run .specify/scripts/bash/check-prerequisites.sh --json --require-tasks --include-tasks once from repo root and parse JSON for FEATURE_DIR and AVAILABLE_DOCS. Derive absolute paths:

  • SPEC = FEATURE_DIR/spec.md
  • PLAN = FEATURE_DIR/plan.md
  • TASKS = FEATURE_DIR/tasks.md

Abort with an error message if any required file is missing (instruct the user to run missing prerequisite command). 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").

Read the full file on GitHub · 190 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 · 190 lines · 0 tokens per session scan A 59d7b59251c4

Subscribe to this mod's changes

speckit.analyze 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 1,577 tokens. A static security scan graded it A with 0 findings. It is 75% identical to speckit-analyze, differing in 91 lines, and is treated as a copy.