vibeos-plugin

Full audit cycle that dispatches audit agents (security, architecture, correctness, test quality, evidence, product drift, flow, system invariants, dependency intelligence, delivery infrastructure, red team, contract validator), applies consensus logic, and produces a composite report with actionable findings. Use when the user says "audit the code", "review everything", "check for security issues", "do a full review", or wants a comprehensive multi-perspective code review.

Autonomous build orchestrator that executes work orders end-to-end. Use when the user says "continue", "keep going", "build the next thing", "resume", "start building", or wants to make progress on the development plan. Dispatches investigator, tester, prompt-engineering, implementation, and documentation agents in sequence with two-layer quality enforcement (Layer 1 gates + Layer 2 audit agents) and error recovery, while checking for product drift and stale high-impact decisions.

VibeOS audit flow for Codex. Use when the user asks for a code audit, quality review, governance review, architecture review, security review, or wants a full audit cycle before or after implementation work.

Full autonomous-session override for VibeOS in Codex. Use when the user says go autonomous, stop checking in, run on your own, stay in autonomous mode, or wants VibeOS to keep building until a real blocker or decision appears.

Autonomous VibeOS work-order execution for Codex. Use when the user says continue, resume, keep going, build the next thing, start implementing, or wants progress against the current VibeOS plan.

Phase-boundary checkpoint and ratchet review for VibeOS in Codex. Use when the user says phase is done, milestone check, checkpoint this phase, or wants a boundary audit before starting the next phase.

Compact enterprise MVP mission intake for VibOS Comp. Use for competition-grade builds, enterprise design-partner MVPs, rapid production-quality prototypes, battle harness runs, or explicit VibOS Comp/VibeOS Comp requests.

Explain VibeOS concepts and route the user to the right Codex workflow. Use when the user asks what a VibeOS term means, wants the difference between status and project status, needs help choosing a workflow, or wants the system explained in plain English.

VibeOS planning and work-order generation for Codex. Use when the user says make a plan, break the work down, organize the roadmap, create work orders, or wants governance and sequencing created after discovery.

Closeout audit for the current or most recent VibeOS build session in Codex. Use when the user says audit this session, review this run, session audit, or wants a trustworthy end-to-end review of what happened in the latest build session.

Tactical VibeOS session status for Codex. Use when the user asks what's the status, what's in flight, where are we in this session, or wants a near-term update on current work rather than a strategic project briefing.

Work Order management for VibeOS in Codex. Use when the user wants to create a WO, inspect WO status, mark a WO complete, audit a WO, or manage an individual unit of work inside the VibeOS plan.

Force VibeOS back into full autonomous session mode. Use when the user says "go autonomous", "stop checking in", "run on your own", "stay in autonomous mode", or wants VibeOS to keep building until it hits a real blocker, finishes the plan, or needs an explicit risk decision.

Phase boundary audit that runs all gates and all audit agents on the entire codebase, establishes quality baselines, and enforces ratcheting (finding count cannot increase between phases). Use when the user says "phase is done", "wrap up this phase", "milestone check", or when all work orders in a phase are complete.

Create a compact VibOS Comp enterprise MVP mission brief. Use when the user wants a competition-grade build, rapid but production-quality MVP, enterprise design-partner prototype, battle harness run, or says VibOS Comp/VibeOS Comp.

Get help with VibeOS concepts, glossary terms, and system orientation. Use when the user asks "what is/are...", "explain...", "how does X work?", "what does Y mean?", or wants to understand any term or concept used by the plugin, or to re-trigger the onboarding introduction.

Run project intake questionnaire, apply decision engine, and generate a complete development plan with phased work orders. Use when the user says "make a plan", "break this down", "organize the work", "create a roadmap", or wants to structure their project into phases. Requires product discovery to be complete first.

Audit the current or most recent VibeOS build session end-to-end. Use when the user says "audit this session", "review what happened in this session", "session audit", or wants a closeout review of the work completed during an autonomous run.

Show tactical session status for the current or most recent work session. Use when the user asks "what's the status?", "where are we in this session?", "remind me what we're doing", "what's in flight?", "what still needs doing right now?", or wants a micro-level update on the active work.

Framework upgrade orchestrator that copies new framework files, reconciles configuration, re-evaluates the decision engine against the project, runs all gates and auditors as a discovery sweep (not a baseline), and produces prioritized recommendations for integration and correction. Use when the user says "upgrade VibeOS", "update the framework", "I pulled the latest version", "run the upgrade", or wants to apply a newer version of the VibeOS framework to their project.

Run VibeOS quality gates from Codex. Use when the user says check the code, run quality checks, validate this, are we passing, pre-commit check, or wants gate status before closing a work order.

Run quality gates for a specific WO lifecycle phase. Use when the user says "check the code", "run quality checks", "are we passing?", "validate this", or wants to run pre-commit checks or verify code quality before completing a work order.

Complementary Audit Protocol — dispatches an independent audit via Codex (GPT-series) as auditor. Claude implements, Codex audits. Use at plan approval, WO closure, session end, or on demand. Claude must reconcile ALL material findings before closure — zero-technical-debt policy enforced (fix now or create a tracked WO, nothing dropped). Triggers: "codex audit", "audit with codex", "independent audit", "dual audit", "complementary audit", "/vibeos:codex-audit plan|complete|session|manual".

Run product discovery to turn a rough idea into validated product, anchor, and governance documents. Use when a user describes what they want to build, shares a product idea, says "I want to build/create/make...", mentions a "new project/app/product", or needs help defining scope, requirements, architecture, and technical approach. Also use for existing codebases when the user wants to analyze what they have.

Discovery, project shaping, and codebase understanding for VibeOS in Codex. Use when the user describes what they want to build, wants help understanding an existing codebase, needs initial governance artifacts, or wants product and architecture context created before planning.

Executive VibeOS project briefing for Codex. Use when the user asks for project status, the big picture, overall progress, founder update, executive summary, or wants business meaning rather than session details.

Show a founder-style executive project status briefing. Use when the user asks "project status", "where are we overall?", "give me the big picture", "executive briefing", "founder update", "program status", or wants a strategic, evidence-based view of overall progress, risks, business impact, and decisions.

Work order management with subcommands for creating, checking status, completing, and auditing individual work orders. Use when the user says "create a work order", "add a task", "what's the status of WO-X?", or wants to manage individual units of work.