speckit.analyze

An analysis command that splits independent checks among parallel sub-agents. A sub-agent is a separate helper process that handles one focused piece of work.

In plain words
What is it for?
Use it to review specification, planning, and task documents for duplication, ambiguity, and related quality problems.
Why use it?
It reduces waiting time when several checks can be done independently. The command looks for duplicate requirements, vague wording, unresolved placeholders, and other issues.

Command

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/github/spec-kit-copilot/speckit.analyze
Clone the repo
git clone --depth 1 https://github.com/github/spec-kit-copilot
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 517 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.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.00517
Opus 5 $0.00000 $0.00259
Sonnet 5 $0.00000 $0.00103
Haiku 4.5 $0.00000 $0.00052

Measured 2d ago against content hash e34a87605eea, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, 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 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.

spec-kit-presets/copilot-sub-agents/commands/speckit.analyze.md · 27 lines

How it starts

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

Sub-Agent Delegation

When executing this command, delegate independent work to parallel sub-agents to reduce total execution time.

How to dispatch sub-agents in Copilot:

  • VS Code: Use the runSubagent tool to spawn each sub-agent in an isolated context.
  • CLI: Delegate to a sub-agent process — Copilot CLI automatically manages subsidiary sub-agent execution. You can also target custom agents defined in .github/agents/ or ~/.copilot/agents/.

Parallel Detection Passes

After loading artifacts and building semantic models, dispatch each detection pass as a separate sub-agent. All six passes are independent and can run in parallel:

  1. Sub-agent: Duplication Detection — "Analyze these artifacts for near-duplicate requirements. Identify lower-quality phrasings for consolidation. Artifacts: {spec summary}, {plan summary}, {tasks summary}. Return findings as rows: ID, Severity, Location(s), Summary, Recommendation."

  2. Sub-agent: Ambiguity Detection — "Flag vague adjectives (fast, scalable, secure, intuitive, robust) lacking measurable criteria and unresolved placeholders (TODO, TKTK, ???). Artifacts: {spec summary}, {plan summary}, {tasks summary}. Return findings as rows."

  3. Sub-agent: Underspecification — "Find requirements with verbs but missing objects or measurable outcomes, user stories missing acceptance criteria, and tasks referencing undefined components. Artifacts: {spec summary}, {plan summary}, {tasks summary}. Return findings as rows."

  4. Sub-agent: Constitution Alignment — "Check all requirements and plan elements against constitution principles. Flag any conflicts with MUST principles. Constitution: {constitution content}. Artifacts: {spec summary}, {plan summary}, {tasks summary}. Return findings as rows."

  5. Sub-agent: Coverage Gaps — "Identify requirements with zero associated tasks, tasks with no mapped requirement/story, and success criteria requiring buildable work not reflected in tasks. Requirements inventory: {inventory}. Task coverage mapping: {mapping}. Return findings as rows."

Read the full file on GitHub · 27 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. 2d ago First seen · 27 lines · 0 tokens per session scan A e34a87605eea

Subscribe to this mod's changes

speckit.analyze is a command published in the GitHub repository github/spec-kit-copilot (11 stars, last pushed 6d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 517 tokens. 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.