Lab
Small tools that do program work
Claude skills, Claude API tools and workflows I’ve built to take repetitive work off a program manager’s plate. Each one started as a recurring chore. Client work is described without naming the client.
Consulting engagement · 2026
Claude Code skillProgram brain
- The chore
- On a large transformation program, decisions and commitments were scattered across Slack, Drive and dozens of meetings. Nobody could quickly answer who decided what, or where a task came from.
- What it does
- A structured knowledge base of people, initiatives, decisions, risks and actions, plus a corpus of exact quotes from Slack, documents and transcripts. A Claude skill searches it with a script, so the model never loads the whole thing, and every answer cites its sources.
- Result
- Status reporting inputs and 'who owns this?' questions now take minutes, with every answer traceable to a source.
Consulting engagement · 2026
Claude Code skillTranscript attribution
- The chore
- Meeting transcripts arrive as SPEAKER 1, SPEAKER 2. Without names, they can't feed a decision log.
- What it does
- Works out who each speaker is from clues in the conversation: direct address, self-introductions, hand-offs, who owns which document, and elimination against the attendee list. It also corrects names the transcription got wrong, checks its reasoning with me, then exports clean Markdown with names.
- Result
- Transcripts that can be used as program records and loaded straight into the program brain.
Mailchimp · 2025
Claude APICapacity model
- The chore
- Capacity planning ran on gut feel and stale spreadsheets, so roadmap commitments didn't match what teams could deliver.
- What it does
- A data-driven model built with the Claude API that analyses months of sprint data and velocity to show real team capacity for planning and resourcing.
- Result
- Adopted across the wider program management org.
Mailchimp · 2024
AI-assisted workflowDesign review synthesis
- The chore
- Design leadership spent hours turning review notes into decisions and follow-ups, and blockers across teams got missed.
- What it does
- A workflow that summarises design review notes and flags blockers across teams for design leadership.
- Result
- Less time spent on manual synthesis, and blockers raised sooner.
Mailchimp · 2025
Slack workflowBug intake in Slack
- The chore
- Bugs came in through DMs and side threads and were lost before anyone triaged them.
- What it does
- A Slack workflow anyone in the org can use to submit a bug. It feeds a live tracker in Google Sheets.
- Result
- One intake path that replaced manual collection.
MASHA · 2025 – 2026
Claude skillBox scores from photos
- The chore
- Before MASHA 2.0, every game lived on a paper scoresheet that someone had to type up by hand.
- What it does
- Turns photos of paper box scores and attendance sheets into HTML box scores, a stats CSV and standings. It reads every scoring row twice to catch missed assists, and checks the goals add up to the final score.
- Result
- Kept the league's stats going for a season until live scoring replaced paper entirely.
MASHA · 2025 – 2026
Claude skillLeague history brain
- The chore
- Five seasons of stats, awards and champions were spread across sheets, so draft prep and season previews took hours of digging.
- What it does
- A structured history of player and goalie stats, awards, standings and championships. It answers questions and writes previews based on the data, with rules that stop it confusing regular-season leaders with champions.
- Result
- Draft night rankings and previews in minutes, grounded in real data.