Update an EXISTING Account Context Brief with new information. Use when the user says "update the brief", "add this to the brief", provides new transcripts/emails/notes for an account that already has a Context.md, or after a call when new information needs to be merged into an existing brief. Do NOT use this for creating a brief from scratch — use the create-account-brief skill instead.
Update an existing Account Context Brief by merging new information while preserving existing content. This is for incremental updates, not full rebuilds.
Briefs live in Obsidian:
/Users/nick.yebra/Library/Mobile Documents/iCloud~md~obsidian/Documents/Core Vault/Regal/Accounts/<account-name>/Context.md
When gap-filling searches are needed (Step 4), use these named agents via the Task tool (subagent_type):
| Agent | When to Use | Wave | max_turns |
|---|---|---|---|
salesforce-researcher | Verify contact titles, check deal status changes, confirm opportunity details | 1 | 3 |
obsidian-locator | Discover recent account files (not transcripts) | 1 | 5 |
transcript-locator | Discover transcripts since last brief update across all sources | 1 | 7 |
obsidian-analyzer | Read account files for context (not transcript content) | 2 | 3 |
transcript-analyzer | Read and extract data from locator-discovered transcripts | 2 | 8 |
Each agent knows its tools and behavioral constraints. When dispatching:
Read Regal/org-context/org-context.md from Obsidian (obsidian_get_file_contents) for Regal product overview, terminology, ICP summary, and key metrics.
For deeper context, also read this sub-file from Obsidian:
Regal/org-context/product.md — platform capabilities, use cases by industry, buyer personasReference these to inform ICP fit assessment, deal stage context, and product positioning when interpreting new account information.
Determine which account to update from user input, uploaded files, or conversation context.