Meeting Notes

Summarize meetings from raw notes, transcripts, or bullet points into a structured, actionable format.

Language

Detect the user's preferred language from Personal Preferences. Respond entirely in that language.

If no preference is set:

AskUserQuestion: "What language should these meeting notes be in?"
Options: ["English", "עברית", "Русский"]

Workflow

Step 1: Input Type

AskUserQuestion: "What format are your meeting notes in?"
Options: [
  "Raw notes / bullet points",
  "Meeting transcript",
  "Audio summary (I'll describe what was discussed)",
  "I'll dictate the key points now"
]

Step 2: Meeting Details

Gather basic meeting metadata (ask only what's missing from the input):

AskUserQuestion: "Let me fill in the meeting details. What type of meeting was this?"
Options: ["Team standup", "Client meeting", "Planning / Strategy", "One-on-one", "All-hands", "Other"]

Collect:

• Date and time (auto-detect from context if possible)
• Attendees (names and roles)
• Meeting type/purpose

Step 3: Process and Structure

Parse the input and extract:

1. Key Topics Discussed — Major themes and discussion points
2. Decisions Made — Anything that was agreed upon or decided
3. Action Items — Tasks assigned with owner and deadline
4. Open Questions — Unresolved issues or items needing follow-up
5. Notable Quotes/Points — Important statements worth capturing (optional)

Rules for extraction:

• Action items must have an owner. If the owner is unclear, flag it: "Owner TBD — needs assignment"
• Decisions must be explicit. Don't infer decisions — only capture what was clearly agreed
• Deadlines: If mentioned, include them. If not mentioned for action items, note "No deadline set"
• Attendees not mentioned by name: List as "[Role] — name unknown"

Step 4: Present Structured Notes

Output using the format from template.md:

AskUserQuestion: "Here are the structured meeting notes. What would you like to do?"
Options: [
  "Save as-is",
  "Edit — I need to correct something",
  "Extract action items to task manager",
  "Send summary to attendees (draft email)",
  "Add to project memory"
]

Step 5: Post-Processing

If "Extract action items to task manager":

• List each action item with owner and deadline
• Offer to add them to ~/Tandem/tasks/ via the task-manager skill

If "Send summary to attendees":

• Invoke email-draft with the meeting summary formatted as an email
• Include action items as a bulleted list with owners
• Subject line: "Meeting Notes — [Meeting Title] — [Date]"

If "Add to project memory":

• Save key decisions and context to the relevant project's MEMORY.md
• Ask which project folder if multiple exist

If "Save as-is":

• Save to ~/Tandem/documents/meeting-[topic]-[date].md

Proactivity — Next Steps

After processing meeting notes, suggest 1-2:

• If action items were extracted: "Want me to add these action items to your task list?"
• If attendees are known: "Should I send the meeting summary to all attendees?"
• If decisions affect a project: "Want me to save these decisions to your [project name] memory?"
• If follow-up meeting was mentioned: "Want me to set a reminder for the follow-up meeting?"
• If this is a recurring meeting: "Want me to save this template for next time?"

Memory

Memory is user-triggered only. Offer to remember:

• Key decisions made in the meeting
• Recurring meeting participants and their roles
• Preferred meeting notes format

Output Format

Follow template.md for the structured output format.

Hebrew RTL Note

When generating Hebrew meeting notes:

• Right-to-left alignment for all text
• Action item checkboxes remain on the left: - [ ]
• Names in Hebrew script, no transliteration needed
• Date format: day/month/year

Error Handling

• Very brief input: "I have limited notes to work with. Can you add more context about what was discussed? Even a few more bullet points would help."
• No action items found: "I didn't find any clear action items. Was anything assigned during the meeting, or was this primarily informational?"
• Unclear attendees: "I couldn't identify all attendees. Can you list who was in the meeting?"

Activity Logging

After completing the workflow, append an entry to ~/Tandem/stats.json:

{
  "type": "document",
  "action": "created",
  "count": 1,
  "timeSavedMinutes": 30,
  "description": "Processed meeting notes: Team standup - 5 action items",
  "timestamp": "<current ISO 8601>"
}

If ~/Tandem/stats.json does not exist, create it as [<entry>]. If it exists, read it, parse the JSON array, append the new entry, and write it back.

Dashboard Sync

After appending to stats.json, follow the /sync workflow from tandem-skills/core/sync/SKILL.md to rebuild ~/Tandem/dashboard.html with updated statistics. This keeps the dashboard current after every skill run. If /sync fails (e.g., dashboard.html does not exist yet), continue — the main skill workflow must complete successfully regardless of sync outcome.