What is speckit.analyze?

A read-only review command for checking whether a software feature’s specification, implementation plan, and task list agree. It also checks them against the project’s written rules before implementation begins.

Use it after generating a complete task list to inspect spec.md, plan.md, tasks.md, and the project constitution, then produce a structured analysis and optional repair plan.

It helps find missing requirements, contradictions, repeated work, unclear tasks, and conflicts with project rules before coding starts. It does not edit the files.

How studyzy/tapd-ai-cli configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to studyzy/tapd-ai-cli. 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/studyzy/tapd-ai-cli/main/.codebuddy/commands/speckit.analyze.md

Clone the repo

git clone --depth 1 https://github.com/studyzy/tapd-ai-cli

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/studyzy/tapd-ai-cli/speckit.analyze/github.svg)](https://agentmods.dev/commands/studyzy/tapd-ai-cli/speckit.analyze)

Your own site

<a href="https://agentmods.dev/commands/studyzy/tapd-ai-cli/speckit.analyze"><img src="https://agentmods.dev/badge/commands/studyzy/tapd-ai-cli/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.

Your own site · 80×15

<a href="https://agentmods.dev/commands/studyzy/tapd-ai-cli/speckit.analyze"><img src="https://agentmods.dev/badge/commands/studyzy/tapd-ai-cli/speckit.analyze.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 1,883 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 100% 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.00030	$0.01883
Opus 5.5	$0.00012	$0.00753
Sonnet 5.5	$0.00006	$0.00377
Haiku 4.5	$0.00003	$0.00188

Measured 2mo ago against content hash d7542fa67307, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, 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 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

100% identical to speckit.analyze — 0 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.

.codebuddy/commands/speckit.analyze.md · 185 lines

How it starts

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

用户输入

$ARGUMENTS

在继续之前, 你必须考虑用户输入(如果不为空).

目标

在实施之前, 识别三个核心制品(spec.md, plan.md, tasks.md)之间的不一致, 重复, 模糊和规范不足的项目. 此命令必须在 /speckit.tasks 成功生成完整的 tasks.md 后运行.

操作约束

严格只读: 不要修改任何文件. 输出结构化分析报告. 提供可选的修复计划(用户必须明确批准后才能手动调用任何后续编辑命令).

章程权威: 项目章程(.specify/memory/constitution.md)在此分析范围内是不可协商的. 章程冲突自动为严重问题, 需要调整规范, 计划或任务——而不是稀释, 重新解释或默默忽略原则. 如果原则本身需要更改, 那必须在 /speckit.analyze 之外的单独, 明确的章程更新中进行.

执行步骤

1. 初始化分析上下文

从仓库根目录运行一次 .specify/scripts/bash/check-prerequisites.sh --json --require-tasks --include-tasks 并解析 JSON 以获取 FEATURE_DIR 和 AVAILABLE_DOCS. 推导绝对路径:

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

如果任何必需文件缺失, 则以错误消息中止(指示用户运行缺失的先决条件命令). 对于参数中的单引号, 如 "I'm Groot", 使用转义语法: 例如 'I'''m Groot'(或尽可能使用双引号: "I'm Groot").

2. 加载制品(渐进式展示)

仅从每个制品加载最小必需的上下文:

**从 spec.md: **

概述/上下文
功能需求
非功能需求
用户故事
边缘情况(如果存在)

**从 plan.md: **

架构/技术栈选择
数据模型引用
阶段
技术约束

**从 tasks.md: **

任务 ID
描述
阶段分组
并行标记 [P]
引用的文件路径

**从章程: **

加载 .specify/memory/constitution.md 进行原则验证

3. 构建语义模型

创建内部表示(输出中不包含原始制品):

需求清单: 每个功能和非功能需求, 带有稳定键(基于祈使短语推导 slug; 例如, "User can upload file" → user-can-upload-file)
用户故事/操作清单: 带有验收标准的离散用户操作
任务覆盖映射: 将每个任务映射到一个或多个需求或故事(通过关键词/显式引用模式推断, 如 ID 或关键短语)
章程规则集: 提取原则名称和 MUST/SHOULD 规范性声明

4. 检测过程(高效令牌分析)

专注于高信号发现. 限制总共 50 个发现; 在溢出摘要中聚合其余部分.

A. 重复检测

识别近似重复的需求
标记较低质量的表述以进行合并

B. 模糊性检测

标记缺乏可测量标准的模糊形容词(快速, 可扩展, 安全, 直观, 稳健)
标记未解决的占位符(TODO, TKTK, ???, <placeholder> 等)

C. 规范不足

有动词但缺少对象或可测量结果的需求
缺少验收标准对齐的用户故事
引用规范/计划中未定义的文件或组件的任务

D. 章程对齐

与 MUST 原则冲突的任何需求或计划元素
章程中缺失的强制部分或质量门控

E. 覆盖缺口

没有关联任务的需求
没有映射需求/故事的任务
未在任务中反映的非功能需求(例如, 性能, 安全性)

F. 不一致性

术语漂移(相同概念在不同文件中命名不同)
计划中引用但在规范中缺失的数据实体(反之亦然)
任务排序矛盾(例如, 集成任务在基础设置任务之前而没有依赖说明)
冲突需求(例如, 一个要求 Next.js 而另一个指定 Vue)

5. 严重性分配

使用此启发式方法对发现进行优先级排序:

严重: 违反章程 MUST, 缺失核心规范制品, 或零覆盖的需求阻止基线功能
高: 重复或冲突需求, 模糊的安全/性能属性, 不可测试的验收标准
中: 术语漂移, 缺失非功能任务覆盖, 规范不足的边缘情况
低: 风格/措辞改进, 不影响执行顺序的轻微冗余

Read the full file on GitHub · 185 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 · 185 lines · 30 tokens per session scan A d7542fa67307

Subscribe to this mod's changes

speckit.analyze is a command published in the GitHub repository studyzy/tapd-ai-cli (61 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 30 tokens to every session and 1,883 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to speckit.analyze, differing in 0 lines, and is treated as a copy.

Planning

speckit.analyze next to 6 commands from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
speckit.analyzestudyzy/tapd-ai-cli	Command	61	3mo ago	Apache-2.0	A	30	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

tapd-ai-cli: Command for Claude Code