Update to AI Board Lite

{
  "description": "Turns notes, figures and project status into a short update for a board, investors, a team or a client: headline first, a status per topic with a clear on track / at risk / off track label, the numbers that moved, what is needed from the reader, and nothing else. Use for \"write the monthly update\", \"draft an investor update\", \"schrijf de maandupdate\", \"maak een update voor de RvC\".",
  "included_files": [],
  "name": "stakeholder-update",
  "skill_md_contents": "---\nname: stakeholder-update\ndescription: Turns notes, figures and project status into a short update for a board, investors, a team or a client: headline first, a status per topic with a clear on track / at risk / off track label, the numbers that moved, what is needed from the reader, and nothing else. Use for \"write the monthly update\", \"draft an investor update\", \"schrijf de maandupdate\", \"maak een update voor de RvC\".\n---\n\n# Stakeholder Update\n\nReaders of an update want three things: is it going well, what changed, and\ndo they need to do something. Everything else is noise. So the update opens\nwith the answer, labels every topic honestly, and puts the ask where it\ncannot be missed.\n\n## Ground rules\n\n- Use only the notes, figures and status the user provides. Every number keeps\n  its source and its period.\n- A topic is \"on track\", \"at risk\" or \"off track\". Pick the honest one; if the\n  material does not say, ask instead of choosing the comfortable label.\n- Bad news goes in the update, early and plainly, with what is being done\n  about it.\n- Answer in the language the user writes in, and write the update in the\n  language of its readers if the user names them.\n  The example below is in English; translate its headings too.\n\n## When to use\n\nThe user has to report to someone and shares notes, numbers or a previous\nupdate: \"write the monthly update\", \"draft the investor update\", \"update for\nthe board\", \"schrijf de maandupdate\", \"maak een update voor de RvC\", \"zet dit\nom in een update voor het team\".\n\n## Steps\n\n1. **Pin down the reader and the period.** A board, investors, a team and a\n   client each need a different level of detail. Ask once if unclear.\n2. **If there is a previous update**, compare against it: what was promised\n   then, and did it happen?\n3. **Write the headline**: one or two sentences on how the period went.\n4. **Write each topic** in two or three lines with its status label, the\n   number that moved (with period and source) and what happens next.\n5. **Write the ask**: what the reader needs to decide, provide or know, with a\n   date. If there is no ask, say \"No action needed\".\n6. **Keep it short.** Aim for something readable in two minutes. Offer a\n   longer appendix only if the user wants one.\n7. **Offer to keep it for next time.** If this environment can write files,\n   offer to save the update as `Updates/<YYYY-MM> · <reader>.md`. Next month,\n   that file is the \"previous update\" from step 2, so promises get checked\n   instead of forgotten. Do not write anything without the user saying yes.\n\n## Output format\n\n```markdown\n**Update August · AI pilot**\n\n**Headline:** The pilot is approved and staffed; data access is the one open\nrisk before go-live in October.\n\n| Topic | Status | What moved | Next |\n|---|---|---|---|\n| Pilot scope | On track | Service confirmed as pilot department (MT, 3 Aug) | Kick-off 1 Sep |\n| Budget | On track | Frame of €48k agreed (Finance, 14 Aug) | First invoice Sep |\n| Data access | At risk | Still no owner, raised twice | Owner needed by 15 Sep |\n\n**Ask:** name an owner for data access before 15 September.\n\n**Promised last month:** choose the pilot department. Done.\n```\n\n## Limits\n\n- The update reports what the material says. Progress that is not in the\n  notes is not claimed.\n- It drafts. The user reviews and sends it; nothing is sent from here.\n"
}