Full spec-driven workflow for adding a feature to an existing codebase with an AI coding agent. Triggers on "feature:" prefix, "I want to add a feature", "add X to my project", "new feature", "build a feature for". Always use when adding functionality to an existing project — even without the exact prefix. Reads PLAN.md feature map before drafting — checks build order, dependencies, shared data. Stops and surfaces clearly if dependencies are not yet met. Marks unplanned features explicitly. Updates PLAN.md feature map after planning so it stays the live source of truth. Creates vibe/features/[date-slug]/ with FEATURE_SPEC.md, FEATURE_PLAN.md, FEATURE_TASKS.md. Checks for existing incomplete feature with same name before creating a duplicate. Reads SPEC.md before drafting to align with existing acceptance criteria. Updates TASKS.md (human progress view) and agent files.
Standalone agentic architecture skill. Designs complete multi-agent AI systems from scratch — no other vibe-* skills required. Deep knowledge of LangGraph, LangChain, CrewAI, AutoGen, Vercel AI SDK, and custom implementations. Produces AGENT_ARCH.md covering pattern selection, agent roles, tool mapping, state design, HITL checkpoints, VerifierAgent rubrics, implementation order, stack recommendations, and boilerplate folder structure. Generates both an interactive inline topology diagram and an exportable static SVG. Triggers on "agent:" prefix, "design an agent system", "I want to build an agent", "multi-agent pipeline", "orchestrator and sub-agents", "agentic workflow", "which agent framework should I use", "how do I structure my agents", "build a workflow with AI agents", "human in the loop", "LangGraph architecture". Always use when designing any system involving AI agents — standalone, no dependencies.
Architecture planning workflow for establishing code structure, patterns, and principles before any code is written. Runs after brainstorm: and before new: on every project. Triggers on "architect:" prefix, "plan the architecture", "architect this", "how should we structure this", "what patterns should we use". Always runs on every project — no exceptions, no shortcuts. Reads BRIEF.md stack decisions and confirms them explicitly before asking any questions — prevents scaffolding with wrong framework (e.g. Next.js when React+Vite is specified). Produces ARCHITECTURE.md from canonical template — structurally consistent so review:, fix-bug:, and add-feature: can parse it reliably every session. review: uses ARCHITECTURE.md as its primary reference for drift detection. Handles gracefully if BRIEF.md is missing. Detects existing ARCHITECTURE.md before overwriting.
Comprehensive brainstorming workflow for turning any app idea into a clear, validated, buildable brief. Two paths: personal project (8 steps) and client/business project (13 steps). Fast path for fully-formed ideas. Detects agentic/AI projects and routes to agent: before architect:. Pre-write quality check ensures BRIEF.md has specific users, measurable success criteria, explicit non-goals, and a clear v1 boundary before writing. Complexity sizing (S/M/L/XL) signals build effort to downstream skills. BRIEF.md is structurally consistent — architect:, new-app:, change-spec:, and review: all read known field names. Does not create code or project structure — thinking and brief only. Triggers on "brainstorm:" prefix, "I have an idea", "I want to build", "help me think through", "I have a client project", "thinking about building", "I want to validate this idea", "let's plan a project".
Scope change workflow for modifying, adding, or removing requirements at any point during a build. Triggers on "change:" prefix, "I forgot to add", "actually I also want", "can we add", "remove X from scope", "I changed my mind about", "before we continue add", "one more thing", "I want to change the spec", "revert the X change". Handles new additions, removals, renames, backlog operations, and reverting previous changes. Assesses impact before touching any file. Updates all affected docs in the correct order. If BRIEF.md doesn't exist, updates SPEC.md and DECISIONS.md only.
Generates and maintains two changelog files from git tags, TASKS.md, DECISIONS.md, and feature folders. CHANGELOG.md at repo root is developer-facing in Keep a Changelog format with task IDs and decisions. CHANGELOG_CLIENT.md is plain English, grouped by "what you can now do", written like a product update — no task IDs or framework names. Version detection reads git tags first, then package.json or pyproject.toml. Appending uses git log [last-tag]..HEAD — never date-based. Groups completed tasks into higher-level entries rather than one line per task. If no git tags exist, generates as [Unreleased] and prompts to tag. Triggers: "changelog:" to generate or update both files, "changelog: since v1.0" to generate entries since a specific tag.
Tracks and reports token usage and dollar cost across every level of a vibe-* project — per task, per session, per feature, per phase, and total project spend. Auto-runs at the end of every session with estimates. When invoked manually with "cost:" accepts pasted Claude Code /cost output for precise numbers. Detects eight waste patterns: CP-01 context overhead, CP-02 repeated reads, CP-03 unstructured output, CP-04 parallel multiplication, CP-05 low cache hit rate, CP-06 oversized planning, CP-07 environment debugging waste (env issues rediscovered each session), CP-08 over-investigation (files read before intent confirmed). Max 4 recommendations per session. Triggers on "cost:", "how much has this cost", "show cost report", "token usage", "what's the spend so far", "is this getting expensive". Also auto-invoked at end of vibe-add-feature, vibe-fix-bug, vibe-new-app, vibe-review.
Prepares a vibe-* project for deployment to 7 platforms: Railway, Render, Fly.io, Heroku, Vercel, Netlify, GitHub Pages. Detects stack automatically (FastAPI, Express, Next.js, Django, React, Vue, static). Patches source files (port binding to $PORT, adds /health endpoint, production CORS). Generates platform config files scoped per service — backend, web, worker. Inlines non-secret env vars directly in config files per service. Links database connections using platform-native syntax. Generates ENV_SETUP.md with per-service CLI commands for secrets only. Handles background workers and cron services if the project requires them. Optionally generates GitHub Actions CI/CD workflow. Produces DEPLOY.md step-by-step checklist. Triggers: deploy: railway, deploy: render, deploy: fly, deploy: heroku, deploy: vercel, deploy: netlify, deploy: github-pages.