メニュー
This skill should be used when the user asks to "document discussion", "save meeting notes", "record conversation", "capture meeting", or mentions needing to document team discussions with participants, decisions, and action items.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Use when the user asks to "create a tortoise model", "new tortoise project", "tortoise orm", "async orm", "aerich migration", "fastapi tortoise", "tortoise model abstract", "tortoise base class", or mentions Tortoise ORM project structure, model organization, querysets, signals, transactions, or testing. Provides opinionated enterprise patterns: model-per-file, abstract Base interfaces for mocks/transitions, strict class member ordering, FastAPI lifespan, built-in Tortoise migrations (never Aerich), Pydantic v2, pytest.
Use when the user wants to embed an architecture diagram directly inside a React/Vite site as inline SVG (no html2canvas, no external scripts, no separate HTML file). Produces an `arch-diagram` fenced markdown block that the site's React renderer expands — including `<lucide-icon>` placeholders for semantic icons. Companion to the `architecture-diagram` skill, which produces standalone HTML.
Use when the user asks for a system, infrastructure, cloud, security, network topology, or architecture diagram. Produces polished dark-themed self-contained HTML+SVG files with mathematically-correct label placement, clean-background priority, text halos, and leader lines.
Use when the user asks for a mindmap, mind-map, concept map, idea tree, brainstorm diagram, or any radial topic explosion ("draw a mindmap of X", "map out the themes around Y", "mindmap the differentiators of Z"). Produces dark-themed self-contained HTML+SVG with a central root, branches radiating in all directions, halo text, Q-curved Bezier connectors, and geometry-audit gating.
Use when the user asks for a sequence diagram, ladder diagram, message-exchange diagram, or any temporal flow showing who talks to whom in order ("draw the OAuth flow", "show the request lifecycle", "diagram the protocol over time", "sequence diagram for X"). Produces dark-themed self-contained SVG with actor lifelines, sync/async/return messages, self-loops, halo text, and a geometry-audit gate that knows about lifelines.
This skill should be used when the user asks to "create ADR", "document decision", "architecture decision", "add decision record", or mentions needing to record a technical decision with status tracking and category organization.
| name | secondbrain-discussion |
| description | This skill should be used when the user asks to "document discussion", "save meeting notes", "record conversation", "capture meeting", or mentions needing to document team discussions with participants, decisions, and action items. |
Capture team discussions with participants, decisions, and action items.
Verify Discussions entity is enabled:
.claude/data/discussions/schema.yamlsecondbrain-initEntityTable component on docs/discussions/index.md, which reads from monthly .claude/data/discussions/YYYY-MM.yaml files. No sidebar modification is needed.Collect from user or conversation context:
Filename format: docs/discussions/YYYY-MM-DD-<participant>-<topic-slug>.md
Example: docs/discussions/2026-01-15-sergey-kubernetes-migration.md
---
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/CD pipeline changes
Add to monthly file .claude/data/discussions/YYYY-MM.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
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.
## 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
### Summary
- 2 decisions recorded
- 3 action items created
- 2 open questions noted
### Next Steps
- Follow up on action items
- Address open questions in next discussion
Discussions are partitioned by month:
discussions/2025-12.yaml — December 2025discussions/2026-01.yaml — January 2026Past months become immutable, preserving history.
| Source | Description |
|---|---|
| manual | Hand-documented discussion |
| meeting | From a scheduled meeting |
| slack | From Slack conversation |