Skip to main content

VibeGov

Portable delivery judgement for AI-assisted software.

Publish governance guidance one page at a time while keeping the site live and feedback-driven.

Quick Start Prompt

Copy this into your IDE agent to adopt VibeGov behavior quickly.

Adopt VibeGov governance from https://governance-foundation.github.io/vibegov.io before any implementation.

Read:
- https://governance-foundation.github.io/vibegov.io/agent.txt
- https://governance-foundation.github.io/vibegov.io/bootstrap.json

Initialization contract:
1) Ensure `.governance/` exists with:
   - `.governance/rules/`
   - `.governance/project/`
   - `.governance/specs/`
2) Treat `.governance/rules/*.mdc` as governance-only constraints.
3) Treat `.governance/specs/*` as the only feature/change spec source.
4) Detect any provider-native rules directory that already exists in the repo. If found, sync `.governance/rules/*.mdc` into it and report the exact target(s).
5) If none exist, do not invent placeholder paths; continue with `.governance/rules/*.mdc` only.
6) Before coding, create:
   - `.governance/project/PROJECT_INTENT.md`
   - `.governance/specs/SPEC-001-<feature>.md`
   - backlog/tasks mapped to spec sections.
7) List active rule files before coding.

Execution gate:
- Do not start coding until initialization is complete and reported.

Completion report:
- summarize applied governance rules
- report validation evidence
- list ambiguity/conflicts/deviations

Publish Increments

Release one governance page at a time while keeping a public, stable site online.

Start Here

Collect Signal Early

Every page has a feedback path to GitHub Issues so ambiguity gets resolved in public.

Contribute

Build Durable Guidance

Keep governance directional and reusable, while project-specific details evolve separately.

Published Rules