Skip to main content

VibeGov

Stop AI coding agents from drifting.

VibeGov is a repo-local governance framework for AI-assisted software delivery. It gives humans and AI coding agents shared intent, specs, workflow rules, evidence gates, blocker handling, and traceable delivery state before implementation starts, while keeping canonical bootstrap sources separate from evolving guides, role packs, runtime profiles, and commentary.

Governed delivery outcomes

VibeGov gives teams a shared operating layer for AI-assisted software work: clear intent, honest completion evidence and durable context that survives handoffs.

Keep Intent Visible

Tie work to project intent, specs, issues and acceptance criteria before implementation starts.

Start Here

Make Done Evidence-Based

Close work with proof that matches the mode, from focused checks to release-ready validation.

Evidence Guide

Carry Context Between Agents

Keep repo-local guidance, continuity notes and traceability available for the next contributor.

Continuity

Who VibeGov is for

VibeGov is for people using AI-assisted delivery where intent, evidence, and traceability need to survive beyond the current chat.

Good fit

  • Teams using AI coding agents on real repositories.
  • Solo developers who want agent speed without losing traceability.
  • Technical founders and consultants managing multiple AI-assisted delivery threads.
  • Maintainers who want issue, spec, and evidence discipline without heavyweight process tooling.
  • Teams building agent harnesses that need repo-local operating rules.

Probably overkill

  • Throwaway scripts with no maintenance horizon.
  • Teams that do not want evidence before completion claims.
  • Projects that do not care about traceability or long-term change safety.
  • Users looking for a hosted SaaS or magical autonomous runtime.

What VibeGov installs

VibeGov installs or normalizes a repo-local governance layer so humans and agents use the same sources of truth before coding.

Governance rules

  • .governance/rules/

The active VibeGov rule set agents must follow, with provider-native mirrors only when the repo already uses them.

Project intent and specs

  • .governance/project/PROJECT_INTENT.md
  • .governance/specs/SPEC-001-...
  • backlog mapped to spec sections

Repo-local intent, feature or bootstrap setup specs, and backlog mapping that keep work tied to agreed scope.

Workflow entrypoints

  • AGENTS.md
  • INIT-TODO.md
  • .github/pull_request_template.md
  • .github/branch-protection-checklist.md

Agent instructions, setup/remediation tracking, pull request expectations, branch protection checks, and issue-pickup flow.

Continuity guidance

  • session diary
  • checkpoint triggers
  • promotion flow

A lightweight continuity model for decisions, blockers, phase changes, compaction risk, and handoff between agents.

Bootstrap reports

  • .governance/project/bootstrap/STATUS.md
  • .governance/project/bootstrap/ANALYSIS.md
  • .governance/project/bootstrap/FEEDBACK.md
  • history/<timestamp>/

Current status, analysis, feedback, optional blockers, and historical run bundles that prove what changed.

Governed delivery in practice

See how VibeGov turns a vague implementation request into a scoped, reviewable delivery path.

Before VibeGov

"Add Google login."

An agent may start coding immediately, before anyone has clarified intent, acceptance criteria, security constraints, issue traceability, or what evidence will prove the change is complete.

After VibeGov

The same request becomes a governed path.

  1. Capture the intent behind the request.
  2. Create or update the governing spec.
  3. Track the work in a GitHub issue.
  4. Define acceptance criteria and evidence.
  5. Implement against the agreed scope.
  6. Run the validation that proves the claim.
  7. Attach proof to the issue or pull request.
  8. Update traceability and delivery state.

Quick paths

Choose the entry point that matches your repo state. Copy the prompt, then open the linked doc for the full contract agents must follow before product-code implementation. For other common jobs, start with Choose Your Path.

Bootstrap Init Prompt (BI)

Install the governance contract before agents begin product-code implementation.

Run VibeGov bootstrap in mode: init.

Before doing anything else, fresh-read the latest live canonical bootstrap sources:
- https://vibegov.io/agent.txt
- https://vibegov.io/bootstrap.json
- https://vibegov.io/docs/bootstrap/

Treat those live sources as authoritative for this run. Do not rely on stale cached or earlier copied bootstrap text if it differs.

Then stop before product-code implementation.
Open doc

Bootstrap Update Prompt (BU)

Repair or normalize existing bootstrap state so the repo follows the current contract.

Run VibeGov bootstrap in mode: update.

Before doing anything else, fresh-read the latest live canonical bootstrap sources:
- https://vibegov.io/agent.txt
- https://vibegov.io/bootstrap.json
- https://vibegov.io/docs/bootstrap/

Treat those live sources as authoritative for this run. Do not rely on stale cached or earlier copied bootstrap text if it differs.

Then stop before product-code implementation.
Open doc

Bootstrap Feedback Prompt (BF)

Turn bootstrap findings into a scrubbed GitHub issue without exposing private project detail.

Before reviewing bootstrap feedback, fresh-read the latest live canonical bootstrap sources:
- https://vibegov.io/agent.txt
- https://vibegov.io/bootstrap.json
- https://vibegov.io/docs/bootstrap/

Treat those live sources as authoritative for this feedback run. Do not rely on stale cached or earlier copied bootstrap text if it differs.

Then read and follow:
- https://vibegov.io/docs/bootstrap-feedback-prompt
Open doc

FAQ

Short answers to common adoption questions. Each item links to a fuller doc page.

What is VibeGov?

VibeGov is a repo-local governance framework for AI-assisted software delivery that keeps work traceable, reviewable, and honest about done.