Quarterly Connection

Quarterly Connection

Produce Workday-ready quarterly connection text: one executive bullet per priority for the past 90 days (WHAT + HOW accomplishments) and one bullet per priority for the next 90 days (expected outcomes).

Scope: Chris Gray and the Global Renewals, Dealmaking, and Ecosystem team — not personal-only.

Prerequisites

1. gws CLI authenticated (gws auth status). Scopes: calendar, gmail, tasks, drive, documents, presentations.
2. Read ME.md at the project root (if present).
3. Read TEAM.md at the project root (if present) for team context when synthesizing.
4. Priority source must be specified by the user — do not infer silently from TEAM.md.

Workflow

Quarterly Connection:
- [ ] Step 0: Confirm priority source and date window
- [ ] Step 1: Check connections (refresh-connections)
- [ ] Step 2: Extract priorities from user-specified source
- [ ] Step 3: Gather 90-day evidence
- [ ] Step 4: Read Workday guidance
- [ ] Step 5: Map evidence to priorities and synthesize bullets
- [ ] Step 6: Save output and present for Workday paste
- [ ] Step 7: Confirm with user and ask for feedback

Step 0 — Required intake (hard gate)

Stop and ask if the user has not specified the priority source.

Priority source options (user picks one):

1. Google Slides — deck URL/ID + slide number(s), e.g. CY26 Executive Summary, slides 3–7
2. Google Doc — doc URL/ID with priority sections
3. TEAM.md — Our Priorities section only (when user explicitly names it)

Example CY26 deck (reference in TEAM.md): 1nOkeUfWYdk_pYyRI7OiJ0nETdrse79LiYXtqXfZMBSU

Step 1 — Check connections

python3 ~/.cursor/skills/refresh-connections/scripts/check_connections.py \
  --project-mcp .cursor/mcp.json

gws must pass. If auth fails, run gws auth login before continuing.

Step 2 — Extract priorities

python3 ~/.cursor/skills/quarterly-connection/scripts/extract_priorities.py \
  --deck-id "<DECK_ID_OR_URL>" \
  --slides "3-7" \
  --format json > /tmp/quarterly-priorities.json

Alternates: --doc-id <id>, --team-md /path/to/TEAM.md

Validate 5–8 top-level priorities with the user if extraction is ambiguous or slide bodies are thin.

Step 3 — Gather evidence

python3 ~/.cursor/skills/quarterly-connection/scripts/gather_quarterly_connection.py \
  --priorities-json /tmp/quarterly-priorities.json \
  --lookback-days 90 \
  --forward-days 90 \
  --format json > /tmp/quarterly-evidence.json

Review counts and warnings in the bundle before synthesizing.

Step 4 — Read Workday guidance

Read data/workday-guidance.md. If older than 30 days, refresh via thesource skill (quarterly connections, performance development) and update the cache file.

Verbatim reflection prompt (accomplishments section):

What accomplishments are you most proud of last quarter? Reflect not only on WHAT you've accomplished but also on HOW you've accomplished it.

Step 5 — Synthesize bullets

For each priority, produce exactly one bullet in each section.

Past 90 days — Accomplishments

• {Priority title}: {WHAT — concrete team outcome} — {HOW — leadership/operating model used to deliver it}

Evidence hierarchy:

1. Sent emails / leadership communications authored by Chris
2. Gemini notes / meeting outcomes from calendar
3. Completed Google Tasks tied to priority keywords
4. Calendar forums where strategy was advanced

Use team names from TEAM.md when attributing org outcomes. Mark gaps [needs input] — never invent metrics.

Next 90 days — Forward look

• {Priority title}: {Expected accomplishment by end of forward period — specific, measurable where possible}

Derive from: open tasks, stated next steps in recent emails/notes, deck expected outcomes, in-flight programs.

Step 6 — Save output and present

Use this template:

# Quarterly Connection — {Quarter label, e.g. Q2 2026}

**Priority source:** {deck/doc/TEAM.md reference}
**Period reviewed:** {startLabel} – {endLabel}
**Forward period:** {endLabel} – {forwardEndLabel}

## Reflection prompt
What accomplishments are you most proud of last quarter? Reflect not only on WHAT you've accomplished but also on HOW you've accomplished it.

## Accomplishments (past 90 days)
• ...
(one bullet per priority)

## Priorities and expected accomplishments (next 90 days)
• ...
(one bullet per priority)

## Notes for Workday entry
{Field tips from workday-guidance.md}

Delivery:

1. Present in chat for copy/paste into Workday
2. Save to notes/quarterly-connection-{YYYY-MM-DD}.md in the active project
3. Email (HTML for Workday): send with send_quarterly_connection.py so bullets render as <ul><li> HTML in Gmail — copy from the email into Workday rich-text fields.

python3 ~/.cursor/skills/quarterly-connection/scripts/send_quarterly_connection.py \
  --subject "Quarterly Connection - {label} - {Month Day, Year}" \
  --body-file notes/quarterly-connection-{YYYY-MM-DD}.md

The script builds multipart plain + HTML via lib/gmail_mime.py (quarterly_connection_to_html). Priority titles before the first : are bold in HTML. Use --force to resend the same subject.

Workday paste from email: Open the message in Gmail, select the Accomplishments or Forward bullet list, copy, and paste into the matching Workday rich-text field. See data/workday-guidance.md.

Do not auto-submit to Workday.

Step 7 — Confirm with user

Report: priority count, evidence counts (emails/events/tasks/notes), warnings, notes file path.

Ask feedback on: priority alignment, WHAT/HOW balance, forward bullets. Update this skill or reference.md from recurring feedback.

Example prompts

• "Quarterly connection using CY26 Executive Summary slides 3–7"
• "Quarterly connection from TEAM.md priorities"
• "Prepare my Workday quarterly connection for the last 90 days"
• "Quarterly self-assessment — priorities from slide deck 1nOkeUfWYdk_pYyRI7OiJ0nETdrse79LiYXtqXfZMBSU slides 3-7"

Additional resources

• reference.md — JSON schemas, flags, troubleshooting
• data/workday-guidance.md — Workday / Talent Management tips