Turn meeting transcripts into tracked actions

Founder, PM, or team lead at 5-50 person company running 5-15 meetings per week; especially startups, agencies, consulting firms · Assemble in ~10 min; first structured summary in <3 min once installed.

Edit flowon X● golden 90

step 1connector

Ingest the raw transcript

⚡ bring your own tool

step 2ready

Structure the meeting notes

meeting-notes6 alts

step 3ready

Log and persist decisions

decision-logger

step 4ready

Broadcast the summary to the team

team-communications

step 5connector

Push tasks to project tracker

⚡ bring your own tool

step 6ready

Generate session handoff for next meeting

session-handoff

Did this recipe work for you?

What you get

▸Structured meeting minutes with decisions and owner-assigned action items
▸Durable decision log entry (two-layer: raw + approved)
▸Team update message ready to paste into Slack, email, or Notion
▸Session handoff document for the next meeting or attendee

tools: Transcript source free tier (Granola/Otter.ai) or existing Zoom license; project tracker per existing subscription

tokens: ~$0.50-1.50 per meeting (1-hour transcript ~8k tokens input)

≈ $5-20/mo in tokens at 5-15 meetings/week; tracker and transcript tools at existing cost

What stays yours

· Confirm owner assignments — the model assigns based on names mentioned but misattributions happen on ambiguous phrasing
· Approve the decision log before it becomes canonical (Layer 2 step in artifact 1941 is a human gate)
· Verify pushed tickets have correct priority and due dates before the team acts on them

✓ Last verified 2026-06-11claude-sonnet-4-6 (subagent, test-mode fixtures)

✓ step 1 · Ingest the raw transcript

✓ step 2 · Structure the meeting notes

✓ step 3 · Log and persist decisions

✓ step 4 · Broadcast the summary to the team

✓ step 5 · Push tasks to project tracker

✓ step 6 · Generate session handoff for next meeting

view sample outputs from this run

step 2 · Structure the meeting notes

# Meeting Minutes — Q3 Product & Growth Sync

**Date:** June 11, 2026
**Time:** 10:00–11:05 AM PST
**Facilitator:** Mia Chen (CPO)
**Attendees:** Mia Chen (CPO), Dara Obi (CTO), Lucas Ferreira (Head of Growth), Priya Nair (Lead Engineer), Sam Yoon (PM)
**Recorded:** Yes (Zoom auto-transcript, Meeting ID 891-234-567)

---

## Agenda

1. Onboarding redesign — ship timeline and sprint planning
2. Q3 growth targets and LinkedIn paid channel decision
3. API rate-limit incident post-mortem and remediation

---

## 1. Onboarding Redesign

**Context:** Design team completed Figma mockups on June 10. E…

step 3 · Log and persist decisions

# Decision Log Entry — Layer 1 (Raw Minutes Record)

**Session:** Q3 Product & Growth Sync
**Meeting ID:** Zoom 891-234-567
**Log entry created:** 2026-06-11
**Logged by:** Decision-Logger skill (automated)

---

## Raw Record

This is the Layer 1 verbatim capture — a faithful record of what was discussed and decided, in meeting order, before any editorial compression. Use this record if a decision needs to be traced back to exact words or context.

---

### Item 1 — Onboarding Redesign Sprint Planning

**What was said:**
- Priya estimated 5 engineering days (2 FE, 2 integration, 1 QA) for the…

step 4 · Broadcast the summary to the team

# Team Update — Q3 Product & Growth Sync

**Posted by:** Mia Chen (CPO)
**Date:** June 11, 2026
**Channel:** #product-growth (Slack) — also pinned in Notion: Product / Meeting Notes / 2026-06

---

Hey team — quick recap from today's sync. Three things happening this week; please check if you have a task below.

---

**Progress**

- Onboarding redesign mockups are done (thanks design team). Engineering kicks off today — Priya starts front-end now, integration tests follow Dara's API spec tomorrow.
- June signups are at 1,840/2,000. The onboarding redesign targets the exact step driving our 23%…

The problem

When a meeting ends, I want the transcript automatically parsed into a structured summary with decisions, action items assigned to owners, and updates pushed to Jira/Linear/Notion so that follow-through actually happens without a PM spending 30 minutes on admin.

Cybernetic layers

Memorypartial

Decision log (artifact 1941) gives a two-layer decision memory. Action item state across meetings (who closed what, what slipped) still requires a BYO tracker — the project tool in step 5 is the practical memory store for tasks.

Background / schedulingbyo

Running this pipeline after every meeting requires a trigger — either manual invocation or a webhook/cron tied to your transcript source (e.g., Granola webhook, Fireflies Zapier integration). No harvested scheduling artifact covers this end-to-end yet.

Harnessready

Claude Code is the runtime. Install the three ready skills (artifact IDs 6862, 1941, 2666, 4772) into ~/.claude/skills/ and invoke in sequence per meeting.

Click any step to see what fills it — and the ranked alternatives you can swap in.