vibe-spec
01Plugin Claude Code
Plugin marketplace listing 1 plugin: vibe-spec.
Plugin Claude Code
Plugin marketplace listing 1 plugin: vibe-spec.
Plugin Claude Code
Spec-driven development workflow + a production-tested full-stack reference. A 5-step /spec- workflow (draft, refine, phases, plan, implement) plus /spec-setup, /spec-doctor, and /spec-troubleshoot for environment setup, /spec-secrets for redacted secret-leak auditing, and a vibe-spec skill with 21 on-demand stack ref.
Command
Read-only environment health check for the Vibe-Spec stack. Detects your OS and reports which prerequisite tools (Git, Node, pnpm, Docker, uv) are installed, their versions, and what each is needed for. Installs nothing.
Command
Step 1 of the Vibe-Spec workflow. Interview the user about their product and write a rough V0 spec — what it does and how users interact with it, no tooling decisions yet.
Command
Step 5 of the Vibe-Spec workflow. Promote a phase plan to detailed, implement it following the vibe-spec references, then update the docs so the spec reflects reality.
Command
Step 3 of the Vibe-Spec workflow. Break the V1 spec into sequential, self-contained phases and append a phase index, producing the final V2 spec.
Command
Step 4 of the Vibe-Spec workflow. Generate the high-level plan file for every phase in the V2 phase index, each with a scope + status header, so the user has a complete set of plan files to work from.
Command
Step 2 of the Vibe-Spec workflow. Critique the V0 spec, fill gaps with clarifying questions, then promote it to a V1 spec that maps each piece of functionality to concrete stack tools using the vibe-spec references.
Command
Audit a Vibe-Spec app for secrets leaking to the browser. A locked-down, redacting command — a local script reads .env and the built bundle, and Claude only ever sees variable NAMES and pass/fail verdicts. Secret values never enter the model's context.
Command
Guided environment setup for the Vibe-Spec stack. Figures out which tools your project needs (from your spec, or by project type), checks what's missing, and helps you install only the gaps — proposing exact per-OS commands and running each only after you confirm.
Command
Diagnose and fix common Vibe-Spec stack problems — tools that are installed but failing, database connection errors, Prisma issues, failing lint/test gates, broken git hooks. Maps the symptom to a cause and a fix, confirming before changing anything.
Skill Claude CodeCodex
Spec-driven development workflow plus a production-tested full-stack reference (Next.js 16, Prisma, PostgreSQL, Auth.js/OTP, RBAC, dbt, Zod, Vitest, shadcn/ui, S3, Web Push, GitHub Actions, Vercel). Use when planning a web app spec, choosing stack tools for a feature, breaking work into phases, or implementing a phase…