企业官网建设流程全解析

Brief: {Meeting Title}

【免费下载链接】rowboatOpen-source AI coworker, with memory项目地址: https://gitcode.com/GitHub_Trending/rowb/rowboat

{Day}, {Time} · [[{Attendee Name}]] ({Company/Role})

About {Attendee First Name}

{Summary from their People note - role, background, key facts} {What they care about, their focus areas}

Your History

{Chronological list of previous interactions from meeting notes} • {Date}: {Brief description of interaction/outcome} • {Date}: {Brief description} • {Date}: {Brief description}

Open Items

{Action items related to this person or their organization} • {Item description} (mentioned {date}) • {Item description}

Suggested Talking Points

{Context-aware suggestions based on:} • {Recent developments they should know about} • {Follow-ups from previous conversations} • {Relevant project updates - reference [[Project Name]] if applicable} • {Questions to ask or topics to cover}

Event ID:{event_id}Prepared:{current_timestamp}

配套的**简报撰写准则**（务必逐条落实）： - 使用 `[[Name]]` wiki-link 语法交叉引用笔记； - “About” 部分保持精炼，最多 2～3 句； - History 按时间倒序（最新的在最前），最多保留 3～5 条最相关的互动； - Open Items 必须具体、可执行； - Talking Points 要具体而非泛泛而谈； - 若某人没有任何笔记，明确标注这一点，并建议创建一条人员笔记。 ### Step 6：更新状态 每处理完一场会议： 1. 把事件 ID 加入 `prepared` 列表； 2. 将 `lastProcessedTimestamp` 更新为该会议的开始时间； 3. 写回 `pre-built/meeting-prep/state.json`。 “每场会议后立即保存状态”是文档强调的容错关键：一旦中途失败，重跑时只需从断点继续，不会重复处理已完成的会议。 ## 六、处理完成后的输出摘要 处理完所有即将到来的会议后，Agent 需要向用户输出如下格式的摘要：

Meeting Prep Summary

Meetings Processed:XBriefs Created:Y

Briefs Created:

• {meeting_title} with {attendee} at {time} → pre-built/meeting-prep/briefs/{event_id}_brief.md

Skipped:

• {event_title}: {reason - e.g., "DND block", "no external attendees"}

【免费下载链接】rowboatOpen-source AI coworker, with memory项目地址: https://gitcode.com/GitHub_Trending/rowb/rowboat