Slash Command

/spec-phases

From vibe-spec

Breaks a V1 project spec into sequential, self-contained phases and appends a phase index, producing the final V2 spec.

documentation

automation

Popularity

Stars

Invocation

How this command is triggered — by the user, by Claude, or both

Slash command

/vibe-spec:spec-phases

Model invocable

No pre-commands

Context Preview

The summary Claude sees in its command listing — used to decide when to auto-load this command

You are running **Step 3 of the Vibe-Spec spec-driven workflow**: promoting the **V1
spec → V2 spec** by breaking it into phases. See the `vibe-spec` skill
(`${CLAUDE_PLUGIN_ROOT}/skills/vibe-spec/reference/00-workflow.md`) for the phase
conventions.

## What to do

1. Read **`docs/project-spec.md`** (the V1 spec from `/spec-refine`). If it isn't a
   tool-mapped V1, tell the user to run `/spec-refine` first.
2. Break the work into **sequential, self-contained phases**. Each phase should be a
   chunk that can be planned, implemented, and verified independently, completable in
   roughly 1–...

Command Content

36 lines · ~422 tokens

Stats

LanguageAstro

Stars5

MaintenanceExcellent

Last CommitJun 18, 2026

Actions

View Source View Plugin View on GitHub View README

What to do

Read docs/project-spec.md (the V1 spec from /spec-refine). If it isn't a tool-mapped V1, tell the user to run /spec-refine first.
Break the work into sequential, self-contained phases. Each phase should be a chunk that can be planned, implemented, and verified independently, completable in roughly 1–3 sessions, with clear entry/exit boundaries so no context bleeds between phases. Early phases lay foundation (scaffold, DB, auth); later phases build features and polish.
Outline only at this stage — phase name, scope boundaries, and a sentence or two on what each covers. Do not fully design them yet (that's /spec-plan).

Append a phase index table to the end of docs/project-spec.md and mark the document V2. Use this shape:

### Phase Plan

| # | File | Scope |
|---|------|-------|
| 1 | `docs/plans/phase-1-foundation.md` | Project scaffold, data ingestion |
| 2 | `docs/plans/phase-2-auth.md`       | Auth, onboarding |
| 3 | `docs/plans/phase-3-dashboard.md`  | Transforms, core dashboard views |

The V2 spec is the final version — V0 and V1 can be discarded. End by telling the user to run /spec-plan to flesh out the first phase.