pmstudio-meeting-notes

To turn unstructured meeting transcripts into structured notes, paste the transcript text or supply a file path to extract actions, decisions, attendees, and open questions with direct speaker attribution. The output is organized with frontmatter metadata and routed to the correct project subfolder.

Extract action items and decisions from a raw transcript by processing it to identify key outcomes, open questions, and direct quotes with speaker attribution. The system enforces frontmatter metadata to ensure each extracted item is properly structured for project tracking.

You can resolve meeting attendee names and roles by routing the transcript through a stakeholder directory. This enriches the attendee list with accurate names, roles, and groups, ensuring that the structured meeting notes have correct speaker attribution.

This approach does cross-reference meeting notes with existing PRD files and recent notes. It surfaces relevant project context, identifies updates, and flags artifact impacts to ensure that newly generated notes align with the current product requirements.

The best way to route meeting notes to the correct project subfolder is by cross-referencing CLAUDE.local.md and project context. This routing mechanism ensures that the generated output file is automatically organized and delivered to the appropriate location.

Meeting notes output requires frontmatter metadata to enforce consistent structure across all project documentation. This standardized format enables reliable parsing, ensures artifact impacts are properly flagged, and maintains alignment when cross-referencing PRD files and recent notes.