设计静默阅读式会议流程
根据会议目的、参会者和时长,制定先阅读评论后讨论的文档结构、时间表与收尾机制。
完整提示词
<context>
You design silent, read-first meetings: the first part of the meeting is spent reading a written document together and commenting in it, and only then does the group talk. The approach guarantees everyone has actually read the material, lets quieter and non-native speakers contribute in writing, and surfaces many more questions in parallel than open discussion can. It fails when the document is a slide deck in prose, when it is too long to read in the reading time, when comments become a debate thread nobody resolves, or when the discussion afterwards ignores the comments. Experienced hosts budget reading speed (roughly 200-250 words a minute for careful reading of dense material), ask commenters to label comments by type, and spend the talking time only on the comments that need a conversation.
Purpose: {{purpose}}
Attendees: {{attendees}}
Length: {{minutes}} minutes
{{#memo}}
<memo>
{{memo}}
</memo>
{{/memo}}
</context>
<task>
1. Check fit: say whether a silent meeting suits this purpose and group, and name the main risk.
2. Propose a document structure for the purpose (for example: decision needed, context, options and trade-offs, recommendation, risks, questions for readers). If a memo is supplied, review it against that structure and list gaps; estimate its reading time and say whether to cut it.
3. Set comment rules: one point per comment; label comments (question, concern, suggestion, agree, blocker); reply in thread rather than starting duplicates; name instead of "+1" when agreeing matters for a decision.
4. Build a run sheet that fits the minutes: short framing, reading and commenting time based on the document's length, a few minutes for the author to triage comments into themes, discussion of the blockers and open questions first, decision or next steps, and a close.
5. Give the author's triage method: sort comments into resolve now, take offline, accept without discussion, and say how to show that in the doc.
6. Explain how to close: record the outcome in the doc itself, answer or assign every unresolved comment, and share the final version.
7. Note adjustments for remote and mixed attendance (everyone in the same doc, cameras optional during reading, one person watches comment flow).
</task>
<constraints>
- Do not write the memo's content from scratch with facts you do not have; if no memo is given, give the structure with prompts for each section.
- Reading time must be realistic for the length; if the memo cannot be read in the time, say what to cut.
- The discussion part must be driven by the comments, not by re-presenting the memo.
- Keep it practical: no claims about specific companies' practices.
</constraints>
<output_format>
## Fit check
Two or three lines.
## The document
Structure, or gaps in the supplied memo, plus estimated reading time.
## Comment rules
Bullets to paste at the top of the doc.
## Run sheet
Table: Time | Segment | Who | What happens.
## Closing and follow-up
Bullets.
</output_format>可替换内容
- {{purpose}}
- {{attendees}}
- {{minutes}}
- {{#memo}}
- {{memo}}
- {{/memo}}
分类与标签
办公效率、会议管理、团队协作、会议流程