Skip to content

productivity: add ~~conversation intelligence connector category (Fireflies + Grain) — meeting-derived task and memory seeds#261

Open
adams wants to merge 1 commit into
anthropics:mainfrom
adams:grain-add-productivity
Open

productivity: add ~~conversation intelligence connector category (Fireflies + Grain) — meeting-derived task and memory seeds#261
adams wants to merge 1 commit into
anthropics:mainfrom
adams:grain-add-productivity

Conversation

@adams
Copy link
Copy Markdown

@adams adams commented May 26, 2026

What this changes

Introduces a new ~~conversation intelligence connector category to the productivity plugin and wires meeting transcripts into both start (memory bootstrap) and update (task sync + comprehensive scan) skills. Fireflies and Grain are the Included MCP servers (matching the existing multi-included pattern in ~~project tracker); Gong, Granola, Chorus, Otter.ai are listed as alternates.

Files touched

File Change
productivity/.mcp.json Add fireflies server block (URL: https://api.fireflies.ai/mcp) and grain server block (URL: https://api.grain.com/_/mcp)
productivity/CONNECTORS.md Add new row: Meeting transcription | ~~conversation intelligence | Fireflies, Grain | Gong, Granola, Chorus, Otter.ai
productivity/skills/update/SKILL.md (a) Add conversation-intelligence as a task source pulling open action items into TASKS.md under a "Meeting Action Items" section (Section 2); (b) add meeting decisions/attendees to Capture Enrichment (Section 6); (c) add meeting transcripts to Comprehensive-Mode Scan Activity Sources
productivity/skills/start/SKILL.md Add meeting transcripts to comprehensive-scan source list in memory bootstrap (Section 6), with note that meeting transcripts are the highest-density source of workplace shorthand (nicknames, project codenames, internal terms)

What stays the same

  • Two-tier memory architecture (CLAUDE.md working memory + memory/ deep storage)
  • The local dashboard.html UI
  • --comprehensive flag semantics and interactivity guarantee
  • memory-management skill workflow, lookup flow, promotion/demotion rules
  • task-management skill structure and TASKS.md format (Meeting Action Items just becomes a new section within the existing structure)
  • Behavior for users who don't connect a ~~conversation intelligence MCP — all new functionality is gated and additive

Why this matters

The productivity plugin's core value is "Manage tasks, plan your day, and build up memory of important context about your work." Today, productivity/update --comprehensive "scans chat and email to catch todos buried in" — but meeting transcripts are the highest-signal-per-byte source of open commitments, decisions, and people-to-remember, and they're absent from the plugin's connector surface. memory-management decodes acronyms / nicknames / project codenames from email and chat, but the recurring weekly-1:1 cadence and customer-call participants that populate someone's working memory live in meetings.

This PR closes that loop while preserving everything that already works.

Scope decisions worth flagging for review

  1. Category placeholder name. Sales uses ~~conversation intelligence; product-management uses ~~meeting transcription. This PR follows sales (~~conversation intelligence) because the category-vs-tool naming is more accurate (Fireflies/Grain/Gong aren't just transcribers — they're full conversation intelligence platforms). Happy to align to product-management's ~~meeting transcription for repo consistency if preferred.
  2. Both Fireflies and Grain bundled in .mcp.json. Because this is a new category, both MCP blocks are added. This matches the parallel PRs adding Grain alongside the already-bundled Fireflies in sales/ and product-management/. If you'd prefer only one bundled with the other listed as an alternate, easy swap.
  3. Skill edit footprint. Edits to update/SKILL.md and start/SKILL.md are deliberately minimal — three additions to update/, one addition to start/. Could go larger (e.g., new dedicated Section 2.5 "Pull Meeting Action Items" with full subsection structure) — flagged it small to keep reviewer surface manageable, but happy to expand if more structure helps.

Also happy to split this into a two-PR sequence if a smaller first step would be easier: (a) connector category + .mcp.json first; (b) skill edits in a follow-up.

MCP details

  • Grain MCP: https://api.grain.com/_/mcp — launched June 2025 (release notes, developer docs). Used in production by Grain customers and Grain's own internal automation.
  • Fireflies MCP: https://api.fireflies.ai/mcp — already bundled in sales/ and product-management/.

— Mike Adams, Founder/Chairman, Grain (grain.com)

Introduces a new ~~conversation intelligence connector category to the
productivity plugin and wires meeting transcripts into both start
(memory bootstrap) and update (task sync + comprehensive scan) skills.
Fireflies and Grain are the Included MCP servers (matching the existing
multi-included pattern in ~~project tracker); Gong, Granola, Chorus,
Otter.ai are listed as Other options.

Changes:
- .mcp.json: add `fireflies` and `grain` server blocks
- CONNECTORS.md: add new ~~conversation intelligence row
- skills/update/SKILL.md: (a) conversation-intelligence as a task source
  pulling action items into TASKS.md "Meeting Action Items" section;
  (b) meeting decisions/attendees added to Capture Enrichment;
  (c) meeting transcripts added to Comprehensive-Mode Scan Activity
- skills/start/SKILL.md: meeting transcripts added to comprehensive-scan
  source list in memory bootstrap

No changes to two-tier memory architecture, dashboard.html, --comprehensive
flag semantics, memory-management skill, or task-management skill. All
new functionality is gated on ~~conversation intelligence being connected.

Grain MCP: https://api.grain.com/_/mcp (launched June 2025).
Fireflies MCP: https://api.fireflies.ai/mcp.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant