What is speckit.analyze?

A read-only review command for comparing a feature specification, implementation plan, and task list. It looks for conflicts, repeated work, unclear wording, and missing details before coding starts.

Use it after generating the task list to review spec.md, plan.md, and tasks.md. It produces an analysis report and may suggest fixes without changing files.

It helps catch planning problems before they turn into implementation rework. It also checks that the plans follow the project’s written rules.

How Damecek/salesforce-mcp-lib configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to Damecek/salesforce-mcp-lib. 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/Damecek/salesforce-mcp-lib/main/.claude/commands/speckit.analyze.md

Clone the repo

git clone --depth 1 https://github.com/Damecek/salesforce-mcp-lib

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/damecek/salesforce-mcp-lib/speckit.analyze/github.svg)](https://agentmods.dev/commands/damecek/salesforce-mcp-lib/speckit.analyze)

Your own site

<a href="https://agentmods.dev/commands/damecek/salesforce-mcp-lib/speckit.analyze"><img src="https://agentmods.dev/badge/commands/damecek/salesforce-mcp-lib/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/damecek/salesforce-mcp-lib/speckit.analyze"><img src="https://agentmods.dev/badge/commands/damecek/salesforce-mcp-lib/speckit.analyze.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 26 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,614 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 80% 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.00026	$0.01614
Opus 5.5	$0.00010	$0.00646
Sonnet 5.5	$0.00005	$0.00323
Haiku 4.5	$0.00003	$0.00161

Measured 2mo ago against content hash 0dd76be34a60, 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

80% identical to analyze — 85 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/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.

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").

2. Load Artifacts (Progressive Disclosure)

Load only the minimal necessary context from each artifact:

From spec.md:

Overview/Context
Functional Requirements
Success Criteria (measurable outcomes — e.g., performance, security, availability, user success, business impact)
User Stories
Edge Cases (if present)

From plan.md:

Architecture/stack choices
Data Model references
Phases
Technical constraints

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 · 26 tokens per session scan A 0dd76be34a60

Subscribe to this mod's changes

speckit.analyze is a command published in the GitHub repository Damecek/salesforce-mcp-lib (19 stars, last pushed 8d ago), licensed MIT. It adds 26 tokens to every session and 1,614 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 80% identical to analyze, differing in 85 lines, and is treated as a copy.

Code review Planning ai apex mcp mcp-server salesforce

speckit.analyze next to 6 commands from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
speckit.analyzeDamecek/salesforce-mcp-lib	Command	19	8d ago	MIT	A	26	Claude Code
is-not-duplicatedArenukvern/mcp_flutter	Command	395	20d ago	MIT	A	0	Claude Code, Cursor
reviewSunflowersLwtech/covate	Command	8	3d ago	MIT	A	14	Claude Code
reviewoutfitter-dev/blz	Command	28	2mo ago	MIT	A	8	Claude Code
implementggemba/squad-mcp	Command	4	3mo ago	Apache-2.0	A	0	Claude Code
inventoryggemba/squad-mcp	Command	4	3mo ago	Apache-2.0	A	0	Claude Code
show_diffZoeLinUTS/MagicTeX-mcp	Command	4	3d ago	AGPL-3.0	A	17	Claude Code

salesforce-mcp-lib: Command for Claude Code