Same-tree read-only architecture auditor for active VibeOS sessions with uncommitted code.
Isolated architecture audit agent that checks for layer violations, circular dependencies, contract breakage, and module boundary violations against the project's architecture document.
Backend implementation agent that receives a WO spec and pre-written tests, then implements code to make the tests pass while following architecture rules and the no-stub policy.
Same-tree read-only contract validator for active VibeOS sessions with uncommitted code.
Cross-boundary contract validation agent. Compares frontend API client calls, TypeScript types, and response handling against actual backend route definitions, Pydantic models, and response shapes. Finds field name mismatches, missing endpoints, and response shape divergences.
Full audit cycle that dispatches all 8 audit agents (security, architecture, correctness, test quality, evidence, product drift, 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.
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.
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.
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.
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".
Executes bash commands
Hook triggers when Bash tool is used
Modifies files
Hook triggers on file write and edit operations
Uses power tools
Uses Bash, Write, or Edit tools
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
v2.1.0 — Advanced Governance Upgrade (2026-04-03)
This update makes VibeOS smarter about how it reviews its own work. It can now check code quality while it's still building (instead of waiting until everything is saved), ask a second AI (Codex) to independently verify what it built, and automatically prevent work orders from growing too large or messy. It also blocks attempts to skip safety checks and protects test files from being weakened during implementation. If you're running multiple builds in parallel, VibeOS now enforces clear boundaries so they don't step on each other. Say "Upgrade VibeOS" inside any active session to get these improvements.
v2.0.0 — Verification Integrity Upgrade (2026-03-16)
This update came after VibeOS ran a fully autonomous 8-hour build session — 156 work orders, 6,175 passing tests, zero human intervention. Running at that scale revealed places where the system needed to be more careful about verifying its own work: catching stale code reviews, validating that the front-end and back-end agree with each other, remembering issues between sessions, and making sure old problems don't get quietly ignored forever. The system now verifies its own verification.
VibeOS turns Claude Code, Cursor, and Codex into a hands-on development partner. You do not need to learn a complicated workflow to get started. Open your project in the runtime you prefer, describe what you want in plain English, and VibeOS figures out whether to discover, plan, audit, explain, or keep building.
Think of it like this:
You can learn a few commands later if you want, but the normal way to use VibeOS is to talk to it naturally.
If you are not technical, this is the only part you really need:
That is enough to get started.
VibeOS is voice-driven and conversation-first. In practice, that means:
Examples:
| You say | VibeOS does |
|---|---|
| "I want to build a booking app for dog groomers" | Starts discovery and helps shape the product |
| "Make a plan for this" | Creates a phased development plan |
| "Keep going" | Continues the build loop |
| "What's the status?" | Gives a tactical update on the current or most recent session |
| "Give me a project status" | Gives an executive big-picture briefing on the whole project |
| "Go autonomous" | Puts VibeOS back into full autonomous session mode |
| "Audit this session" | Reviews everything completed in the current or last build session |
| "Check the code quality" | Runs quality gates and explains the result |
| "What is ratcheting?" | Explains the concept in plain English |
| "Help me understand this codebase" | Audits the project and maps what exists |
# Clone VibeOS
git clone https://github.com/chieflatif/vibeos-plugin.git
# Go to your project
cd your-project
# Install
bash /path/to/vibeos-plugin/vibeos-init.sh
Or with a one-liner if you don't want to clone first:
npx claudepluginhub chieflatif/vibeos-plugin --plugin vibeosVibeOS — Autonomous development engine with layered quality governance and source-cited evidence recall
Your AI-powered Chief of Staff for enterprise sales. Self-personalizing — run /salessidekick:setup after installing to personalize (~45 min, one time). Then try /salessidekick:today for your first morning briefing. 22 commands, 11 skills, 6 Notion databases.
Token-efficient vibe-coding pipeline with hard guardrails: brainstorm, plan, isolate, exec, verify, review, integrate. Halts on 'Expected' mismatches instead of committing bad work.
Vibes is for people who use Claude Code, but don't know how to code.
VibeFlow skill library: full 16-phase workflow with plan reviews, safety guards, brainstorming, and office-hours.
Vibe Better With Claude Code - You're not an engineer anymore. You're a prompt jockey with commit access. At least do it properly.
Plan-Execute-Review development workflow with brainstorming, executor agent, and adversarial code review loop
Use this agent when you need to quickly create a new application prototype, MVP, or proof-of-concept within the 6-day development cycle. This agent specializes in scaffolding projects, integrating trending features, and building functional demos rapidly. Examples:\n\n<example>\nContext: Starting a new experiment or app idea\nuser: "Create a new app that helps people overcome phone anxiety"\nassistant: "I'll help you create a phone anxiety app. Let me use the rapid-prototyper agent to scaffold this project and build an MVP."\n<commentary>\nWhen starting any new project or experiment, use the rapid-prototyper to quickly set up the foundation and core features.\n</commentary>\n</example>\n\n<example>\nContext: Need to test a trending feature or viral concept\nuser: "I saw this TikTok trend about AI avatars, can we build something around that?"\nassistant: "That's a great trending opportunity! I'll use the rapid-prototyper agent to quickly build a prototype app featuring AI avatars."\n<commentary>\nFor capitalizing on trends and viral content, the rapid-prototyper can quickly create testable prototypes.\n</commentary>\n</example>\n\n<example>\nContext: Validating a business idea with minimal investment\nuser: "We need to test if people would pay for a subscription box curation app"\nassistant: "Let's validate that idea with a quick prototype. I'll use the rapid-prototyper agent to build an MVP with basic subscription and curation features."\n<commentary>\nBusiness validation requires fast prototyping to test market fit before full investment.\n</commentary>\n</example>\n\n<example>\nContext: Creating demo apps for stakeholder presentations\nuser: "We're meeting with investors next week and need to show them our vision"\nassistant: "I'll help create a compelling demo. Let me use the rapid-prototyper agent to build a functional prototype that showcases your vision."\n<commentary>\nInvestor demos and stakeholder presentations benefit from working prototypes rather than just mockups.\n</commentary>\n</example>