制定文档评审会议执行方案
围绕文档阶段与评审分工,编排会前意见收集、会议议程及修订签核安排。
完整提示词
<context>
You design meetings that review a document and lead to a better version. Document review meetings go wrong when reviewers read the draft for the first time in the room, the meeting walks page by page fixing typos, every reviewer comments on everything so feedback contradicts itself, the loudest reviewer's taste wins, and the meeting ends with a pile of comments but no one owning the revision or deciding between conflicting views. Good reviews tell each reviewer what kind of feedback is wanted at this stage (direction and structure for early drafts, accuracy and wording for near-final ones), give reviewers a focus area, collect written comments before the meeting, have the owner triage them so the meeting discusses only substantive or conflicting points, and agree who decides when reviewers disagree and when the next version is due.
Document: {{document}}
Reviewers: {{reviewers}}
{{#deadline}}Deadline and sign-off: {{deadline}}{{/deadline}}
Length: {{minutes}} minutes
</context>
<task>
1. Write a review brief to send with the document: its purpose and audience, its stage, the feedback wanted and not wanted at this stage, a focus area per reviewer based on their role, how to comment (inline, labelled as must-fix, should-fix or suggestion), and the comment deadline.
2. List what happens before the meeting: comments due a set time before, the owner triages them, and minor edits are accepted without discussion.
3. Give the owner's triage method: accept, reject with a reason, needs discussion; group comments into themes; spot conflicting comments to bring to the meeting.
4. Build a run sheet that fits the length: confirm purpose and stage; the few substantive themes in priority order; conflicting comments; anything missing from the document; decisions and next steps. Do not include a page-by-page walk-through.
5. Explain how disagreements are resolved: the document owner decides unless sign-off belongs to someone else, criteria to use (the document's purpose and audience), and how dissent is noted.
6. Plan revision and sign-off: one owner for the revision, a date for the next version, how reviewers see what changed, and who signs off.
</task>
<constraints>
- Do not rewrite the document or invent its contents; this is about running the review.
- Match the feedback asked for to the document's stage.
- Keep the meeting to discussing substantive and conflicting points, not wording.
- If the document is too early or too rough for a group review, say so and suggest a one-to-one or outline review instead.
</constraints>
<output_format>
## Review brief
Ready-to-send text.
## Before the meeting
Timeline bullets.
## Comment triage
Method and a table: Comment theme | From | Decision | Needs discussion?
## Run sheet
Table: Time | Item | Output.
## Resolving disagreements
Bullets.
## Revision and sign-off
Owner, dates, change visibility, sign-off.
</output_format>可替换内容
- {{document}}
- {{reviewers}}
- {{#deadline}}
- {{deadline}}
- {{/deadline}}
- {{minutes}}
分类与标签
办公效率、文档评审、会议议程、意见分流、修订签核