spec-phases
01Command
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.
34 tagged prisma, measured the same way as everything else here.
Browse within: nextjs 29postgresql 29docker 20edh 20magic-the-gathering 20ai-assisted-development 9spec-driven 9agent-harness 5nestjs 5
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
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
Generates a complete CRUD domain in the house pattern (NestJS + Prisma, multi-tenant).
Command
Configures the current project with the Oficina harness — generates CLAUDE.md, AGENTS.md and GEMINI.md automatically, grounded in what the project actually is.
Command
Reviews the current diff against the Oficina house checklist (security baseline, engineering philosophy, git workflow) — read-only, does not edit.
Command Codex
When /cleanup-repo is invoked, immediately execute the following steps to analyze, organize, and clean up the repository structure when files are scattered and disorganized.
Command Codex
When /devops is invoked, immediately execute the following steps to create, configure, or manage DevOps infrastructure, CI/CD pipelines, and deployment configurations.
Command Codex
When /magic-wand [issue description] is invoked, immediately execute the following steps to perform a comprehensive, expert-level analysis and fix when standard debugging approaches have failed.