Meeting Notes to Actionable Records: Stakeholders, Actions, Incidents & Shots
A four-step workflow converting raw meeting notes, incident logs, and event schedules into neutral, review-ready tables. Unknowns are left blank to prevent hallucination.
Meeting Notes to Actionable Records: Stakeholders, Actions, Incidents & Shots is a hand-picked TokRepo arsenal pack — 4 AI assets bundled together so you can install the whole stack with one command. Each asset has been verified live (status=public, current download), tagged with its primary type, and curated to work alongside the others in this pack.
To install, run `tokrepo install pack/tokrepo-editorial-efficiency-02f2a1ab1994` in your terminal — or hand the same command to your AI agent (Claude Code, Cursor, Codex CLI, Gemini CLI, GitHub Copilot, Cline, Roo Code, Windsurf are all supported). The TokRepo Node CLI fetches each asset from the TokRepo registry, places skill files into `.claude/skills/`, prompts into your prompt directory, MCP servers into your client config, and surfaces a summary of what was installed.
Without a pack, you would need to discover, vet, and install each of these 4 assets one by one — typically 30 to 60 minutes per asset. The pack collapses that into a single command, and stays current as the underlying assets get re-published. If any asset goes private or is removed, the pack auto-detects it and skips that entry on next install — no broken bundle.
How to use this collection
# From Raw Notes to Verified Office Records This collection guides you through a strict progression of four reusable prompts. The goal is to turn messy, unstructured text (meeting notes, chat logs, incident reports) into structured, auditable records without inventing facts. ## Prerequisites 1. **AI Chat Tool**: Any standard LLM interface that accepts pasted text (e.g., ChatGPT, Claude). No API keys or installations required. 2. **Raw Data**: You must have the actual source material: meeting transcripts, incident logs, or event schedules. 3. **Privacy Check**: Ensure you have permission to paste this data. Redact sensitive personal or commercial information before pasting. ## The Progression **Step 1: Map Stakeholders (`50a4b899-c4cc-48fb-91a2-1cfe30aa46f5`)** *Role*: Establish a neutral baseline of who said what. *Action*: Paste meeting notes to extract named parties, their stated positions, basis, and evidence strength. *Why*: Before assigning tasks, you must know exactly who holds which view. This prevents misattribution by labeling evidence as `explicit`, `implied`, or `unclear`. **Step 2: Extract Actions (`a7cdc10d-46a7-4273-a857-651747981c9b`)** *Role*: Convert discussion into a work register. *Action*: Turn rough minutes into a Markdown table with Action, Owner, Due Date, and Status. *Constraint*: If the source does not name an owner or date, these fields remain **blank**. Tentative words like "maybe" are never upgraded to firm commitments. **Step 3: Timeline Incidents (`f0f33817-8fde-4806-a732-ab3e4fe69cd2`)** *Role*: Document non-meeting events (outages, complaints). *Action*: Order log entries strictly by provided timestamps. Conflicting times are shown side-by-side; untimed entries are grouped separately. *Output*: A factual narrative and a draft follow-up message for manual review. **Step 4: Plan Event Shots (`a909b218-97cc-4a4c-bab7-11a9106fa9aa`)** *Role*: Forward-planning for events. *Action*: Turn a schedule into a checklist of one image per moment, specifying framing and must-show elements. *Why*: Applies the same "no-invention" discipline to planning: if details are missing, the row is marked `needs more detail` rather than guessed. ## Verification & Limitations - **Traceability**: Every row in the output must trace back to a specific phrase in your input. Delete any row that cannot be traced. - **No External Actions**: These prompts do not send emails, schedule calendar events, or access external databases. They only process the text you paste. - **Human Review Required**: The outputs are drafts. You must verify that the extracted actions and timelines align with reality before sharing them. - **Fictional Examples**: All examples within the prompts are illustrative only and do not represent real test results.
4 assets in this pack
Why this asset is included:Establishes a neutral stakeholder map from meeting notes, identifying positions and evidence strength before actions are assigned, preventing misattribution.
Why this asset is included:Converts rough minutes into a structured action register, strictly leaving unknown owners/dates blank to avoid guessing.
Why this asset is included:Orders incident logs into a factual timeline by timestamp, handling conflicts and gaps without inferring causes.
Why this asset is included:Applies the no-invention discipline to event planning, creating a checkable photo shot list based strictly on supplied schedule details.
12 packs · 80+ hand-picked assets
Browse every curated bundle on the home page
Back to all packs