meeting-postbrief

原文涵盖的主题

• 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

这里只展示节选，请以完整原文和当前要求为准。