返回提示词目录第 1443 页

审查文档歧义并提出清晰改写

逐项找出可能导致不同理解的表述,说明各自后果与严重程度,并给出贴近原文的修改建议。

完整提示词

<context>
Ambiguity is cheap to fix on the page and expensive to discover later, in a dispute, a wrong build or an inconsistent decision. Authors cannot see their own ambiguities because they know what they meant. A useful review reads as the least charitable competent reader would, finds statements with two or more plausible readings, shows the readings side by side with what each would lead someone to do, and offers wording that allows only the intended one.

Common sources of ambiguity to check:
- **Lexical:** a word with two meanings ("bi-weekly", "sanction", "next Friday"), or an undefined term.
- **Inconsistent terms:** the same thing called two names, or one name used for two things.
- **Scope and attachment:** what a modifier or condition applies to ("employees and contractors with a laptop"); "and" versus "or"; "and/or".
- **Quantifiers and negation:** "all … not", "up to", "at least", "a few", "regularly".
- **Time:** "within 30 days" (calendar or business, from when), "by Friday" (inclusive, which time zone), "annually".
- **Reference:** "it", "they", "this", "the above", "the manager" when several are in play.
- **Modal strength:** "should", "may", "will", "must" used interchangeably for obligations.
- **Missing actor:** passive voice that hides who must act ("requests will be approved").
- **Vague standards:** "reasonable", "promptly", "where possible", "appropriate" with no test.
- **Conditions and exceptions:** nested if, unless, except, and which takes precedence when two rules conflict.
</context>

<task>
Review the document below for ambiguity.{{#document_type}} Document type: {{document_type}}.{{/document_type}}{{#reader}} The reader who must act on it: {{reader}}.{{/reader}}

<document>
{{document}}
</document>

1. If the document is empty, ask for it and stop. If no reader is given, assume a competent reader who was not involved in writing it and say so in the Summary.
2. Read the whole document once for purpose. Then go statement by statement looking for the sources listed above.
3. For each ambiguity, record: the location (section or a few quoted words), the exact quoted text, the type, reading A and reading B (and C if needed), the practical consequence of the difference for the reader, a severity, and proposed wording.
   - **High:** readers would act differently in ways that cost money, safety, rights, deadlines or a failed delivery.
   - **Medium:** likely to cause questions, delays or inconsistent handling.
   - **Low:** unlikely to mislead in practice but worth tightening.
4. Proposed wording must allow only the intended reading. If you cannot tell which reading the author intended, give wording for each and ask.
5. List terms that should be defined once and used consistently, with a suggested definition where the document implies one, or a question where it does not.
6. Do not flag ordinary style issues, typos or wordiness unless they create ambiguity.
</task>

<constraints>
- Quote the document exactly; never paraphrase it in the "text" column.
- Report only genuine ambiguities with two plausible readings, not far-fetched ones. Fewer, real findings beat a long list.
- Keep proposed wording as close to the original as possible and in the document's register.
- If the document is a contract or other legal text, note once that this is a drafting clarity review, not legal advice, and that changes to binding terms should be checked by someone qualified.
</constraints>

<output_format>
## Summary
Two or three sentences: how many ambiguities by severity, the most consequential one, and the assumed reader.
## Ambiguities
Table: # · Location · Text · Type · Reading A · Reading B · Consequence · Severity · Proposed wording. Ordered by severity, then position.
## Terms to define
Table: Term · Where used · Problem · Suggested definition or question.
## Notes
Bullets: patterns across the document (for example "uses 'should' for both rules and advice") and any author questions. "None" if none.
</output_format>

<examples>
Text: "Expenses must be submitted within 30 days with receipts over 25 EUR."
Reading A: submit all expenses within 30 days; attach receipts only for items over 25 EUR.
Reading B: the 30-day rule applies only to expenses over 25 EUR, which need receipts.
Proposed: "Submit every expense within 30 calendar days of the purchase date. Attach a receipt for any item over 25 EUR."
</examples>

可替换内容

  • {{#document_type}}
  • {{document_type}}
  • {{/document_type}}
  • {{#reader}}
  • {{reader}}
  • {{/reader}}
  • {{document}}

分类与标签

办公效率、文档审校、歧义检查、文本改写

前往 AI 图片创作