spec-to-plan

spec-to-plan is a skill for Claude Code, Codex from eugenepyvovarov/mcpbundler-agent-skills-marketplace. It costs 80 tokens per session (928 once invoked), scanned A, original, MIT.

A method for turning a project description or feature request into a written specification and a list of implementation tasks.

In plain words
What is it for?
Use it to define features, identify unclear requirements, document technical work, and create a development plan.
Why use it?
It helps clarify requirements and break a broad idea into work that developers can carry out.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it to define features, identify unclear requirements, document technical work, and create a development plan.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/eugenepyvovarov/mcpbundler-agent-skills-marketplace/spec-to-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 eugenepyvovarov/mcpbundler-agent-skills-marketplace --skill spec-to-plan
Clone the repo
git clone --depth 1 https://github.com/eugenepyvovarov/mcpbundler-agent-skills-marketplace

Made for: Claude Code, Codex.

Its marketplace also offers this one on its own, as the plugin spec-to-plan/plugin install spec-to-plan after adding the marketplace above.

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 spec-to-plan

README.md
[![agentmods](https://agentmods.dev/badge/skills/eugenepyvovarov/mcpbundler-agent-skills-marketplace/spec-to-plan/github.svg)](https://agentmods.dev/skills/eugenepyvovarov/mcpbundler-agent-skills-marketplace/spec-to-plan)
Your own site
<a href="https://agentmods.dev/skills/eugenepyvovarov/mcpbundler-agent-skills-marketplace/spec-to-plan"><img src="https://agentmods.dev/badge/skills/eugenepyvovarov/mcpbundler-agent-skills-marketplace/spec-to-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 spec-to-plan

Your own site · 80×15
<a href="https://agentmods.dev/skills/eugenepyvovarov/mcpbundler-agent-skills-marketplace/spec-to-plan"><img src="https://agentmods.dev/badge/skills/eugenepyvovarov/mcpbundler-agent-skills-marketplace/spec-to-plan.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 80 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 928 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.00080 $0.00928
Opus 5 $0.00040 $0.00464
Sonnet 5 $0.00016 $0.00186
Haiku 4.5 $0.00008 $0.00093

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

Security

Grade A, and why

spec-to-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 9d 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-to-plan/SKILL.md · 118 lines

How it starts

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

Spec-to-Plan Skill

This skill guides the process of transforming project descriptions into clear specifications and actionable task lists for developers.

Process Overview

The skill follows a five-phase workflow:

  1. Create Initial Specification - Analyze the feature/project description
  2. Clarify Questions - Identify and resolve all ambiguities
  3. Generate Markdown Spec - Produce detailed specification document (presented as spec.md in chat)
  4. Create Comprehensive Todo - Break down into implementable tasks
  5. Output Plan Markdown - Generate final plan.md with progress tracking (presented in chat)

Final deliverables: Both specification and plan content are provided as markdown in the conversation.

Phase 1: Initial Specification

Load the prompt template from references/phase1_spec_prompt.md and fill in the feature description provided by the user.

Key principles:

  • If files are provided, analyze the codebase thoroughly
  • If no files, work from the task description or ask for detailed project description
  • Identify dependencies, structure, and integration points
  • Note edge cases (within reason - ask about scope depth)
  • List ALL unclear or ambiguous points

Do NOT implement yet - only analyze and prepare questions.

Phase 2: Clarify Questions

Ask all clarification questions at once. After receiving answers:

  • If more questions persist, ask them
  • Continue until no ambiguities remain
  • Do NOT assume any requirements beyond explicitly described details

Scope control:

  • Ask the user about desired depth and scope when uncertain
  • Avoid going overboard with edge cases unless specifically requested
  • Focus on what's explicitly needed

Phase 3: Generate Markdown Spec

After all questions are answered, create a comprehensive specification document and present it in the chat:

Content requirements:

  • No specific template required (flexible format)
  • Should be clear, detailed, and implementation-ready
  • Include all decisions and clarifications from the Q&A phase
  • Document the full feature/project specification

Read the full file on GitHub · 118 lines

Files

What ships with it

3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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. 9d ago First seen · 118 lines · 80 tokens per session scan A b19bf360db60

Subscribe to this mod's changes

spec-to-plan is a skill published in the GitHub repository eugenepyvovarov/mcpbundler-agent-skills-marketplace (12 stars, last pushed 6mo ago), licensed MIT. It adds 80 tokens to every session and 928 once invoked, about $0.0004 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-09-03.

Related

Other skills, from other repositories

syndic

Gère un parc de copropriétés en France avec vue portfolio consolidée. Couvre administration, comptabilité (décret 2005, plan comptable copro, 5 annexes), assemblées générales (convocation, PV, notification), appels de fonds, travaux, fournisseurs, recouvrement d'impayés et transition de syndic. Maîtrise les majorités…

romainsimon/paperasse · 194 tokens

template-instantiation

Creates .NET projects from templates with validated parameters, smart defaults, Central Package Management adaptation, and latest NuGet version resolution. USE FOR: creating new dotnet projects, scaffolding solutions with multiple projects, installing or uninstalling template packages, creating projects that respect…

managedcode/dotnet-skills · 168 tokens

baocut

BaoCut-only operator for the installed bcut CLI and .bcut projects. Implicitly trigger only when the request explicitly names BaoCut or bcut, targets a .bcut project or BaoCut Subtitle Studio, or continues a BaoCut workflow already established in the conversation. Do not trigger solely for generic audio or video…

JimLiu/baocut · 160 tokens

note-improvement

Capture an out-of-scope improvement opportunity so it doesn't get lost. Use when the user asks to "note improvement", "save improvement", "track this for later", "remember this improvement", "note this idea", "log improvement", "backlog this", or "park this idea". Also invoke proactively when noticing something…

tobihagemann/turbo · 107 tokens

turborepo-monorepo

Provides comprehensive Turborepo monorepo management guidance for TypeScript/JavaScript projects. Use when creating Turborepo workspaces, configuring turbo.json tasks, setting up Next.js/NestJS apps, managing test pipelines (Vitest/Jest), configuring CI/CD, implementing remote caching, or optimizing build performance…

giuseppe-trisciuoglio/developer-kit · 76 tokens

handover-admin

Generate comprehensive admin documentation for AEM Edge Delivery Services project handover. Use when handing over admin responsibilities, onboarding a new site administrator, or documenting admin procedures — e.g., "admin guide", "admin documentation", "admin handover".

adobe/skills · 52 tokens