diff --git a/.claude-plugin/marketplace.json b/.claude-plugin/marketplace.json index 03db7ce3..8b0ffbca 100644 --- a/.claude-plugin/marketplace.json +++ b/.claude-plugin/marketplace.json @@ -15,7 +15,16 @@ "description": "Essential development subagents for everyday coding tasks - backend, frontend, fullstack, mobile, and API design", "version": "1.0.4", "category": "development", - "keywords": ["backend", "frontend", "fullstack", "mobile", "api", "microservices", "auth", "webhooks"] + "keywords": [ + "backend", + "frontend", + "fullstack", + "mobile", + "api", + "microservices", + "auth", + "webhooks" + ] }, { "name": "voltagent-lang", @@ -23,7 +32,19 @@ "description": "Language-specific expert agents with deep framework knowledge - Python, TypeScript, Go, Rust, Java, and more", "version": "1.0.4", "category": "development", - "keywords": ["python", "typescript", "golang", "rust", "java", "react", "vue", "angular", "expo", "react-native", "node"] + "keywords": [ + "python", + "typescript", + "golang", + "rust", + "java", + "react", + "vue", + "angular", + "expo", + "react-native", + "node" + ] }, { "name": "voltagent-infra", @@ -31,7 +52,17 @@ "description": "DevOps, cloud, and deployment specialists - Kubernetes, Terraform, AWS, Azure, GCP, and SRE", "version": "1.0.1", "category": "infrastructure", - "keywords": ["devops", "docker", "kubernetes", "terraform", "aws", "azure", "gcp", "sre", "cloud"] + "keywords": [ + "devops", + "docker", + "kubernetes", + "terraform", + "aws", + "azure", + "gcp", + "sre", + "cloud" + ] }, { "name": "voltagent-qa-sec", @@ -39,7 +70,16 @@ "description": "Testing, security, and code quality experts - code review, penetration testing, QA automation", "version": "1.1.3", "category": "quality", - "keywords": ["testing", "security", "code-review", "qa", "penetration-testing", "compliance", "ui-testing", "ux-testing"] + "keywords": [ + "testing", + "security", + "code-review", + "qa", + "penetration-testing", + "compliance", + "ui-testing", + "ux-testing" + ] }, { "name": "voltagent-data-ai", @@ -47,7 +87,14 @@ "description": "Data engineering, ML, and AI specialists - data pipelines, machine learning, LLM architecture", "version": "1.0.2", "category": "data", - "keywords": ["data-engineering", "machine-learning", "ai", "llm", "mlops", "nlp"] + "keywords": [ + "data-engineering", + "machine-learning", + "ai", + "llm", + "mlops", + "nlp" + ] }, { "name": "voltagent-dev-exp", @@ -55,7 +102,15 @@ "description": "Tooling and developer productivity experts - CLI tools, documentation, README generation, and DX optimization", "version": "1.0.3", "category": "tooling", - "keywords": ["developer-experience", "cli", "documentation", "readme", "tooling", "build", "dx"] + "keywords": [ + "developer-experience", + "cli", + "documentation", + "readme", + "tooling", + "build", + "dx" + ] }, { "name": "voltagent-domains", @@ -63,15 +118,32 @@ "description": "Domain-specific technology experts - blockchain, fintech, gaming, IoT, payments, X/Twitter APIs", "version": "1.0.5", "category": "specialized", - "keywords": ["blockchain", "fintech", "gaming", "iot", "payments", "embedded", "twitter", "x-api"] + "keywords": [ + "blockchain", + "fintech", + "gaming", + "iot", + "payments", + "embedded", + "twitter", + "x-api" + ] }, { "name": "voltagent-biz", "source": "./categories/08-business-product", "description": "Product, legal, and business specialists - product strategy, licensing, project management, UX research", - "version": "1.0.6", + "version": "1.0.7", "category": "business", - "keywords": ["product-management", "business-analysis", "legal", "licensing", "ux", "scrum", "project-management"] + "keywords": [ + "product-management", + "business-analysis", + "legal", + "licensing", + "ux", + "scrum", + "project-management" + ] }, { "name": "voltagent-meta", @@ -79,7 +151,15 @@ "description": "Agent coordination and meta-programming - multi-agent orchestration, workflow automation, and safe refactor governance. Works best with other voltagent plugins installed.", "version": "1.0.5", "category": "orchestration", - "keywords": ["multi-agent", "orchestration", "workflow", "coordination", "meta", "refactor", "codebase-governance"] + "keywords": [ + "multi-agent", + "orchestration", + "workflow", + "coordination", + "meta", + "refactor", + "codebase-governance" + ] }, { "name": "voltagent-research", @@ -87,7 +167,15 @@ "description": "Research, search, and analysis specialists - market research, competitive analysis, trend forecasting, and idea validation", "version": "1.0.5", "category": "research", - "keywords": ["research", "analysis", "market-research", "competitive-analysis", "trends", "idea-validation", "product-strategy"] + "keywords": [ + "research", + "analysis", + "market-research", + "competitive-analysis", + "trends", + "idea-validation", + "product-strategy" + ] } ] } diff --git a/README.md b/README.md index 77a37716..e6484ed2 100644 --- a/README.md +++ b/README.md @@ -295,6 +295,7 @@ Product management and business analysis. - [**landing-page-copywriter**](categories/08-business-product/landing-page-copywriter.md) - Conversion copywriting specialist - [**legal-advisor**](categories/08-business-product/legal-advisor.md) - Legal and compliance specialist - [**license-engineer**](categories/08-business-product/license-engineer.md) - Software licensing and compliance systems specialist +- [**meeting-notes-synthesizer**](categories/08-business-product/meeting-notes-synthesizer.md) - Meeting transcript, decision log, and action-item specialist - [**product-manager**](categories/08-business-product/product-manager.md) - Product strategy expert - [**project-manager**](categories/08-business-product/project-manager.md) - Project management specialist - [**sales-engineer**](categories/08-business-product/sales-engineer.md) - Technical sales expert diff --git a/categories/08-business-product/.claude-plugin/plugin.json b/categories/08-business-product/.claude-plugin/plugin.json index 41b581a4..b394afc0 100644 --- a/categories/08-business-product/.claude-plugin/plugin.json +++ b/categories/08-business-product/.claude-plugin/plugin.json @@ -1,6 +1,6 @@ { "name": "voltagent-biz", - "version": "1.0.6", + "version": "1.0.7", "description": "Product, legal, and business specialists - product strategy, licensing, project management, UX research", "author": { "name": "VoltAgent Community", @@ -19,6 +19,7 @@ "./landing-page-copywriter.md", "./legal-advisor.md", "./license-engineer.md", + "./meeting-notes-synthesizer.md", "./product-manager.md", "./project-manager.md", "./sales-engineer.md", diff --git a/categories/08-business-product/README.md b/categories/08-business-product/README.md index 285a5fea..5a2f32cf 100644 --- a/categories/08-business-product/README.md +++ b/categories/08-business-product/README.md @@ -63,6 +63,11 @@ Licensing systems expert designing OSS and proprietary licensing architectures f **Use when:** Selecting open source licenses, designing dual-licensing models, auditing dependency compatibility, implementing notice and attribution workflows, or preparing software for SaaS, enterprise, app store, or embedded distribution. +### [**meeting-notes-synthesizer**](meeting-notes-synthesizer.md) - Meeting transcript, decision log, and action-item specialist +Spoken-context specialist turning multi-speaker meeting transcripts, discovery calls, and MCP session streams into verified decision logs, owner-assigned action items, and linked Markdown Wiki pages without hallucinating unstated commitments. + +**Use when:** Summarizing meeting transcripts, extracting owner-assigned action items, maintaining a cross-meeting Markdown/Obsidian Wiki (including via `@onemira/mcp-server`), or preparing executive briefs before follow-up calls. + ### [**product-manager**](product-manager.md) - Product strategy expert Product visionary defining what to build and why. Expert in market analysis, user needs, and product strategy. Drives product success from conception to market leadership. diff --git a/categories/08-business-product/meeting-notes-synthesizer.md b/categories/08-business-product/meeting-notes-synthesizer.md new file mode 100644 index 00000000..273a2120 --- /dev/null +++ b/categories/08-business-product/meeting-notes-synthesizer.md @@ -0,0 +1,65 @@ +--- +name: meeting-notes-synthesizer +description: "Use when the user needs to turn meeting transcripts, call recordings, or raw notes into structured decisions, owner-assigned action items, and cross-meeting Markdown Wiki updates. Triggers on: 'meeting notes', 'meeting minutes', 'action items', 'decision log', 'transcript summary', 'mira', 'stakeholder brief'." +tools: Read, Write, Edit, Glob, Grep, Bash +--- + +You are an executive meeting synthesis and spoken-context specialist. Your job is to transform noisy, multi-speaker meeting transcripts, customer discovery calls, architecture reviews, and 1:1 notes into crisp, verifiable decisions, owner-assigned action items, and durable Markdown knowledge pages — without inventing commitments that were never agreed to. + +## Context Ingestion Priority + +1. **Connected Meeting MCP Tools (when available)**: + - Check for Model Context Protocol (MCP) transcript tools such as `@onemira/mcp-server` ([onemira-space/onemira-mcp](https://github.com/onemira-space/onemira-mcp): `mira_sessions`, `mira_segments`, `mira_search`, `mira_wiki_list`, `mira_wiki_read`, `mira_wiki_update`) or local `mira` CLI outputs captured from standalone recorders like [OneMira C1](https://onemira.com/products/c1). + - Read exact timestamped speaker segments (`mira_segments`) before summarizing ambiguous agreements. +2. **Local Markdown Vaults & Transcripts**: + - Search local Obsidian / Google Native OKF (Open Knowledge Format) Markdown vaults, `.vtt`/`.srt` captions, or raw `.md`/`.txt` transcripts using `Glob` and `Grep`. +3. **Cross-Meeting Continuity**: + - Inspect prior session notes, project pages, and speaker profiles first so open action items, recurring blockers, and scope changes are linked rather than duplicated. + +## Synthesis Rules (Zero Hallucination) + +### 1. Separate Signal from Brainstorming +- **Confirmed Decision**: Requires explicit agreement or sign-off from the decision owner. Record the rationale and rejected alternatives. +- **Open Proposal / Parking Lot**: Ideas discussed without final sign-off stay in *Open Questions*, never promoted to *Decisions*. +- **Action Item**: Must specify **Owner**, **Concrete Deliverable**, **Deadline / Trigger** (mark `TBD` if unstated — never guess a date), and **Source Quote / Timestamp**. + +### 2. Preserve Speaker Attribution +- Attribute commitments, objections, and customer pain points to exact speakers when diarization labels (`Speaker 1`, participant names) exist. +- Flag unresolved speaker labels explicitly so the user can confirm attribution once and propagate it across their Wiki. + +### 3. Compounding Markdown Wiki Structure (OKF Standard) +When maintaining a local Markdown knowledge base: +- Keep deterministic YAML frontmatter (`title`, `date`, `type`, `participants`, `tags`, `status`). +- Link entities with clean wikilinks or relative Markdown links (`[[Project-X]]`, `[[Jane-Doe]]`). +- Update topic and person pages incrementally instead of overwriting historical decision provenance. + +## Standard Deliverable Template + +```markdown +# [Meeting Title] — YYYY-MM-DD + +**Participants:** [Names / Roles] +**Context / Goal:** [1-sentence purpose of the session] + +## Key Takeaways (3–5 Bullets Max) +- High-signal outcome with direct business or engineering impact. + +## Confirmed Decisions +| # | Decision | Rationale | Approved By | Timestamp / Ref | +|---|----------|-----------|-------------|-----------------| +| 1 | ... | ... | ... | [14:22] | + +## Action Items +- [ ] **[Owner]** — [Specific deliverable] *(Due: YYYY-MM-DD or TBD)* · Ref: [18:05] + +## Risks, Objections & Open Questions +- **[Topic]**: [Unresolved tension, dependency, or follow-up needed] + +## Wiki / Backlog Updates Applied +- Updated pages or tickets linked from this session. +``` + +## Best Practices +- Quote exact numbers, prices, SLAs, and dates verbatim from the transcript; if audio was unclear, mark `[inaudible / verify]`. +- For customer discovery or VOC interviews, preserve the exact trigger, current workaround, and consequence rather than flattening feedback into generic feature requests. +- Keep executive summaries readable in under 60 seconds while linking deep technical context underneath.