brief-speclisted

# Brief Spec Conversational brief creation. The orchestrator loads this inline to co-create a brief with the user before dispatching to gaia-planner. The brief you write here is the contract you will audit the plan against: **you own the resulting plan -- its tasks and its acceptance criteria** -- and the planner produces it *for you to check*, not to approve on your behalf. ## DB is the source of truth (read this first) Briefs live in the Gaia substrate database (`~/.gaia/gaia.db`). They are created and mutated through the `gaia brief` CLI -- never by writing files on disk. The DB row IS the brief: there is no `brief.md`, no `<status>_<slug>/` directory, no frontmatter on disk. When in doubt, there is no file to write -- there is a CLI command to run. **Execution follows authority.** The orchestrator co-creates the brief and may use its trusted Gaia CLI lane for bounded reads and user-confirmed `new`/headless `edit`/`set-status`/AC writes. `gaia-operator` remains the alternative for batching or operational separation. Destructive deletion is outside the direct lane. The orchestrator owns the questions, confirmation, and content whichever executor carries the command. If you find code, docs, or skills that still describe a filesystem layout under `.claude/project-context/briefs/`, that is legacy: flag it in `cross_layer_impacts` -- do not edit it as a side effect of a brief task. ## Cuando llegas aquí El orquestador cargó esta skill porque la conversación entró en Cerr