How to run it

Levels from the manual. This is the Phase 0 start. The trial itself has not been run yet.

Back to vibecodebots. The repository.

  1. Level 1. Get the repo

    Take a copy of the public repository. Read the honest limits before you trust the rest.

  2. Level 2. Fill the two templates

    Copy mission-template.txt to mission.txt and fill it in. Copy brief-template.txt to docs/brief.txt and fill it in: scope, users, feature areas, domain safety rules, sources, and jurisdiction.

  3. Level 3. Set the budget and the caps

    The Owner sets three numbers: the Phase 0 credit budget, the weekly cap, and which providers, if any, may be used. Before any hosted call, set a hard spend cap with each provider.

  4. Level 4. Set up the repository

    Protect the main branch. Require checks. Keep a decision log. Create the artefact skeleton from the templates, including the decision log and the artefact index.

  5. Level 5. Load only what the task needs

    A bot loads CORE-PROMPT.txt first, then one persona card, then the task card, then only the document slices the task card names. It does not load the whole repository.

  6. Level 6. Start with seven bots

    Orchestrator, Project Manager, Product Owner, Architect, Developer, Tester, and Safety and Compliance. Every other persona stays dormant until its named trigger. The Owner approves waking one.

  7. Level 7. Reviews and approvals

    The author self-checks and attaches evidence. That self-check never counts as a review. Ordinary work gets one peer. Riskier work gets a reviewer on another model family, and the human Owner approves it. Releases are always the Owner.

  8. Level 8. Ask for a review in plain words

    Say the task, what is done and where the evidence is, what is not done, the risk class, and who should review it. The manual's handoff message is the form for that. A review writes a verdict with findings and evidence. It is not the author marking their own work.

  9. Level 9. Release

    Before notes, tags or publishing, the orchestrator tells the Owner three things, in order. Which changes are still unreviewed, and the release stays blocked unless the Owner records an acceptance. A short risk assessment, shown to the Owner. Then a short list of recommended reviews, each marked required or only advised. The building bot's own check never counts as a review.

Loaders

Ready-made setup files for the major vibe-coding apps are coming in the next framework update. They are not in the repository yet, so this page does not name them or link to them.