VIBESTRATE.md
A committed manual at your project root that the orchestrator reads before every task, so you never re-explain your project.
VIBESTRATE.md is a committed file at your project root that tells the orchestrator what this project is and how you like it run. It reads the file before every task, so you never re-explain your project.
The operating manual, not a hard rule. VIBESTRATE.md is durable, project-aware guidance the orchestrator leans on. It is advisory: it shapes how a run is planned, but it can never override a code-enforced policy.
What goes in it
Keep it concise and prune it. Suggested sections, written in plain prose:
# VIBESTRATE.md
## Project Model
What this project is, its domains, architecture boundaries, critical flows.
## Development Commands
Install, test, typecheck, lint, build, run locally - in order.
## Orchestration Preferences
Preferred flows and crews; when to use heavier review; when to stay lean.
## Risk Rules
When to propose sandbox mode, approval gates, isolated execution, extra
validation. (e.g. "propose sandbox mode when a task touches provider execution
or secret/credential paths.")
## Codebase Conventions · Known Constraints · Lessons LearnedHow it ranks against other guidance
It is distinct from .vibestrate/rules.md, and the precedence is explicit:
| Layer | What it is | Enforced? |
|---|---|---|
Policy (.vibestrate/policies/) | Hard, code-enforced gates | Yes - code |
VIBESTRATE.md | The orchestrator’s operating manual | No - advisory |
.vibestrate/rules.md | Per-turn prompt guidance for roles | No - advisory |
VIBESTRATE.md is advisory to the orchestrator, its durable project model. It can never override a code-enforced gate.
Ask it questions
You don’t only write to VIBESTRATE.md. You can also ask the orchestrator about your project and get an answer grounded in it. That read-only advisor is Consult.
Related: consult, safety, configuration.
