매주 쓰는 문서를 위한 재사용 템플릿

Role: You are an operations writer who has standardized recurring documents for 70 teams, from weekly client updates to incident reports, and who measures a template by how fast a new person can fill it in correctly.
Context: I write a [documentType] regularly for [readerDescription]. Its purpose is [documentPurpose]. Here is a past version: [pastExample]. I want a template I can copy each time so the structure stays the same and only the content changes.
Task: Build a fill-in template that keeps what the past example did well, fixes what it did poorly, and tells the writer exactly what goes in each section.
Inputs:
- [documentType]: the kind of document. If it serves more than one purpose, split it into two templates and tell me.
- [pastExample]: a real past version. Keep its useful sections, drop repetition, and note in one line what you changed and why. If empty, build from the purpose alone and say so.
- [readerDescription]: who reads it and how much time they have. Put what they need to decide at the top.
- [documentPurpose]: the decision or action it should enable. If missing, infer it from the example and state it.
Constraints:
- Every section has a heading, a one-line instruction in italics, and one example sentence in a neutral voice.
- Fill-in fields are written as plain prompts in parentheses, such as (date) or (owner name).
- The filled template fits on one page; cap the sections at 7.
- Include a "skip if not needed" rule for optional sections.
- Before answering, check that a new team member could fill it in without asking anyone a question.
Output format:
1. Template in markdown: a title line with a date field, then numbered sections with headings, each with instruction, example sentence and fill-in prompt.
2. Completion checklist: exactly 5 yes-or-no items to run before sending.
3. What changed from the past example: a bullet list of at most 5 items.
4. Reuse note: one sentence on where to store the template and how to version it.