Not quite vibe-coding. Not quite boomer coding. Something else.
概要
/spec is a standard agent skill that runs a full spec-driven build process: upfront specs written with you, phased autonomous builds, and layered code review. You make the decisions; the agent does the drafting, the building, and the first few passes of review. It's the process I use to ship code I actually care about — an iOS app, Mac apps, a Python data pipeline, Git sync engines — without writing the code myself, and without compromising on architecture or quality. Install it and you get ten /spec commands in the agent of your choice. — how the process evolved, where the AI still gets things wrong, what it costs, and the sandboxing/tooling pain — is in the blog post: . run npx skills add scosman/vibe-crafting, or copy the skill/ directory into your agent's skills directory, named spec.
README
██╗ ██╗██╗██████╗ ███████╗
██║ ██║██║██╔══██╗██╔════╝
██║ ██║██║██████╔╝█████╗
╚██╗ ██╔╝██║██╔══██╗██╔══╝
╚████╔╝ ██║██████╔╝███████╗
╚═══╝ ╚═╝╚═════╝ ╚══════╝
██████╗██████╗ █████╗ ███████╗████████╗██╗███╗ ██╗ ██████╗
██╔════╝██╔══██╗██╔══██╗██╔════╝╚══██╔══╝██║████╗ ██║██╔════╝
██║ ██████╔╝███████║█████╗ ██║ ██║██╔██╗ ██║██║ ███╗
██║ ██╔══██╗██╔══██║██╔══╝ ██║ ██║██║╚██╗██║██║ ██║
╚██████╗██║ ██║██║ ██║██║ ██║ ██║██║ ╚████║╚██████╔╝
╚═════╝╚═╝ ╚═╝╚═╝ ╚═╝╚═╝ ╚═╝ ╚═╝╚═╝ ╚═══╝ ╚═════╝
Vibe Crafting
An agent skill for spec-driven development
/spec is a standard agent skill that runs a full spec-driven build process: upfront specs written with you, phased autonomous builds, and layered code review. You make the decisions; the agent does the drafting, the building, and the first few passes of review.
It’s the process I use to ship code I actually care about — an iOS app, Mac apps, a Python data pipeline, Git sync engines — without writing the code myself, and without compromising on architecture or quality.
Install it and you get ten /spec commands in the agent of your choice.
[!TIP] Read the full story — how the process evolved, where the AI still gets things wrong, what it costs, and the sandboxing/tooling pain — is in the blog post: Vibe Crafting: Vibe Coding for Stuff You Care About.
Quickstart
Install: run npx skills add scosman/vibe-crafting, or copy the skill/ directory into your agent’s skills directory, named spec.
Then the shortest real path from nothing to shipped:
/spec setup # once per repo
/spec new project # walks you through creating a spec for your project
/spec implement all # walk away; it builds every phase, reviewing and committing as it goes
/spec pr # after you open the PR: pulls review comments and fixes them
Two things worth getting right up front:
Add an AGENTS.md. If you haven’t already, add one with your code-review guidelines, testing strategies, and best practices. It’s what the coding agent follows on every phase.
Don’t let the coding agent stop to ask permission. /spec implement all is only useful if it actually runs unattended. I run in cloud sandboxes in yolo mode, or locally in a sandbox with claude --permission-mode=dontAsk. Give it build, test, lint, and format tools it can call on its own.
Commands
| Command | Aliases | What it does |
|---|---|---|
/spec |
— | Router. Reads current state and suggests the next action. Also interprets open-ended requests. |
/spec setup |
— | One-time per-repo setup. Adds .specs_skill_state/ and reviews/ to .gitignore, creates /specs/projects/, detects monorepo layout, checks for missing config. Idempotent. |
/spec new project |
/spec new_project, /spec new |
Plan a new project from scratch: project overview, functional spec, UI design (if relevant), architecture, component designs, implementation plan. Sets it as the active project. |
/spec continue |
/spec cont |
Resume the active project. Shows current state and routes to the next logical action. |
/spec implement [all] |
/spec impl |
Build the active project. implement next for one phase, implement all for every remaining phase, implement phase N for a specific one. Each phase runs code → review → commit. |
/spec task |
— | A one-off change without the full spec process. Describe it inline, get the same implement loop (code → review → commit) with no planning artifacts. |
/spec research |
— | Research a topic on the web. Splits it into subtopics, runs a sub-agent per subtopic, writes a tree of research docs under one summary. Needs web search + fetch tools. Runs standalone or inside new project. |
/spec cr |
/spec code_review |
Fast, spec-aware code review of the current diff (or a scope you name). Always runs in a sub-agent with clean context. |
/spec deep cr |
/spec deep review |
Multi-phase agentic review of the whole branch against its fork point. Designs review phases for the diff, runs focused sub-agents in parallel, writes persistent review artifacts. |
/spec design crit |
/spec crit |
A multi-agent design review. Ends with an interactive pass to triage and fix what it found. |
/spec pr |
— | Address GitHub PR feedback. Finds the PR for the branch, pulls unresolved comments, fixes them through the standard CR loop, commits, pushes, and replies to each thread. |
Full details for each command live in skill/references/, one file per command. The skill loads them on demand.
What else is in this repo
skill/— the skill itself. This is the thing you install.prompts/— the hand-rolled prompt files that predate the skill, from before any of this was packaged. The blog post references them as examples; the skill supersedes them.example_specs/phase13.md— a real per-phase plan, so you can see what the coding agent is actually handed.specs/— the specs used to build this repo, including the blog post and several of the skill’s own features. It’s self-demonstrating:/specwas built with/spec.
推奨ツール
別のキーワードを試すか、フィルタを外してください。
インストール
npx skillfish add scosman/vibe-crafting