meeting-postbrief
Write a Meeting Postbrief, a one-page findings sheet sent after a technical meeting - the shared vocabulary the discussion needed, what was proposed and what it will and will not deliver against the real need, and concrete ways forward with named techniques and workday estimates. Use whenever someone asks for "a postbrief", "a findings sheet", "a cheat sheet from the meeting", "my notes with ways forward", "something to send the team after the call", or wants to turn a meeting (transcript, chat, slides, live notes) into a decision-ready one-pager for attendees; also offer one after any technical meeting where people talked past each other on terms, a plan was presented, or options were left open. Not for minutes or a full meeting summary (relevant-transcripts conventions) or a pre-meeting brief.
Target: Presentations. Automatically collected · unverified.
Excerpt from the author’s documentation
Extracted from a fixed version of SKILL.md in its original language. This is the author’s documentation; installation, compatibility and runtime results have not been verified by this site.
Read the original English text
Topics in the source
- Meeting Postbrief
- Inputs, gather all of them first
- The three sections, always in this order
- Style
- Build and deliver
A Meeting Postbrief is the one page you send attendees after a technical meeting. Minutes record what was said; a postbrief records what it means and what we could do next. Write one when people are using terms interchangeably, a plan is being taken as the answer to a different question, or a lead needs to decide where to spend. An illustrative example, with its rendered page, is references/example-postbrief.md and assets/example-postbrief.pdf. It earns its place when the meeting had at least one of: words used loosely, a plan presented, a decision left open. If it had none, send a summary instead. The raw transcript (Teams/Plaud) and its summary, if one exists. The meeting chat (links, papers, code and data people pasted are often the real content). Slides or screenshots shown, and any live notes taken during the call. The project's own record: what the program actually needs (requirements, success criteria, the larger system this piece sits in). The postbrief judges the plan against that, not against what the presenter said it was for. Quote people only with words the transcript shows. Mark anything from your own knowledge (figures, product accuracies, method claims) as unverifie
This is an excerpt. Refer to the complete source and its current requirements.
- Source repository
- Lmandrake/MandrakeWorkflows
- Source file
- skills/meeting-postbrief/SKILL.md
- Fixed revision
- 1874105936272447e2f9c81ba1dac48dae6ed074
Sources and evidence
This record was collected automatically. Its documentation, suitability and runtime behavior have not been manually verified.
Author: Lmandrake/MandrakeWorkflows · original repository metadata. Documentation review: Not reviewed. Last source check: 2026-11-11T03:01:44.687Z.
Categories are inferred from names, descriptions and paths. They do not establish compatibility.
License and attribution
MIT. Third-party content and copyright remain with their authors. Refer to the original license and terms.
Original license ↗Synchronization, copying and user-reported success do not mark a resource as runtime-tested.
Limitations and notes
- Collecting metadata does not mean this site has installed, adapted, runtime-tested or security-reviewed the resource.