secondbrain-discussion

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Document Discussion

记录讨论

Capture team discussions with participants, decisions, and action items.

捕获包含参会人员、决策和行动项的团队讨论内容。

Prerequisites

前提条件

Verify Discussions entity is enabled:

Check for
```
.claude/data/discussions/schema.yaml
```
If not found, suggest enabling discussions via
```
secondbrain-init
```

确认Discussions实体已启用：

检查是否存在
```
.claude/data/discussions/schema.yaml
```
文件
若未找到，建议通过
```
secondbrain-init
```
启用discussions功能

Workflow

工作流程

Step 1: Gather Information

步骤1：收集信息

Collect from user or conversation context:

Participant(s) — Who was in the discussion
Topic — Main subject discussed
Source — manual, meeting, slack
Key Points — Discussion content
Decisions — What was decided
Action Items — Follow-up tasks

从用户或对话上下文收集以下内容：

参会人员 — 讨论涉及的人员
主题 — 讨论的核心议题
来源 — manual（手动记录）、meeting（会议）、slack（Slack对话）
关键点 — 讨论的具体内容
决策 — 达成的决议
行动项 — 后续跟进任务

Step 2: Generate Discussion File

步骤2：生成讨论文件

Filename format:

docs/discussions/YYYY-MM-DD-<participant>-<topic-slug>.md

Example:

docs/discussions/2026-01-15-sergey-kubernetes-migration.md

文件名格式：

docs/discussions/YYYY-MM-DD-<participant>-<topic-slug>.md

示例：

docs/discussions/2026-01-15-sergey-kubernetes-migration.md

Step 3: Create Discussion Document

步骤3：创建讨论文档

markdown

---
date: 2026-01-15
participants:
  - Sergey Bershadsky
  - Kate Angelopoulos
topic: Kubernetes Migration Planning
status: documented
source: meeting
tags: [kubernetes, infrastructure, planning]
---

markdown

---
date: 2026-01-15
participants:
  - Sergey Bershadsky
  - Kate Angelopoulos
topic: Kubernetes Migration Planning
status: documented
source: meeting
tags: [kubernetes, infrastructure, planning]
---

Kubernetes Migration Planning

Date: 2026-01-15 Participants: Sergey Bershadsky, Kate Angelopoulos

Context

背景

Why did this discussion happen?

本次讨论的起因是什么？

Discussion Points

讨论要点

Migration Timeline

迁移时间线

Discussion:

Discussed phased approach
Agreed on staging first

Outcome: Start with staging environment by end of Q1

讨论内容：

讨论了分阶段实施的方案
一致同意先从预发布环境开始

结果： 在Q1末前完成预发布环境的搭建

Resource Requirements

资源需求

Discussion:

Node sizing
Cost implications

Outcome: Will use 3 node cluster initially

讨论内容：

节点规格
成本影响

结果： 初期将使用3节点集群

Decisions Made

已达成的决策

Decision	Owner	Deadline
Set up staging cluster	Sergey	2026-01-31
Document runbook	Kate	2026-02-15

决策内容	负责人	截止日期
搭建预发布集群	Sergey	2026-01-31
编写操作手册	Kate	2026-02-15

Action Items

行动项

Create staging environment — @sergey
Write migration runbook — @kate
Schedule follow-up review — @sergey

创建预发布环境 — @sergey
编写迁移操作手册 — @kate
安排后续复盘会议 — @sergey

Open Questions

待解决问题

What's the rollback strategy?
How do we handle stateful services?

回滚策略是什么？
如何处理有状态服务？

Follow-up

后续安排

Next discussion scheduled for: 2026-01-22
Related topics to explore: CI/CD pipeline changes

undefined

下次讨论时间：2026-01-22
待探索相关议题：CI/CD流水线变更

undefined

Step 4: Update Records

步骤4：更新记录

Add to monthly file

.claude/data/discussions/YYYY-MM.yaml

yaml

- date: 2026-01-15
  member: sergey
  topic: Kubernetes Migration Planning
  file: docs/discussions/2026-01-15-sergey-kubernetes-migration.md
  source: meeting
  participants:
    - Sergey Bershadsky
    - Kate Angelopoulos

将内容添加至月度文件

.claude/data/discussions/YYYY-MM.yaml

：

yaml

- date: 2026-01-15
  member: sergey
  topic: Kubernetes Migration Planning
  file: docs/discussions/2026-01-15-sergey-kubernetes-migration.md
  source: meeting
  participants:
    - Sergey Bershadsky
    - Kate Angelopoulos

Step 5: Sidebar Note

步骤5：侧边栏说明

DO NOT manually add discussions to VitePress sidebar.

Discussions are automatically listed via the

EntityTable

component on

docs/discussions/index.md

, which reads from monthly

.claude/data/discussions/YYYY-MM.yaml

files. No sidebar modification needed.

请勿手动将讨论内容添加到VitePress侧边栏。

讨论内容会通过

docs/discussions/index.md

页面上的

EntityTable

组件自动列出，该组件会读取月度

.claude/data/discussions/YYYY-MM.yaml

文件，无需修改侧边栏。

Step 6: Confirm Creation

步骤6：确认创建完成

undefined

undefined

Discussion Documented

讨论已记录

Date: 2026-01-15 Topic: Kubernetes Migration Planning Participants: Sergey Bershadsky, Kate Angelopoulos Source: meeting File: docs/discussions/2026-01-15-sergey-kubernetes-migration.md

日期： 2026-01-15 主题： Kubernetes Migration Planning 参会人员： Sergey Bershadsky, Kate Angelopoulos 来源： meeting 文件路径： docs/discussions/2026-01-15-sergey-kubernetes-migration.md

Summary

摘要

2 decisions recorded
3 action items created
2 open questions noted

记录了2项决策
创建了3个行动项
记录了2个待解决问题

Next Steps

下一步

Follow up on action items
Address open questions in next discussion

undefined

跟进行动项的执行
在下次讨论中解决待解决问题

undefined

Monthly Partitioning

月度分区管理

Discussions are partitioned by month:

```
discussions/2025-12.yaml
```
— December 2025
```
discussions/2026-01.yaml
```
— January 2026

Past months become immutable, preserving history.

讨论内容按月份分区存储：

```
discussions/2025-12.yaml
```
— 2025年12月
```
discussions/2026-01.yaml
```
— 2026年1月

过往月份的记录将设为不可修改，以保留历史数据。

Sources

来源类型

Source	Description
manual	Hand-documented discussion
meeting	From a scheduled meeting
slack	From Slack conversation

来源	说明
manual	手动记录的讨论内容
meeting	来自已安排的正式会议
slack	来自Slack对话

Tips

小贴士

Capture decisions explicitly — Use the table format
Create action items — Every decision should have an owner
Note open questions — Track what needs follow-up
Link to related content — Reference ADRs, notes, etc.
Document context — Future readers need to understand "why"

明确记录决策 — 使用表格格式
创建行动项 — 每项决策都应指定负责人
记录待解决问题 — 跟踪需要后续跟进的内容
关联相关内容 — 引用ADRs、笔记等资料
记录背景信息 — 让未来的阅读者理解“为什么”进行本次讨论