Consulting Account Reality

Workspace: use the selected project and its AGENTS.md; keep existing entity folders and Reality headings. Business paths below are relative to that project. Bundled resources are relative to this installed skill; sibling capabilities resolve by their installed names. Never search another private checkout for missing inputs. Use workspace identity, audience, pricing, and DESIGN.md fonts.

Produce an evidence-grounded, honestly-caveated picture of where one account actually stands — and keep the agent from mistaking activity for outcomes. The output is the ## Reality block at the top of the entity's AGENTS.md (canonical shape: clients/<client>/AGENTS.md).

Fictional example: a consultant sees completed pull requests for Cedar Lantern Studio and calls the new system widely adopted. The pull requests establish build activity, not usage. Obtain usage evidence or mark it missing. Build ≠ usage; CRM stage ≠ account health.

Steps

1. Scope to ONE entity (deal-scoped). Load only that account's clients/<client>/ or pipeline/<stage>/<deal>/ folder + its AGENTS.md. Never load the whole lake.
2. Traverse every channel — collect, don't conclude. Fan out (parallel subagents for speed), one per source, each on a strict "cite source + quote; do NOT interpret" brief:
   • Granola notes (integrations/granola/<workspace>/clients|prospects/<entity>/) — verify any figure against the verbatim transcript (?include=transcript), not the AI summary.
   • Gmail thread (integrations/gmail/threads/<entity>.json) — who owes the reply, last ball.
   • Slack deal channel(s) (routing table in integrations/slack/AGENTS.md) — async delivery state.
   • Attio live (ATTIO_API_KEY) — stage, $, people (reconcile-on-touch).
   • GitHub (only if we build product for them) — build activity, explicitly NOT adoption. Each subagent returns cited facts and a list of what that channel could NOT tell you.
3. Synthesize + separate activity from outcome. Reconcile across channels. Distinguish build/commits from adoption, CRM stage from health, a plan from a commitment. Anything not directly evidenced → [MISSING]; never infer success from volume. Re-verify any subagent's numbers against the source.
4. Write the ## Reality block at the top of the entity AGENTS.md: where it stands, what the customer actually values, the highest-leverage next move, risks, and an explicit [MISSING] list. If the owner hasn't confirmed it, label it DRAFT — agent-reconstructed, the owner to confirm (never present a reconstruction as the owner's stated view). Keep a dated Challenge log.
5. Apply the value ladder. Flag whether the best next move is communication / an artifact / a proactive update / presence / aggressive execution — before defaulting to building product (slow, expensive). Match the move to what THIS account values right now.
6. Report what needs the owner. Surface the [MISSING] gaps + any money/dates to confirm. Never auto-send; confirm before writing client facts into the dashboard.

Resolve <workspace> from integrations/granola/AGENTS.md; preserve the existing mirror directory name.