You use Atomic VCS (not git). A draft view is created for each session automatically.
atomic vault intent create --title "<short title>"This gives you an intent ID (e.g., HELL-4) and a file path.
The user's prompt is usually a solution ("build me X"). Reframe it as a problem statement.
Ask clarifying questions if the problem is ambiguous. Do not guess — ask.
Once the problem is clear, define:
- Problem statement — what problem are we solving and why
- Success criteria — concrete, testable conditions that mean "done"
- Tasks — ordered list of work items
Write all of this into the intent file. Replace every REPLACE placeholder.
Then run atomic vault sync to persist the file into the vault database. The intent file lives on disk, but atomic vault intent show/update read from the database — without sync they see the original placeholder template, and update will overwrite your file edits with it.
Work through the TODOs in order. After completing each one:
- Verify it meets its criteria — run the commands or checks specified in the TODO.
- Edit the intent file using your file editing tool to mark it done:
Also check off any acceptance criteria that are now satisfied.
- [ ] `PROJ-1/1` ... → - [x] `PROJ-1/1` ... - Sync so the database stays current:
atomic vault sync
Use your file editing tool to check off tasks — not bash, not Python, not sed. Raw file manipulation bypasses the vault.
atomic vault sync # persist file edits to the database first
atomic vault intent update <ID> --status doneAlways atomic vault sync before intent update — update re-materializes the database copy over the file, so an unsynced update discards your edits.
Do NOT run atomic add or atomic record. The hook system records your changes automatically with full AI provenance (model, tokens, session, timing) when the turn ends. (atomic vault sync is not record — it only moves your .vault/ edits into the vault database, and you must run it.)
- One intent per turn. Every prompt gets its own intent.
- Problem first. Reframe solution-requests as problems. Ask questions if unclear.
- Write the intent file before coding. The plan goes in the file, not just in chat.
- Use Atomic for code discovery. Before using shell
grep,find,rg, or similar filesystem search tools, first try the Atomic knowledge graph and content index:- Source text:
atomic vault query code "pattern" -t <type> - Structure:
atomic vault query search "term" - Relationships:
atomic vault query neighbors <node_id> - File outline:
atomic vault query entities <path>
- Source text:
- Only fall back to
grep/findif Atomic query commands fail, the repository has no content index/KG yet, or you need to inspect files that are not tracked/indexed by Atomic. If results are sparse, runatomic vault query enrichbefore falling back. - Do not run
atomic addoratomic record. Hooks handle this with provenance. - Do run
atomic vault syncafter editing any.vault/file, and beforeatomic vault intent show/update. It deflates your on-disk edits into the vault database; it is notrecordand hooks do not do it for you mid-turn. - Do not create or switch views. The session view is created automatically.
- Do not run
atomic agent enable. The integration is already configured globally.
Five skills are installed. Cascade sees their names and descriptions automatically. Invoke a skill with @skill-name when you need its full reference, or let Cascade auto-invoke based on what you're doing.
| Workflow step | Invoke | What it gives you |
|---|---|---|
| Step 1–2: Creating an intent, filling in problem/criteria/TODOs | @intent-builder |
Section structure, good/bad examples, simplification guard method, TODO format rules |
| Step 1–2: Searching the codebase to inform questions and scope | @codebase-context |
How to use atomic vault query commands to explore code before asking questions |
| Step 1–2: Finding code definitions, relationships, file structure | @code-intelligence |
Full atomic vault query reference — code, search, neighbors, entities, enrich |
| Step 1–4: Vault lifecycle — creating intents, goals, syncing, updating status | @atomic-vault |
All vault CLI commands, intent statuses, goal lifecycle, memory commands, sync rules |
| Anytime: Checking repo state, reviewing history, auditing provenance | @atomic-vcs |
status, log, change -p/-a, diff — read-only inspection commands |
- Before creating an intent, invoke
@intent-builderto load the section structure and TODO format. This prevents malformed intents. - Before your first question to the user, invoke
@codebase-contextand search the knowledge graph. What you find informs what you ask. - When you need
atomic vault querycommand syntax, invoke@code-intelligence. It has the full reference forcode,search,neighbors,entities. - When you need vault command syntax (
intent create,goal start,vault sync), invoke@atomic-vault. - When you need to inspect repo state or history, invoke
@atomic-vcs. These are read-only commands, safe to run anytime.