Vibeflow

Plugin vibeflow from marketplace vibeflow-marketplace in pe-menezes/vibeflow-claude. Commands read from the repo's manifest — 2 days ago.

Skills (10)

• analyze

  Deep-analyzes the current codebase to discover stack, architecture, patterns, conventions, and pitfalls. Creates curated documentation in .vibeflow/ that persists and can be committed to git. Supports incremental updates, scoped deep-dives, interactive review, and satellite repo analysis. Use when s

• audit

  Audits recent work against its Definition of Done and project patterns, from a review package of the diff. Runs the test suite, compares code against the spec, tests scenarios, sabotages risk code, and reports PASS / PARTIAL / FAIL with a severity and a cause on every finding. Also runs the Critical

• discover

  Runs an interactive discovery dialogue (1–5 rounds) to turn a vague idea into a clear, actionable PRD. Challenges assumptions, cuts scope, and forces decisions. Saves the PRD to .vibeflow/prds/. Use before gen-spec when the idea is not yet well-defined or requirements are unclear.

• gen-spec

  Generates a technical spec with objective, Definition of Done (3–7 binary checks), scope, anti-scope, technical decisions, and applicable patterns. Grounded in the project's real patterns from .vibeflow/. Auto-splits specs that exceed budget or DoD limits. Use when requirements are clear and you're

• hotfix

  Fixes an observed defect with reproducible evidence in one call: writes a short trace doc before touching code, implements the fix, and backs it with a regression test written before the fix. Production incidents are the motivating case, not a gate. When blocked, it halts by name and saves the doc f

• implement

  Implements a feature from its spec following all guardrails: budget, DoD, anti-scope, and pattern compliance. Runs a 9-phase pipeline, phases 0 to 8 (find spec → extract guardrails → load patterns → plan → implement → test → refine → self-verify DoD → finish). Use after gen-spec when you're ready to

• prompt-pack

  Generates a self-contained prompt pack from a spec. Embeds real code patterns from .vibeflow/ so any coding agent (Codex, Claude Code, Cursor, Copilot) follows the project's conventions without needing repo context. Use when handing off implementation to a separate session or agent.

• quick

  Fast-tracks small tasks into a ready-to-use prompt pack in one command. Skips discover, generates an ephemeral spec in memory, and outputs a prompt pack with embedded patterns. Use for well-defined tasks that fit in ≤4 files.

• stats

  Compiles statistics from audit reports: PASS/PARTIAL/FAIL rates, most violated patterns, most failing DoD checks, and quality trends over time. Output is chat-only (no file created). Use after running several audits to spot quality patterns and improvement areas.

• teach

  Updates the project knowledge base (.vibeflow/) with corrections, new conventions, architectural decisions, or new patterns based on natural language feedback. Also imports patterns from external repos through the --from option. Edits are placed outside auto-generated markers to survive incremental

Subagents (3)

• architect

  Senior software architect and technical PM. Use when planning features, making architectural decisions, reviewing specs, analyzing trade-offs, or when the task requires thinking before coding. Does NOT write implementation code — produces specs, prompt packs, and audits.

• auditor

  Independent auditor for one part of a Vibeflow feature. Use when a part's work is done and needs an audit or a re-audit in a session that did not do it: reads the briefing and the review package, follows the audit workflow, and writes only the report and the probe file. Never fixes.

• executor

  Executor for one part of a Vibeflow feature in the execution loop. Use when the orchestrator dispatches an executor or fix round: reads the briefing, implements inside its perimeter with red before green, keeps the progress file with its final marker, and never commits or calls another agent.

Similar plugins