secondbrain-discussion

# Document Discussion

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

## Prerequisites

Verify Discussions entity is enabled:
1. Check for `.claude/data/discussions/schema.yaml`
2. If not found, suggest enabling discussions via `secondbrain-init`

## Workflow

### Step 1: Gather Information

Collect from user or conversation context:

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

### Step 2: Generate Discussion File

**Filename format:** `docs/discussions/YYYY-MM-DD-<participant>-<topic-slug>.md`

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

### Step 3: Create Discussion Document

```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

### Resource Requirements

**Discussion:**
- Node sizing
- Cost implications

**Outcome:**
Will use 3 node cluster initially

## Decisions Made

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

## Action Items

- [ ] Create staging environment — @sergey
- [ ] Write migration runbook — @kate
- [ ] Schedule follow-up review — @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/