speckit-plan

speckit-plan is a skill for Claude Code from arrrrny/zuraffa. It costs 19 tokens per session (1,865 once invoked), scanned A, a copy of speckit-plan, MIT.

A Spec Kit workflow that creates a written implementation plan from a plan template. The plan describes how a feature should be designed and built.

In plain words
What is it for?
Use it to run the project's planning process and generate its design files, including the plan artifact.
Why use it?
It gives developers a consistent design record before they start changing code.

Skill for Claude Code

Written for Claude Code: $ARGUMENTS substitution. Also seen: installed under .agents/ (shared by several agents).

Good fit Use it to run the project's planning process and generate its design files, including the plan artifact.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/arrrrny/zuraffa/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 arrrrny/zuraffa --skill speckit-plan
Clone the repo
git clone --depth 1 https://github.com/arrrrny/zuraffa

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.

agentmods badge for speckit-plan

README.md
[![agentmods](https://agentmods.dev/badge/skills/arrrrny/zuraffa/speckit-plan/github.svg)](https://agentmods.dev/skills/arrrrny/zuraffa/speckit-plan)
Your own site
<a href="https://agentmods.dev/skills/arrrrny/zuraffa/speckit-plan"><img src="https://agentmods.dev/badge/skills/arrrrny/zuraffa/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/arrrrny/zuraffa/speckit-plan"><img src="https://agentmods.dev/badge/skills/arrrrny/zuraffa/speckit-plan.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 19 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,865 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 98% 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00019 $0.01865
Opus 5.5 $0.00008 $0.00746
Sonnet 5.5 $0.00004 $0.00373
Haiku 4.5 $0.00002 $0.00186

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

98% identical to speckit-plan — 6 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.

.agents/skills/speckit-plan/SKILL.md · 167 lines

How it starts

The opening of the file, as written. The whole thing — 167 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).

Pre-Execution Checks

Check for extension hooks (before planning):

  • Check if .specify/extensions.yml exists in the project root.
  • If it exists, read it and look for entries under the hooks.before_plan key
  • If the YAML cannot be parsed or is invalid, do not skip silently: tell the user that .specify/extensions.yml could not be read (include the parser error) and that no hooks were checked, including any mandatory (optional: false) hooks registered there, then continue normally
  • Filter out hooks where enabled is explicitly false. Treat hooks without an enabled field as enabled by default.
  • For each remaining hook, do not attempt to interpret or evaluate hook condition expressions:
    • If the hook has no condition field, or it is null/empty, treat the hook as executable
    • If the hook defines a non-empty condition, skip the hook and leave condition evaluation to the HookExecutor implementation
  • When constructing command invocations from hook command names, replace dots (.) with hyphens (-). For example, speckit.git.commit → /speckit-git-commit.
  • For each executable hook, output the following based on its optional flag:
    • Optional hook (optional: true):
      ## Extension Hooks
      
      **Optional Pre-Hook**: {extension}
      Command: `/{command}`
      Description: {description}
      
      Prompt: {prompt}
      To execute: `/{command}`
      
    • Mandatory hook (optional: false):
      ## Extension Hooks
      
      **Automatic Pre-Hook**: {extension}
      Executing: `/{command}`
      EXECUTE_COMMAND: {command}
      
      Wait for the result of the hook command before proceeding to the Outline.
      
      After emitting the block above you MUST actually invoke the hook and wait for it to finish before continuing. Run it the same way you would run the command yourself in this agent/session (the invocation may differ from the literal {command} id shown above, e.g. a skills-mode agent runs it as /skill:speckit-... or $speckit-...). Emitting the block alone does not run the hook.
  • If no hooks are registered or .specify/extensions.yml does not exist, skip silently

Read the full file on GitHub · 167 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. 1mo ago Changed c77d361665b3
  2. 1mo ago Changed 3ba54b3b7b19
  3. 1mo ago First seen · 167 lines · 19 tokens per session scan A 3d13e010accc

Subscribe to this mod's changes

speckit-plan is a skill published in the GitHub repository arrrrny/zuraffa (5 stars, last pushed yesterday), licensed MIT. It adds 19 tokens to every session and 1,865 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 98% identical to speckit-plan, differing in 6 lines, and is treated as a copy.

Related

Other skills, from other repositories

flutter

Use when building, structuring, testing or optimizing a Flutter app — feature-first layering, Riverpod 3 or Bloc, typed gorouter, freezed models, a dio data layer, Material 3, jank hunting, widget/golden tests. Targets Flutter 3.44 / Dart 3.12. NOT React Native (that is react-native), NOT Compose Multiplatform (that…

ericrisco/rsc-harness · 91 tokens

he-plan

Plan a change before implementation, resolve material user decisions and prepare repository-grounded UX references. Use a compact plan for small changes; route large, unclear efforts or explicit Wayfinder requests to Wayfinder. Skip explanation-only requests and execution already covered by a ready, authorized plan.

sgaabdu4/building-flutter-apps · 58 tokens

he-ship

Deliver a verified build through a task branch and PR, check the intended remote result, and clean up the completed task safely. Use for PR creation, shipping, merging or release/deployment requests; skip planning, implementation and review-only work.

sgaabdu4/building-flutter-apps · 52 tokens

he-build

Implement and verify a ready, authorized plan through focused fixes and integrated checks, ending with a ready-for-ship handoff. Use for implementation, bug fixes or resuming build work; skip planning-only, review-only and shipping-only requests.

sgaabdu4/building-flutter-apps · 51 tokens

e2e

Prove real user journeys across browser, mobile, desktop, API and CLI surfaces using the project's existing test tools. Use for end-to-end verification, runtime UI review or requested visual proof.

sgaabdu4/building-flutter-apps · 42 tokens

he-learn

Prevent verified repeated failures and preserve lasting decisions in terse ADRs. Use when failures recur, prevention needs strengthening, or accepted decisions and steering need durable capture; skip ordinary one-off fixes and routine task updates.

sgaabdu4/building-flutter-apps · 45 tokens