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: you co-create, gaia-operator persists.** This skill is loaded inline by the orchestrator, which carries no shell -- every `gaia brief` command below (`new`, `ac add`, `ac remove`, `show`, `edit`, `set-status`, `delete`, `list`, `search`) is executed by dispatching gaia-operator with the exact command; gaia-operator relays the printed row or slug back to you. Wherever this skill says "run" a `gaia brief` command, read it as "dispatch gaia-operator to run" -- you own the conversation (the questions, the confirmation), never the CLI execution itself. 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` -