brief
產生法務每日、主題或事件應變的情境式簡報
中文翻譯
--- name: brief description: 為法務工作產生情境式簡報：每日摘要、主題研究或事件應變。當你一天開始時需要掃過 email、行事曆和合約裡跟法務有關的事項、需要跨內部來源研究某個特定法律問題，或有正在發展的狀況（資料外洩、訴訟威脅、主管機關詢問）需要快速掌握背景時使用。 argument-hint: "[daily | topic <query> | incident]" --- # /brief -- 法務團隊簡報 > 如果看到不熟的 placeholder，或需要確認目前連了哪些工具，請看 [CONNECTORS.md](../../CONNECTORS.md)。 為法務工作產生情境式簡報。支援三種模式：每日簡報、主題簡報和事件簡報。 **重要**：這個指令協助處理法務工作流程，但不提供法律意見。簡報在被採信之前，應該由合格的法務專業人員審閱。 ## 呼叫方式 ``` /brief daily # 與法務相關事項的晨間簡報 /brief topic [query] # 針對特定法律問題的研究簡報 /brief incident [topic] # 針對正在發展的狀況的快速簡報 ``` 如果沒有指定模式，就問使用者需要哪一種簡報。 ## 模式 --- ### 每日簡報 法務團隊成員開始一天所需要知道的所有事情的晨間摘要。 #### 要掃描的來源 檢查每個已連線的來源，找出跟法務相關的事項： **Email（如果有連線）：** - 新的合約請求或審閱請求 - 合規問題或報告 - 對方在進行中的談判裡的回覆 - 法務團隊信箱裡被標記或緊急的事項 - 外部律師的來信 - 法規或法律更新電子報 **行事曆（如果有連線）：** - 今天需要法務準備的會議（董事會、交易審查、廠商電話會議） - 本週即將到來的期限（合約到期、申報期限、回覆期限） - 定期的法務團隊同步會議 **聊天（如果有連線）：** - 法務團隊頻道裡的隔夜訊息 - 請求法務意見的私訊 - 提到法務相關主題的訊息（合約、合規、隱私、NDA、條款） - 升級處理或緊急請求 **CLM（如果有連線）：** - 等待審閱或簽署的合約 - 即將到期的日期（未來 30 天） - 新簽訂的協議 **CRM（如果有連線）：** - 進入需要法務介入的階段的交易 - 被標記要法務審查的新商機 #### 輸出格式 ``` ## 法務每日簡報 -- [日期] ### 緊急 / 需要處理 [需要立即處理的事項，依緊急程度排序] ### 合約管線 - **等你審閱**：[數量與清單] - **等對方回覆**：[數量與清單] - **即將到期**：[本週到期的事項] ### 新請求 [自上次簡報以來收到的合約審閱請求、NDA 請求、合規問題] ### 今日行事曆 [與法務相關的會議，以及需要做哪些準備] ### 團隊動態 [法務團隊頻道裡的重要訊息或更新] ### 本週期限 [即將到來的期限與申報日期] ### 無法取得的來源 [任何沒有連線或回傳錯誤的來源] ``` --- ### 主題簡報 跨可用來源，針對特定法律問題或主題做研究並整理成簡報。 #### 工作流程 1. 接收使用者的主題查詢 2. 在已連線的來源中搜尋： - **文件**：內部備忘錄、過去的分析、playbook、先例 - **Email**：過去關於這個主題的往來 - **聊天**：團隊對這個主題的討論 - **CLM**：相關的合約或條款 3. 把發現綜合成結構化的簡報 #### 輸出格式 ``` ## 主題簡報：[主題] ### 摘要 [2 到 3 句話的重點摘要] ### 背景 [來自內部來源的脈絡與歷史] ### 現況 [根據可用文件，組織目前的立場或做法] ### 關鍵考量 [重要因素、風險或未解的問題] ### 內部先例 [在內部來源中找到的過去決定、備忘錄或立場] ### 缺口 [缺少哪些資訊，或哪些來源無法取得] ### 建議的下一步 [使用者該拿這些資訊做什麼] ``` #### 重要注意事項 - 主題簡報是綜合已連線來源裡有的資料，不能取代正式的法律研究 - 如果主題需要最新的法律依據或判例，建議使用者去查法律研究平台（Westlaw、Lexis 等）或諮詢外部律師 - 一律註明所搜尋來源的限制 --- ### 事件簡報 針對需要法務立即關注的發展中狀況（資料外洩、訴訟威脅、主管機關詢問、智慧財產爭議等）的快速簡報。 #### 工作流程 1. 接收事件主題或描述 2. 快速掃描所有已連線的來源，找出相關背景： - **Email**：關於這個事件的往來 - **聊天**：即時討論與升級處理 - **文件**：相關政策、應變計畫、保險範圍 - **行事曆**：已排定的應變會議 - **CLM**：受影響的合約、賠償條款、保險要求 3. 彙整成可執行的事件簡報 #### 輸出格式 ``` ## 事件簡報：[主題] **準備時間**：[timestamp] **分級**：[如果能判斷，附上嚴重程度評估] ### 狀況摘要 [目前對這個事件已知的資訊] ### 時間線 [根據可用來源整理的事件時間順序摘要] ### 立即要考慮的法律事項 [主管機關通報要求、保全義務、律師當事人保密特權（privilege）的顧慮] ### 相關協議 [可能牽涉到的合約、保險單或其他協議] ### 內部應變 [根據 email 和聊天，已經發生了哪些應變行動] ### 關鍵聯絡人 [從來源中找出的相關內部與外部聯絡人] ### 建議的立即行動 1. [最緊急的行動] 2. [第二優先] 3. [以此類推] ### 資訊缺口 [還不知道、需要釐清的事情] ### 已檢查的來源 [搜尋了哪些來源，哪些無法取得] ``` #### 事件簡報的重要注意事項 - 速度最重要。用現有資訊快速產出簡報，不要等資訊完整才動手 - 任何訴訟保全（litigation hold）或證據保存義務要立刻標出來 - 註明 privilege 的考量（適當的話，把簡報標示為律師與當事人間保密溝通 / 工作成果） - 如果事件可能涉及資料外洩，標出適用的通報期限（例如 GDPR 的 72 小時） - 如果事情重大，建議委請外部律師 ## 一般注意事項 - 如果有來源無法取得，要醒目地註明缺口，讓使用者知道哪些沒檢查 - 每日簡報要隨著時間學習使用者的偏好（他覺得哪些有用，想過濾掉哪些） - 簡報要能行動：每一項都要有明確的下一步，或列入的理由 - 簡報要精簡。連結到來源資料，不要整份重貼
英文原文
--- name: brief description: Generate contextual briefings for legal work — daily summary, topic research, or incident response. Use when starting your day and need a scan of legal-relevant items across email, calendar, and contracts, when researching a specific legal question across internal sources, or when a developing situation (data breach, litigation threat, regulatory inquiry) needs rapid context. argument-hint: "[daily | topic <query> | incident]" --- # /brief -- Legal Team Briefing > If you see unfamiliar placeholders or need to check which tools are connected, see [CONNECTORS.md](../../CONNECTORS.md). Generate contextual briefings for legal work. Supports three modes: daily brief, topic brief, and incident brief. **Important**: This command assists with legal workflows but does not provide legal advice. Briefings should be reviewed by qualified legal professionals before being relied upon. ## Invocation ``` /brief daily # Morning brief of legal-relevant items /brief topic [query] # Research brief on a specific legal question /brief incident [topic] # Rapid brief on a developing situation ``` If no mode is specified, ask the user which type of brief they need. ## Modes --- ### Daily Brief A morning summary of everything a legal team member needs to know to start their day. #### Sources to Scan Check each connected source for legal-relevant items: **Email (if connected):** - New contract requests or review requests - Compliance questions or reports - Responses from counterparties on active negotiations - Flagged or urgent items from the legal team inbox - External counsel communications - Regulatory or legal update newsletters **Calendar (if connected):** - Today's meetings that need legal prep (board meetings, deal reviews, vendor calls) - Upcoming deadlines this week (contract expirations, filing deadlines, response deadlines) - Recurring legal team syncs **Chat (if connected):** - Overnight messages in legal team channels - Direct messages requesting legal input - Mentions of legal-relevant topics (contract, compliance, privacy, NDA, terms) - Escalations or urgent requests **CLM (if connected):** - Contracts awaiting review or signature - Approaching expiration dates (next 30 days) - Newly executed agreements **CRM (if connected):** - Deals moving to stages that require legal involvement - New opportunities flagged for legal review #### Output Format ``` ## Daily Legal Brief -- [Date] ### Urgent / Action Required [Items needing immediate attention, sorted by urgency] ### Contract Pipeline - **Awaiting Your Review**: [count and list] - **Pending Counterparty Response**: [count and list] - **Approaching Deadlines**: [items due this week] ### New Requests [Contract review requests, NDA requests, compliance questions received since last brief] ### Calendar Today [Meetings with legal relevance and what prep is needed] ### Team Activity [Key messages or updates from legal team channels] ### This Week's Deadlines [Upcoming deadlines and filing dates] ### Sources Not Available [Any sources that were not connected or returned errors] ``` --- ### Topic Brief Research and brief on a specific legal question or topic across available sources. #### Workflow 1. Accept the topic query from the user 2. Search across connected sources: - **Documents**: Internal memos, prior analyses, playbooks, precedent - **Email**: Prior communications on the topic - **Chat**: Team discussions about the topic - **CLM**: Related contracts or clauses 3. Synthesize findings into a structured brief #### Output Format ``` ## Topic Brief: [Topic] ### Summary [2-3 sentence executive summary of findings] ### Background [Context and history from internal sources] ### Current State [What the organization's current position or approach is, based on available documents] ### Key Considerations [Important factors, risks, or open questions] ### Internal Precedent [Prior decisions, memos, or positions found in internal sources] ### Gaps [What information is missing or what sources were not available] ### Recommended Next Steps [What the user should do with this information] ``` #### Important Notes - Topic briefs synthesize what is available in connected sources; they do not substitute for formal legal research - If the topic requires current legal authority or case law, recommend the user consult a legal research platform (Westlaw, Lexis, etc.) or outside counsel - Always note the limitations of the sources searched --- ### Incident Brief Rapid briefing for developing situations that require immediate legal attention (data breaches, litigation threats, regulatory inquiries, IP disputes, etc.). #### Workflow 1. Accept the incident topic or description 2. Rapidly scan all connected sources for relevant context: - **Email**: Communications about the incident - **Chat**: Real-time discussions and escalations - **Documents**: Relevant policies, response plans, insurance coverage - **Calendar**: Scheduled response meetings - **CLM**: Affected contracts, indemnification provisions, insurance requirements 3. Compile into an actionable incident brief #### Output Format ``` ## Incident Brief: [Topic] **Prepared**: [timestamp] **Classification**: [severity assessment if determinable] ### Situation Summary [What is known about the incident] ### Timeline [Chronological summary of events based on available sources] ### Immediate Legal Considerations [Regulatory notification requirements, preservation obligations, privilege concerns] ### Relevant Agreements [Contracts, insurance policies, or other agreements that may be implicated] ### Internal Response [What response activity has already occurred based on email/chat] ### Key Contacts [Relevant internal and external contacts identified from sources] ### Recommended Immediate Actions 1. [Most urgent action] 2. [Second priority] 3. [etc.] ### Information Gaps [What is not yet known and needs to be determined] ### Sources Checked [What was searched and what was not available] ``` #### Important Notes for Incident Briefs - Speed matters. Produce the brief quickly with available information rather than waiting for complete information - Flag any litigation hold or preservation obligations immediately - Note privilege considerations (mark the brief as attorney-client privileged / work product if appropriate) - If the incident may involve a data breach, flag applicable notification deadlines (e.g., 72 hours for GDPR) - Recommend outside counsel engagement if the matter is significant ## General Notes - If sources are unavailable, note the gaps prominently so the user knows what was not checked - For daily briefs, learn the user's preferences over time (what they find useful, what they want filtered out) - Briefs should be actionable: every item should have a clear next step or reason for inclusion - Keep briefs concise. Link to source materials rather than reproducing them in full