speckit.plan

speckit.plan is a skill for Claude Code, Codex from wedabro/bro-skills. It costs 22 tokens per session (273 once invoked), scanned A, original, MIT.

A technical planning workflow that turns a product specification into research notes, a data model, API contracts and an architecture plan. An API contract describes how software components communicate.

In plain words
What is it for?
It helps identify unknowns, model data, define API behaviour, plan folders and components, and check whether the design meets the project’s success criteria.
Why use it?
It separates decisions about how to build the system from writing code and checks the plan against project rules before implementation.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: installed under .agents/ (shared by several agents).

Good fit It helps identify unknowns, model data, define API behaviour, plan folders and components, and check whether the design meets the project’s success criteria.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/wedabro/bro-skills/speckit.plan
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.

Any agent
npx skills add wedabro/bro-skills --skill speckit.plan
Clone the repo
git clone --depth 1 https://github.com/wedabro/bro-skills

Made for: Claude Code, Codex.

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.plan

README.md
[![agentmods](https://agentmods.dev/badge/skills/wedabro/bro-skills/speckit.plan/github.svg)](https://agentmods.dev/skills/wedabro/bro-skills/speckit.plan)
Your own site
<a href="https://agentmods.dev/skills/wedabro/bro-skills/speckit.plan"><img src="https://agentmods.dev/badge/skills/wedabro/bro-skills/speckit.plan/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.plan

Your own site · 80×15
<a href="https://agentmods.dev/skills/wedabro/bro-skills/speckit.plan"><img src="https://agentmods.dev/badge/skills/wedabro/bro-skills/speckit.plan.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 22 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 273 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 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.1 $0.00022 $0.00273
Opus 5 $0.00011 $0.00137
Sonnet 5 $0.00004 $0.00055
Haiku 4.5 $0.00002 $0.00027

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

Security

Grade A, and why

speckit.plan 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 10d 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.

.agents/skills/speckit.plan/SKILL.md · 37 lines

What it actually says

🎯 Mission

Convert spec.md (WHAT) to plan.md (HOW). Use Goal-Backward thinking to ensure your plan leads directly to Success Criteria.

📋 Protocol

Phase 0: Research

  • Scan spec → list unknowns ("NEEDS CLARIFICATION").
  • Research the solution → write to research.md .

Phase 1: Data Model

  • From entities in spec → create data-model.md .
  • Determine relationships (1:N, N:N).

Phase 2: API Contracts

  • From User Scenarios → create contracts/[entity].md .

Phase 3: Architecture

  • Create plan.md with: Folder structure, Component hierarchy, State management, Docker topology.

Phase 4: Must-Haves (Goal-Backward) ⭐

Identify required components to achieve "Success Criteria":

  • Truths: Absolutely correct logic.
  • Artifacts: Key files/outputs.
  • Key Links: Links between modules.

Gate Check

  • Compare plan vs constitution → REPORT if rules are violated.

🚫 Guard Rails

  • DO NOT write code during the planning step.
  • MUST check constitutional compliance.
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. 10d ago First seen · 37 lines · 22 tokens per session scan A b26bb7f6c06d

Subscribe to this mod's changes

speckit.plan is a skill published in the GitHub repository wedabro/bro-skills (2 stars, last pushed 14d ago), licensed MIT. It adds 22 tokens to every session and 273 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-31.