Monday Brief

Run the Monday briefing chain. Three skills, one document. The owner should read it in under two minutes and know exactly what their week is.

Parse arguments: - `--post` (default `none`) — post the summary to `slack`, `teams`, or `none` - `--save-to` (default `files`) — `files` (Drive / OneDrive), `desktop`, or `both`

## Step 1 — The snapshot (business-pulse)

Run `business-pulse` with the **Monday preset** — full pulse, forward-looking.

- **In:** nothing. The skill discovers its own connectors. - **Out:** cash position, sales trend, pipeline movement, watch-list items, and the risks it flagged by name. With Shopify connected, the sales trend and any fulfillment problems come from live Shopify orders, not just the ledger. With TikTok Ads connected, the pulse adds last week's ad spend and cost per result beside the sales trend, so Monday opens with whether the paid push earned its money. With Expensify or Ramp connected, it adds last week's card spend and flags expenses missing receipts. Stripe adds failed payments and new disputes, DocuSign adds contracts sitting unsigned, and RingEx Chat plays Slack's role for RingEx shops. - **Gate:** none. This is read-only and it is the floor of the brief — if every connector is dark, the pulse still returns "n/a" rows and the chain continues.

Do not recompute any number this step produced. Later links cite it; they never recalculate it.

## Step 2 — The owner's KPI pack (report-builder)

Run `report-builder` in saved-report mode only.

- **In:** the current date and "Monday" as the cadence match. - **Out:** the chat summary for every saved report whose cadence is weekly or Monday, per report-builder's saved-reports file (`../report-builder/reference/saved_reports.md`). - **Gate:** none.

**If no saved report matches, skip this step silently.** Do not apologize, do not explain, do not offer to build one inside the brief. An owner who has never defined a report should get a two-part Monday brief that reads as complete. Offer report-building once, at the very end, and only if they seem to want more.

**Never interview the owner about a new report inside this chain.** Monday morning is the wrong moment for a spec conversation. If they ask for a new report, hand off to `report-builder` directly and end the brief.

## Step 3 — The week ahead (read it directly)

Run this leg inline, widened from the day to the week. Read Google Calendar for the week's commitments and the connected mailbox (Gmail or Microsoft 365) for open threads where the owner owes someone an answer. Carry the Step 1 pulse forward rather than recomputing any of it — one set of cash numbers, from one place.

- **In:** the pulse from Step 1, plus Calendar and mail if connected. With neither connected, ask the owner for the week's three big commitments and build from that. - **Out:** the week's shape (not a calendar readout), open commitments now due, and the one thing. - **Gate:** none for reading. Any follow-up email, invite, or calendar block it proposes is drafted, never sent.

Widening means the week's shape, not five daily briefs stapled together. Where are the real work blocks. What travel breaks the week. Which day is already lost.

## Step 4 — Merge into one document

**One Monday document, not three reports in a row.**

Merge rules: - Cash, sales, and pipeline come from Step 1 and appear once. - Saved-report findings fold into the section they belong to. A saved "labor percent" report belongs next to the cash line, not in an appendix. - The week ahead and open commitments come from Step 3. - **The one thing closes the document.** Pick one and say why — the deadline, the dollar amount, the person waiting. - Every number carries its comparison. Missing sources are named once, in a short line at the bottom, not apologized for three times.

Example close, Okonkwo Mechanical: "The one thing: Rosewood's USD 12,400 invoice is 41 days out and their site visit is Thursday. Ask for the check in person."

## Step 5 — Deliver, save, and optionally post

**Deliver per the owner's stored output preference — never default to a markdown file.** Check the `## Business context` block's `Output preference` (shared style guide rule, `../../shared/artifact-style.md`):

- **Visual artifact (the default):** publish the merged brief as a one-page HTML document in the house style — sections for cash, sales, pipeline, the week ahead, and the one thing. Cash, sales, and pipeline headline numbers are stat tiles with their comparisons as context lines; saved-report findings fold in as table rows with tabular-nums; watch-list items carry status pills (warn or critical); the one thing closes the page in its own panel; missing sources go in one quiet footer line. The artifact is additive — the short answer still lands in chat. A markdown dump in chat is the fallback only when artifacts are unavailable, and say so when it happens. - **docx / md / notion / canva preference:** deliver the same content in that form — a DOCX or mar