Update to AI Board Lite

{
  "description": "Builds a delta brief for an upcoming meeting from the notes, emails and documents the user provides. Reconstructs what was agreed last time, what changed since, who owes what, and three talking points, each line with its source. Use when the user asks \"prep me for X\", \"where did we leave X last time\", \"bereid me voor op X\".",
  "included_files": [],
  "name": "meeting-prep",
  "skill_md_contents": "---\nname: meeting-prep\ndescription: Builds a delta brief for an upcoming meeting from the notes, emails and documents the user provides. Reconstructs what was agreed last time, what changed since, who owes what, and three talking points, each line with its source. Use when the user asks \"prep me for X\", \"where did we leave X last time\", \"bereid me voor op X\".\n---\n\n# Meeting Prep\n\nThe real question is never \"what is this meeting about\". It is \"what did we\nagree last time, and what quietly changed since\". This is a delta brief, not a\nsummary. Two ways to get it wrong: padding it with context the user already\nhas, and stating a prior agreement you cannot point to a source for.\n\n## Ground rules\n\n- Work only from what the user provides in this conversation: previous meeting\n  notes, transcripts, email threads, decks, documents. Nothing else counts as a\n  source.\n- Every claim about \"last time\" cites the document it came from. No source, no\n  line.\n- Silence means \"not recorded\", not \"nothing happened\". Say which one it is.\n- Answer in the language the user writes in.\n  The example below is in English; translate its headings too.\n\n## When to use\n\nThe user has a meeting coming up and asks \"prep me for the board call\", \"where\ndid we leave X last time\", \"what do I need to know before Thursday\", \"bereid me\nvoor op X\", \"hoe stond het er vorige keer voor\".\n\n## Steps\n\n1. **Pin down the meeting:** topic, who is in the room, when. Ask for whatever\n   is unclear. Guessed attendees produce a wrong brief.\n2. **Gather the material.** If the user keeps meeting notes in a folder (for\n   example a `Meetings/` folder saved in earlier sessions) and this\n   environment can read it, ask to search it on the topic and the people.\n   Otherwise ask the user for the notes or transcript of the previous meeting,\n   plus anything since: email threads, updated decks, status reports. If they have nothing on record, say so in the first line of the\n   brief and work from what they can tell you.\n3. **Reconstruct \"last time\":** decisions taken, commitments made, who owed\n   what. Cite the source for each line.\n4. **Work out the delta:** commitments that were met, missed or never started,\n   numbers that moved, new documents or facts touching the topic. Compare dates\n   against today to show how long each open item has been open.\n5. **List open items by owner**, with the promised date and how overdue each\n   one is.\n6. **Write three talking points.** A talking point is a position with a reason,\n   not a topic.\n7. **Offer to keep it for next time.** If this environment can write files,\n   offer to save the brief as `Meetings/<YYYY-MM-DD> · <topic> prep.md`, with\n   headings that can take the real minutes afterwards, so the next prep starts\n   from it. Do not write anything without the user saying yes.\n\n## Output format\n\n```markdown\n# 2026-08-03 · AI strategy (prep)\n\n**Last time:** 2026-06-14, same group. Source: notes from 14 June.\n\n## Agreed then\n- Pilot in one department first, broad rollout after. *(decision, notes 14 June)*\n- Budget parked until the pilot shows numbers. *(open, no owner recorded)*\n\n## Changed since\n- The pilot never started: no mention in any email since, 7 weeks gone.\n- New: the Q3 budget deck sets a precedent for pilot spend. *(budget deck, slide 6)*\n\n## Who owes what\n| Item | Owner | Promised | Status |\n|---|---|---|---|\n| Choose the pilot department | You | 2026-06-14 | 50 days open |\n| Budget frame | Finance | no date | never assigned |\n\n## 3 talking points\n1. The pilot is the decision. Seven weeks without choosing cost a quarter.\n2. Don't reopen scope: that is how June ended without an owner.\n3. Leave with a name and a date, or the next meeting is this meeting.\n```\n\n## Limits\n\n- The brief is only as good as the material provided. It does not search mail,\n  calendars or drives on its own unless the user has connected them in this\n  environment and asks for it.\n- A prior meeting exists only if it was written down. An empty result is\n  reported as \"not recorded\", never as \"nothing happened\".\n- This skill prepares. It does not send agendas or invites.\n"
}