Continuation prompts¶
A project is alive while someone can pick it up. These prompts are written so that anyone with any capable AI agent — including the sovereign default, gpt-oss on Ollama — can pick vibey up cold: no memory of past sessions, no knowledge of who built it, no access to anyone who did. Each one is self-contained. Paste it into an agent whose working directory is a clone of this repository, and it says what to read, what to run, what never to do, and how to know the work is done. Sub-doctrine 10.l is the law they keep, and ADR-0080 is how.
They are not left to rot. scripts/continuation_prompts.py check runs on every pull
request and fails when a prompt names a file, command or workflow that no longer exists, when
a lane or an agent skill is covered by no prompt, or when a page's generated state is stale.
And GitHub runs them: every week the
Continuation prompts
workflow keeps every scheduled workflow enabled, refreshes these pages, and runs each prompt
on a GitHub-hosted runner with an open-weights model — the act prompts may open draft pull
requests, the drill prompts verify that every instruction still holds and report what
does not. Nothing it runs can merge, approve, release, delete, or touch a ruleset or a secret.
Rendered from the repository at vibey-engine 4.4.0, with 88 decision records and 34 workflow lanes, all covered. Regenerated by scripts/continuation_prompts.py; do not edit inside these markers.
| Prompt | Mode | What it is for |
|---|---|---|
| Resume | act | Orient in the repository as it stands and continue delivery where it left off. |
| Keep develop green | act | Find every failing workflow on the integration branch, fix its cause, and land the fix. |
| Release | drill | Derive the version, promote develop to main, and verify every channel and every asset. |
| Triage | act | Keep the backlog, the tracker and the roadmap truthful. |
| Keep the documentation true | act | Find one statement in the documentation, the paper or the book that the repository contradicts, and correct it. |
| Work the backlog | act | Take this run's backlog item and land its smallest shippable, tested slice. |
| Research and measurement | act | Keep every weekly measurement and every registered study running without breaking its protocol. |
| Succession | drill | Hand the project to a new steward: what they must hold, where it is declared, and how to verify it. |
| Rebuild | drill | Reconstitute the project from any surviving copy if the forge, the runner or the operator is gone. |
| Chat | chat | Answer a trusted person who writes /vibey in an issue, a pull request or the Actions tab. |
If everything else is gone¶
Start with Rebuild. It assumes nothing survives but a copy of the code — a clone, a release's source distribution, or the book — and walks back from there.