Borrowing it
Nothing to install: this file belongs to agentculture/culture-tools. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/agentculture/culture-tools/main/.claude/skills/spec-to-plan/SKILL.mdgit clone --depth 1 https://github.com/agentculture/culture-toolsWrote 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.
[](https://agentmods.dev/skills/agentculture/culture-tools/spec-to-plan)<a href="https://agentmods.dev/skills/agentculture/culture-tools/spec-to-plan"><img src="https://agentmods.dev/badge/skills/agentculture/culture-tools/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.
<a href="https://agentmods.dev/skills/agentculture/culture-tools/spec-to-plan"><img src="https://agentmods.dev/badge/skills/agentculture/culture-tools/spec-to-plan.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00181 | $0.02804 |
| Opus 5 | $0.00090 | $0.01402 |
| Sonnet 5 | $0.00036 | $0.00561 |
| Haiku 4.5 | $0.00018 | $0.00280 |
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 12d 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.
This is a copy
100% identical to spec-to-plan — 0 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.
How it starts
The opening of the file, as written. The whole thing — 231 lines — stays where its author put it; the contents beside it link to each section on GitHub.
spec-to-plan — work a converged spec forwards into a buildable plan
The skill is named spec-to-plan; the product/CLI it drives is the
devague plan command group. (The prior leg — turning a vague idea into a
spec — is the sibling /think skill.) It is the forward peer of the
working-backwards spec engine: where /think converges on what to build,
/spec-to-plan converges on how to build it.
A plan is seeded from a converged frame and tracks tasks against the
spec's coverage targets. The CLI is deterministic and move-driven — you
(the agent) choose the next move; the CLI tracks state and tells you what's still
missing. Run devague plan learn for the method and devague plan explain <move> for any single move.
How to run
The entry point is scripts/spec-to-plan.sh. Invoke it from the repository you
are speccing (plans persist under .devague/ in the current directory, alongside
the frames they derive from):
bash .claude/skills/spec-to-plan/scripts/spec-to-plan.sh <move> [args...]
bash .claude/skills/spec-to-plan/scripts/spec-to-plan.sh status
It resolves the CLI portably — an installed devague on PATH (the normal
case), falling back to uv run devague inside the devague checkout, else an
install hint. Every move — including status — is forwarded verbatim as
devague plan <move>, so you can equally call the CLI directly
(devague plan <move> …).
Moves
| Move | What it does |
|---|---|
new --frame <slug> |
Seed a plan from a converged frame. Derives the coverage targets (c*/h*) the plan must satisfy. Refuses an unconverged frame. |
task "<summary>" |
Add a task. --accept "<crit>", --dep <tN>, --covers <c*/h*> (each repeatable); --origin llm lands it proposed. |
accept <tN> "<crit>" |
Add an acceptance criterion to a task. |
depend <tN> --on <tM> |
Record that task tN depends on tM. |
cover <tN> --target <c*/h*> |
Mark a task as covering a coverage target. |
confirm <tN> / reject <tN> |
Resolve a task. User-only decision. |
risk "<text>" --kind <kind> |
Record a first-class plan risk (--task <tN> to attach). |
converge |
Evaluate the gate against the live source frame; list remaining gaps. |
export |
Write the buildable plan to docs/plans/ — only after converge passes. |
waves |
Emit deterministic dependency waves ({plan, waves}) — scheduling metadata only, not orchestration. Read-only, works on an in-progress plan; refuses a cyclic/dangling graph. Devague describes the graph; an operator decides how to run it (#20). |
status |
Read-only: where the plan stands + the recommended next move, re-checked against the live frame (--json too). |
show / list |
Render a plan / list plans (--json for raw state). |
learn / explain <move> |
Teach the method / explain one move. |
What ships with it
1 file 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.
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.
- 12d ago First seen · 231 lines · 181 tokens per session scan A 237fa08bdcdc
spec-to-plan is a skill published in the GitHub repository agentculture/culture-tools (2 stars, last pushed 5d ago), licensed Apache-2.0. It adds 181 tokens to every session and 2,804 once invoked, about $0.0009 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to spec-to-plan, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…