返回提示词目录第 1174 页

将技术讨论整理为可追溯文档

从讨论中提取最终共识与适用条件,生成技术文档、来源对照表和待解决问题清单。

完整提示词

<context>
A lot of real documentation lives in chat threads: someone asks how a thing works, three people answer, one answer gets corrected forty messages later, and the useful outcome is buried. Turning that into a page goes wrong in predictable ways. The writer copies the first confident answer instead of the corrected one, presents a suggestion nobody agreed to as the rule, keeps the chronology ("first we tried X") when readers only need the outcome, and drops the conditions ("only on the EU cluster", "until the v3 migration lands") that made the answer true. Discussions also mix stable facts with temporary workarounds; a page that does not mark which is which goes stale silently. Good conversion keeps the final, agreed state, cites where each claim came from so a reviewer can check it, and lists what was never resolved instead of smoothing it over.
</context>

<task>
<discussion>
{{discussion}}
</discussion>
{{#page_type}}Page type: {{page_type}}{{/page_type}}
{{#audience}}Audience: {{audience}}{{/audience}}

1. Read the whole discussion before writing. Mark each substantive statement as one of: settled (agreed, or stated by the person who owns the system and not challenged), corrected (later replaced, note by what), proposal (suggested, not agreed), question (asked, not answered), workaround (temporary, with its trigger to remove) or off-topic.
2. Choose the page type from what the discussion actually answers: a task with steps is a how-to, a "why does it work this way" is an explanation, a symptom and fix is a troubleshooting entry, a choice between options is a decision record. If a page type was given and the material does not fit it, say so and use the closest fit.
3. Write the page from settled and corrected-final statements only, in present tense, for the stated audience. Keep conditions and scope (environment, version, plan, region). Commands, config keys and names must appear exactly as in the source. Label workarounds as temporary.
4. Build a source map: each claim on the page linked to the message, comment or timestamp it came from.
5. List open points: proposals, unanswered questions and contradictions, each with who could settle it if the discussion makes that clear.
</task>

<constraints>
- Do not fill gaps with general knowledge presented as the team's practice. If a step is missing, leave a marked gap rather than inventing it.
- Do not name individuals in the page itself; refer to teams or roles. Personal names may appear only in the source map.
- Drop personal remarks, blame, credentials, tokens, internal hostnames and customer data that appear in the thread, and say under "Left out" that you removed sensitive content.
- If the discussion never reached an answer, do not write a page that implies one; return the open points and a short draft skeleton instead.
{{> guardrails/investigate-before-answering}}
</constraints>

<output_format>
## Page
The finished docs page in Markdown, with title and type.
## Source map
Table: claim, source message or timestamp, status (settled or corrected).
## Open points
Checklist of proposals, unanswered questions and contradictions, with who could resolve each.
## Left out
What was removed (history, off-topic, sensitive content) and why, in one line each.
</output_format>

可替换内容

  • {{discussion}}
  • {{#page_type}}
  • {{page_type}}
  • {{/page_type}}
  • {{#audience}}
  • {{audience}}
  • {{/audience}}
  • {{> guardrails/investigate-before-answering}}

分类与标签

编程开发、技术文档、讨论整理、来源追溯、知识沉淀

前往 AI 图片创作