A specification-led workflow for planning, building, and reviewing software projects. It provides commands for starting projects, continuing work, implementing tasks, and reviewing code or pull requests.

Use it to create or continue a project, turn specifications into implementation tasks, set up work, and review code or pull-request feedback.

It gives development work a structured path from an idea to implementation and review. This can reduce uncertainty about what to plan or do next.

spec — Skill for Claude Code and Codex by scosman/vibe-crafting

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 scosman/vibe-crafting --skill skill

Clone the repo

git clone --depth 1 https://github.com/scosman/vibe-crafting

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/scosman/vibe-crafting/skill/github.svg)](https://agentmods.dev/skills/scosman/vibe-crafting/skill)

Your own site

<a href="https://agentmods.dev/skills/scosman/vibe-crafting/skill"><img src="https://agentmods.dev/badge/skills/scosman/vibe-crafting/skill/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/scosman/vibe-crafting/skill"><img src="https://agentmods.dev/badge/skills/scosman/vibe-crafting/skill.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 171 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 2,290 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.

Model	Per session	Once invoked
Fable 5.1	$0.00171	$0.02290
Opus 5.5	$0.00068	$0.00916
Sonnet 5.5	$0.00034	$0.00458
Haiku 4.5	$0.00017	$0.00229

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

Security

Grade A, and why

spec 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 21d 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.

skill/SKILL.md · 209 lines

How it starts

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

Spec-Driven Development

A structured process for building software projects with specifications. You (the human) focus on decisions and review; AI agents handle drafting and building.

How It Works

Every batch of work ("project") gets a spec folder under /specs/projects/PROJECT_NAME/. The skill guides you through:

Planning: Project overview → functional spec → architecture → implementation plan
Building: Implement phases autonomously, with code review built into each phase
Reviewing: Spec-aware code review that verifies implementation matches design

The skill is project-agnostic. It provides the process; your project-specific conventions (test commands, linting, style) come from your system prompt configuration.

If This Conversation Was Compacted

The command references below hold the role definitions, process gates and prompt templates for each command. Compaction restores only this file — not them. If this conversation has been compacted part-way through a command, re-read that command's reference file before your next action.

When compacting, preserve: this instruction, which /spec command is running, which phase and step it is on, and the handles of any sub-agents you hold — the coding agent's agent ID in particular, since you resume it for review feedback and commit.

During /spec implement, /spec task and /spec pr you are a manager: you spawn and resume sub-agents, triage review findings, run git, and print progress blocks. You do not write code, run tests, review code, or commit. Every coding round — including one that addresses review feedback — is code-reviewed before commit.

Command Reference

`/spec setup`

One-time (or incremental) setup for using the skill in a repo. Adds .specs_skill_state/ to gitignore, creates /specs/projects/ directories, detects monorepo layout, and checks for commonly-needed configuration.

→ Read setup command reference

`/spec new_project` or `/spec new`

Read the full file on GitHub · 209 lines

Files

What ships with it

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

21d ago Changed d99d64e595d1
1mo ago Changed · +2 lines bfd9b1ccce26
1mo ago Changed · +9 lines 480fae845eed
1mo ago Changed · +21 lines · +32 tokens per session 55557e6476e5
1mo ago First seen · 177 lines · 139 tokens per session scan A 9609f238faa2

Subscribe to this mod's changes

spec is a skill published in the GitHub repository scosman/vibe-crafting (78 stars, last pushed 22d ago), licensed MIT. It adds 171 tokens to every session and 2,290 once invoked, about $0.0007 per session on Opus 5.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-30.

Code review Planning

autoreview

Structured code review through the shared OpenClaw agent-skills installation.

openclaw/clawhub · 17 tokens

omh-code-review

This is an OMH code-review workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).

rlaope/oh-my-hermes · 48 tokens

revdiff-plan

Review the last Codex assistant message (plan, analysis, or proposal) with inline annotations in a TUI overlay. Extracts the most recent response from Codex rollout files and opens it in revdiff for review and annotation. Activates on "revdiff-plan", "review plan with revdiff", "annotate plan", "review last response"…

umputun/revdiff · 84 tokens

re0-merge

Review and land an external contribution the way this suite does: gate it against the thesis, land it with the author's credit intact, complete a new skill rather than merging it raw, then approve, credit, and explain before closing. Use when reviewing a pull request, as any collaborator or maintainer, not only the…

LilMGenius/paperthin · 70 tokens

explore-unknowns

Guide the user through a quadrant walk that maps the unknowns of a task — open by listing the known knowns, then work through known unknowns, unknown knowns, and unknown unknowns one stage at a time, ending with a complete four-quadrant map in the user's hands. Use when a request is ambiguous or underspecified, the…

dzhng/skills · 162 tokens

asplos-writing-style

Use when drafting or revising ASPLOS prose — engineering the first two pages that rapid review actually reads, stating the cross-layer insight as one quotable sentence, structuring per-layer mechanism sections, writing bounded claims, and fitting everything into 11 self-contained pages that include figures and…

brycewang-stanford/Awesome-Journal-Skills · 65 tokens