1) Decide if a meeting is needed and pick the format
1) 判断是否需要会议并选择合适形式
Inputs: Request + context + constraints.
Actions: Clarify objective; decide whether the live meeting is for discussion only; pick meeting type (operational vs strategic vs decision vs workshop).
Checks: No important decision is left implicit or “to be clarified later.”
输入： 引导脚本；记录模板
行动： 以预热内容开场；引导讨论；实时记录决策和行动项；严格遵守时间限制
输出： 填写完成的记录+决策日志条目+行动项表格
校验： 所有重要决策均被明确记录，无隐含或“待后续澄清”的内容
7) Close, follow up, and improve meeting hygiene
7) 收尾、跟进及优化会议规范
Inputs: Captured notes/decisions/actions.
Actions: End with: (1) What did we decide? (2) Who does what by when? (3) Who else needs to know? Send follow-up within 24h; propose hygiene changes (split strategic vs operational, cancel/shorten recurring meetings).
Example 1 (Operational cadence): “Design a weekly operational meeting for a product squad to track priority projects without drifting into strategy.”
Expected: a structured meeting brief, recurring agenda template, status update pattern, and a hygiene rule to move strategy to a separate forum.
Example 2 (Decision meeting): “Create a decision meeting pack for choosing between two onboarding flows (A vs B) with PM/Design/Eng and a decision owner.”
Expected: pre-read with options + evidence, timed agenda, facilitation prompts for trade-offs, and a decision record + action items.
Boundary example: “Schedule a meeting to ‘get alignment’ but there’s no decision, no owner, and no pre-read.”
Response: ask for the decision/outcome; recommend async discovery first; refuse to produce a meeting pack until objective/owner is defined.