3. Pull Context from Connected Tools

If ~~project tracker is connected:

• Pull status of roadmap items and milestones
• Identify completed items since last update
• Surface items that are at risk or blocked
• Pull sprint or iteration progress

If ~~chat is connected:

• Search for relevant team discussions and decisions
• Find blockers or issues raised in channels
• Identify key decisions made asynchronously

If ~~meeting transcription is connected:

• Pull recent meeting notes and discussion summaries
• Find decisions and action items from relevant meetings

If ~~knowledge base is connected:

• Search for recent meeting notes
• Find decision documents or design reviews

If no tools are connected, ask the user to provide:

• What was accomplished since the last update
• Current blockers or risks
• Key decisions made or needed
• What is coming next

4. Generate the Update

Structure the update for the target audience using the templates and frameworks below.

For executives: TL;DR, status color (G/Y/R), key progress tied to goals, decisions made, risks with mitigation, specific asks, and next milestones. Keep it under 300 words.

For engineering: What shipped (with links), what is in progress (with owners), blockers, decisions needed (with options and recommendation), and what is coming next.

For cross-functional partners: What is coming that affects them, what you need from them (with deadlines), decisions that impact their team, and areas open for input.

For customers: What is new (framed as benefits), what is coming soon, known issues with workarounds, and how to provide feedback. No internal jargon.

For launch announcements: What launched, why it matters, key details (scope, availability, limitations), success metrics, rollout plan, and feedback channels.

5. Review and Deliver

After generating the update:

• Ask if the user wants to adjust tone, detail level, or emphasis
• Offer to format for the delivery channel (email, chat post, doc, slides)
• If ~~chat is connected, offer to draft the message for sending

Update Templates by Audience

Executive / Leadership Update

Executives want: strategic context, progress against goals, risks that need their help, decisions that need their input.

Format:

Status: [Green / Yellow / Red]

TL;DR: [One sentence — the most important thing to know]

Progress:
- [Outcome achieved, tied to goal/OKR]
- [Milestone reached, with impact]
- [Key metric movement]

Risks:
- [Risk]: [Mitigation plan]. [Ask if needed].

Decisions needed:
- [Decision]: [Options with recommendation]. Need by [date].

Next milestones:
- [Milestone] — [Date]

Tips for executive updates:

…

customer-research

围绕客户问题进行多来源调研与溯源，快速整理背景并支持准确回复。

digest

汇总多来源每日或每周动态，快速掌握提及、待办与项目进展