TL;DR · 10 seconds
A live Claude Artifact reads 8 weekly 1:1 docs from Drive and surfaces patterns no single meeting can show — deduped action items, goal-health drift, recurring manager promises.
- Download the sample artifact PDF (3 pages) — exported from Joe's actual working build.
- Page 1: stat cards + quarterly goal tracker + the recurring-pattern callouts (“Marcus has promised the same thing in 8 of 8 meetings”).
- Pages 2 + 3: deduped action items (Mine vs Marcus's) + recent-meetings timeline. Drive-connected live version ships when public permissions land.
Sprint 02 · Your Own Leverage · Cowork Tier · Entry Difficulty
1:1 Patterns Tracker.
A Claude Live Artifact that reads 8 weekly 1:1 meeting docs from a Google Drive folder and surfaces patterns no single meeting note could show on its own — deduped action items across the quarter, goal health by mention frequency, recurring themes, and the manager promise that keeps appearing and never lands. Sample artifact published below as a static PDF + preview; the Drive-connected live version ships once permissions land.
Tier
Cowork · Entry
Build time
~1 afternoon
Persona
IC + Manager
Output
Live Artifact
Exhibit · Sample Artifact Preview
What the artifact actually renders.
This is page 1 of the artifact's actual output — exported as a static preview. Stat cards (open action items, manager-owes-you count, days since last 1:1, goals on track) ship up top, the quarterly goal tracker is colour-coded by health, and the recurring-pattern callouts (the “Marcus has promised the same thing in 8 of 8 1:1s” insight) sit in their own highlighted block. Pages 2 and 3 carry the deduped action-item queue and recent-meetings timeline — see the full PDF below.
Section I
What the artifact does.
Universal pain. Every IC has 1:1s. Every IC forgets what was discussed. Every IC has goals they meant to track. The 1:1 Patterns Tracker reads all 8 weekly 1:1 docs from a Google Drive folder and surfaces what no single meeting note could show — recurring themes across the quarter, action items that keep being promised and never shipped, goals that quietly died when something else got loud.
The artifact does three things a static page can't. It pulls fresh data on every open (your Google Docs are still the source of truth — nothing got migrated). It uses Claude inline to write the per-meeting summaries (real AI inference happening in the page, not pre-baked). And it surfaces patterns across the data that you couldn't see by reading any single doc. That last one is the actual unlock — the message-not-the-medium of the whole concept.
Your mental model shifts from “AI chat” to “AI is a synthesis layer over my existing tools.” That shift is what the sprint version of this build teaches — your 1:1s, your project notes, your weekly status reports, whatever recurring writing you already do.
Section II
What the artifact surfaces.
3 excerpts · pulled from the live build
Three signals the artifact returns. Each one is the kind of cross-document pattern you cannot see by reading any single 1:1 — only the synthesis layer makes it visible.
Insight 01
“Marcus has promised the same thing in 8 of 8 meetings.”
The artifact dedupes action items across the entire quarter and ranks them by recurrence. The top item — 'Marcus to send the headcount plan next week' — appears in every 1:1 over Q2 and has shipped zero times. That pattern isn't visible if you read any single meeting note. The artifact surfaces it on first open.
Insight 02
“System design keeps being your goal — until migration intensifies.”
Goal health is computed from how often each goal was discussed across meetings. 'Lead system-design review' opens Q2 strong (mentioned in 4 of the first 4 1:1s) then drops to zero the moment the data-pipeline migration kicks off. The pattern reads as a real signal: the goal isn't dead, it's been crowded out. The artifact flags it; the IC sees it before their year-end review.
Insight 03
“Capacity is the recurring theme you keep raising and nothing changes.”
Recurring-theme detection picks up that 'capacity' (or its synonyms — bandwidth, headcount, swamped) appears in 7 of 8 meetings. The artifact surfaces it as a top recurring topic with a sentiment trend. The IC's actual move: print it for the next 1:1.
Section III
What the artifact reads.
One source surface — Google Drive — and one synthesis surface — the Live Artifact. The artifact is the whole tool; Drive is the source of truth.
8 weekly 1:1 Google Docs
Q2 2026 worth of 1:1 meeting notes between an IC and their manager Marcus. Each ~1-2 pages with structured sections: agenda, discussion, action items (mine + theirs), goals review. Realistic continuity — recurring capacity theme, slipping action items, a manager promise that never lands across the entire quarter.
Live Artifact (HTML)
Single-page Claude Artifact that reads all 8 docs from Drive on every open, parses structured sections, dedupes action items across meetings, computes goal health from mention frequency, detects recurring themes, and renders a polished single-page synthesis view. Uses Claude inline for per-meeting summaries.
Section IV
Build path · 5 steps.
How this gets built. Total ~1 afternoon if your 1:1 corpus is already in Drive. The Builders' version is the same shape — your meetings, your template, your patterns.
01
Set up the source corpus in Google Drive
Create a Drive folder with weekly 1:1 docs. Use a consistent template — agenda / discussion / action items (mine + theirs) / goals review. Consistency is what lets the artifact parse structured fields cleanly across meetings. For the demo, 8 weeks across Q2 with woven continuity (recurring themes, slipping action items, a never-lands manager promise).
02
Connect the Cowork connector
claude.ai → Connectors → Google Drive → grant read-access to the 1:1s folder. The Live Artifact will pull fresh data from this connector on every open. Source of truth stays in Docs; nothing gets migrated.
03
Build the Live Artifact
claude.ai → Artifacts → 'Build a 1:1 patterns tracker that reads my weekly 1:1 docs from this Drive folder. On every open, fetch all docs, parse the structured sections, deduplicate action items across meetings, compute goal health from mention frequency, and surface recurring themes.' Claude generates the HTML + parsing logic + inline-summary calls in one shot.
04
Iterate with peer feedback
First version surfaces patterns; second version adds the rubric callouts ('promised X times, delivered Y'); third version adds the timeline view with cached AI summaries per meeting. Each iteration is a single Claude conversation — refining the artifact in place.
05
Share publicly
Click Share → 'Anyone with the link.' The artifact is now a live URL the IC can bookmark and reload anytime. Edit a 1:1 doc in Drive, reload the artifact, watch the count tick up — that 15-second sequence is the whole pitch.
End of Specimen No. 05
Now build yours.
The 1:1 corpus is sample data. The shape of the build is portable: your weekly 1:1s, your project status updates, your standup notes. Same five steps, same Live Artifact pattern — your inputs. The Sprint 02 Cowork-Entry build is one of six modalities you can pick for this skill in the sprint.
One real workflow. One working tool. One sprint.