A read-only review command that compares a specification, implementation plan, and task list for consistency and quality. It checks for conflicts, repeated work, unclear wording, and missing detail.

Use it as a pre-implementation quality gate for spec.md, plan.md, and tasks.md without changing those files.

It finds planning problems before coding begins, when they are easier to fix. It also checks the documents against the project’s required engineering and security rules.

analyze — Command by ddunnock

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods

npx agentmods add commands/ddunnock/claude-plugins/analyze

Clone the repo

git clone --depth 1 https://github.com/ddunnock/claude-plugins

Made for: Claude Code.

Per session 12 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,043 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

Origin original No closer match found 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	$0.00012	$0.01043
Opus 5	$0.00006	$0.00522
Sonnet 5	$0.00002	$0.00209
Haiku 4.5	$0.00001	$0.00104

Measured 2d ago against content hash bc509ff95b11, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

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 2d 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.

mcps/knowledge-mcp/.claude/commands/analyze.md · 178 lines

How it starts

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

Analyze

Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md before implementation.

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 before implementation. This is a pre-implementation quality gate.

Operating Constraints

STRICTLY READ-ONLY: Do not modify any files. Output a structured analysis report.

Directive Authority: The project directives in .claude/memory/ are non-negotiable. Directive conflicts are automatically CRITICAL and require adjustment of the spec, plan, or tasks.

Memory Directives

Load these directive files for compliance checking:

Always loaded:

constitution.md - Global principles, quality gates
security.md - Security requirements
testing.md - Test coverage requirements (80% minimum)
documentation.md - Documentation standards

Project-specific (detected: Python ≥3.11, Poetry, MCP SDK):

python.md - Python standards, Pyright strict, ruff, Google-style docstrings
git-cicd.md - Conventional commits, CI pipeline

Artifacts to Analyze

Artifact	Source
spec.md	`speckit/spec.md`
plan.md	`speckit/plan.md`
tasks.md	`speckit/*-tasks.md`

Detection Passes

A. Duplication Detection

Identify near-duplicate requirements
Mark lower-quality phrasing for consolidation

B. Ambiguity Detection

Flag vague adjectives (fast, scalable, secure) lacking measurable criteria
Flag unresolved placeholders (TODO, TKTK, ???, <placeholder>)

C. Underspecification

Requirements with verbs but missing measurable outcome
User stories missing acceptance criteria
Tasks referencing undefined components

D. Directive Alignment (Agent)

Invoke compliance-checker agent:

subagent_type: "speckit-generator:compliance-checker"
prompt: "Check compliance of speckit/*.md against .claude/memory/constitution.md and all tech-specific memory files"

Read the full file on GitHub · 178 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.

2d ago First seen · 178 lines · 12 tokens per session scan A bc509ff95b11

Subscribe to this mod's changes

analyze is a command published in the GitHub repository ddunnock/claude-plugins (12 stars, last pushed 5mo ago), licensed MIT. It adds 12 tokens to every session and 1,043 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Code review

analyze