vibeos

Plugin vibeos in chieflatif/vibeos-bootstrap. Commands read from the repo's manifest — 1 month ago.

Skills (8)

• audit

  Full audit cycle that dispatches all 5 audit agents (security, architecture, correctness, test quality, evidence), 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

• checkpoint

  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 p

• discover

  Run product discovery to turn a rough idea into validated product 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

• gate

  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.

• help

  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.

• plan

  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

• status

  Show project dashboard with current phase, active work orders, recent audit results, and recommended next action. Use when the user asks "how's it going?", "what's the status?", "where are we?", "what's done?", "update me", or wants to see progress, what to work on next, or an overview of the projec

• wo

  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.

Subagents (11)

• architecture-auditor

  Isolated architecture audit agent that checks for layer violations, circular dependencies, contract breakage, and module boundary violations against the project's architecture document.

• backend

  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.

• correctness-auditor

  Isolated correctness audit agent that uses deep reasoning to find logic errors, missing error paths, incomplete implementations, and hardcoded values. Each finding includes a "would a user notice?" impact statement.

• doc-writer

  Documentation agent that updates project docs after implementation, records implementation notes and evidence in the WO file, and updates tracking documents.

• evidence-auditor

  Isolated evidence audit agent that validates documentation completeness, evidence bundles, WO audit framework compliance, and tracking document accuracy across all completed work orders.

• frontend

  Frontend implementation agent that follows the same TDD pattern as the backend agent, implementing UI code to make pre-written tests pass while following architecture and accessibility standards.

• investigator

  Pre-flight analysis agent that revalidates WO assumptions, checks dependency completion, analyzes relevant codebase, and flags risks before implementation begins. Dispatched at the start of each WO.

• plan-auditor

  Read-only audit agent that evaluates a work order against the 10-question WO-AUDIT-FRAMEWORK planning checklist. Returns structured findings with severity ratings. Use before approving any WO for implementation.

• security-auditor

  Isolated security audit agent that performs OWASP Top 10 analysis, secrets detection, injection pattern scanning, and PII exposure checks. Returns structured findings with severity and confidence ratings.

• test-auditor

  Isolated test quality audit agent that evaluates whether tests were written from spec, detects fallback masking, checks mock density, verifies edge coverage, and analyzes git history for TDD compliance.

• tester

  TDD agent that reads a WO spec and acceptance criteria, then writes tests BEFORE implementation exists. Never reads implementation code. Tests define expected behavior from the spec.

Hooks (7)

• SessionStart

  ${CLAUDE_PLUGIN_ROOT}/hooks/scripts/prereq-check.sh

• UserPromptSubmit

  ${CLAUDE_PLUGIN_ROOT}/hooks/scripts/intent-router.sh

• PreToolUse

  ${CLAUDE_PLUGIN_ROOT}/hooks/scripts/secrets-scan.sh

• PreToolUse

  ${CLAUDE_PLUGIN_ROOT}/hooks/scripts/frozen-files.sh

• PreToolUse

  ${CLAUDE_PLUGIN_ROOT}/hooks/scripts/test-file-protection.sh

• PreToolUse

  ${CLAUDE_PLUGIN_ROOT}/hooks/scripts/test-diff-audit.sh

• Stop