9148c358d0
Topic_Agent/Topic_Blog/Topics/Topics_Biz/Topics_Meeting/Topics_Rag의 마크다운 지식 문서를 Topic_General/Topic_Programming/Topic_Graphic/Topic_Business 4개 카테고리로 재분류. - 중복 제거: frontmatter의 status:duplicate/merged + duplicate_of/redirect_to 필드로 자기 자신을 중복으로 선언한 리다이렉트 stub 1032개 제거, 완전 동일 내용 파일 472개 제거, 동일 파일명·다른 내용 충돌 시 더 큰(완전한) 버전만 유지(162개 제거) — 총 1639개 중복 제거. - 분류: 폴더 단위로 명확한 항목(AI_and_ML/Coding/Architecture 등 → Programming, Comfyui/Visual_Effects → Graphic, Topics_Biz/Topics_Meeting/사업 등 → Business, Poetic_Blog_Writing/창의성/Game_Design 등 → General)은 폴더 우선순위로, 나머지 혼재 폴더(Topic_Agent/Topic_Blog/Topics 루트/Thinking & Reasoning/Other/UI_UX_Assets)는 title/tags 키워드 스코어링으로 파일 단위 분류(불명확한 경우 General로 폴백). 원본 폴더명은 "From_*" 서브폴더로 보존해 추적 가능성 유지. - 최종 배치: Programming 2784 / General 1608 / Graphic 285 / Business 249 = 4926개 문서. - 에이전트 운영 상태(.astra/.agent/.obsidian/sessions/memory/_company/docs/lessons/_shared/src)는 지식 콘텐츠가 아니므로 재분류 대상에서 제외하고 원위치 유지. - Topics/Topic_email(상위 보호 폴더 Topic_email과 파일명 100% 중복) 삭제 — 보호 폴더 자체는 미변경. - 완전히 비게 된 Topic_Agent/Topic_Blog/Topics_Biz/Topics_Rag 폴더 제거.
4.8 KiB
4.8 KiB
id, title, category, status, canonical_id, aliases, duplicate_of, source_trust_level, confidence_score, verification_status, tags, raw_sources, last_reinforced, github_commit, tech_stack
| id | title | category | status | canonical_id | aliases | duplicate_of | source_trust_level | confidence_score | verification_status | tags | raw_sources | last_reinforced | github_commit | tech_stack | |||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| wiki-2026-0508-team-collaboration | Team Collaboration | 10_Wiki/Topics | verified | self |
|
none | A | 0.9 | applied |
|
2026-05-10 | pending |
|
Team Collaboration
매 한 줄
"매 sync + async + AI-aided 매 hybrid 의 modern team collaboration — 매 right tool for the right cadence". 2026 매 distributed teams + AI agents (Claude Code, Devin, Cursor) 의 first-class teammate. 매 RFC + chat + async video + agent PR 의 layered stack.
매 핵심
매 Cadence layers
- Real-time (sync): huddle, pair-programming, incident war room.
- Near-real-time: Slack/Discord thread (response in hours).
- Async deep: RFC, design doc, Linear ticket (response in days).
- Permanent: wiki, ADR, Notion, this wiki.
매 AI-aided (2026)
- Agent PRs: Claude Code 의 small task 의 autonomous PR 의 file.
- Meeting summaries: Granola/Otter 의 transcript + action items.
- Async video: Loom + AI auto-chapter.
- Knowledge agent: 매 wiki + chat history 의 RAG agent (e.g. Glean).
매 Communication patterns
- DRI (Directly Responsible Individual): 매 task의 single owner.
- RACI: Responsible / Accountable / Consulted / Informed.
- Disagree & commit: 매 decision lock 후 의 execute.
매 응용
- Distributed startup (3 timezones) — async-first + 2x weekly sync.
- Open-source maintainer + contributors — RFC + GitHub Discussions.
- AI-augmented team — agent의 boilerplate PR + human의 review.
💻 패턴
RFC template
# RFC: <Title>
**Author**: @alice **Status**: Draft **Date**: 2026-05-10
## Problem
<1 paragraph>
## Proposal
<2-3 paragraphs>
## Alternatives considered
1. ...
2. ...
## Risks / Open questions
- ...
## Decision (filled after review)
<TBD>
Standup as async update
# Daily — 2026-05-10 — @alice
**Yesterday**: Shipped checkout v2 PR #421.
**Today**: Investigating flaky test in CI.
**Blockers**: None.
**FYI**: AWS quota raised, US-east-1 ok now.
Decision log (ADR)
# ADR-014: Adopt SQLite for analytics cache
Date: 2026-05-10
Status: Accepted
Context: Need <10ms read for dashboard.
Decision: SQLite + LiteFS replication.
Consequences: + simple ops, - 1 writer at a time.
Slack channel naming
#proj-checkout-eng # project work
#team-platform # team home
#help-frontend # ask experts
#inc-2026-05-09 # incident (auto-archived)
#fyi-shipping # broadcast
AI-agent task hand-off
# .claude/tasks/rename-billing-fields.yaml
agent: claude-opus-4-7
task: |
Rename `customer_id` to `account_id` across the billing module.
- Update tests
- Run `bun test`
- Open PR titled "rename: customer_id -> account_id"
human_review: required
auto_merge: false
Meeting decision capture
# Meeting — 2026-05-10 — Q3 Planning
**Decisions**:
1. Ship payments v3 by 2026-07-15 (DRI: @bob)
2. Defer GraphQL migration to 2026-Q4
**Action items** (synced to Linear):
- [ ] @alice: Draft RFC for payments v3 schema (due 2026-05-17)
- [ ] @bob: Spec out v3 webhook events (due 2026-05-24)
매 결정 기준
| 상황 | Channel |
|---|---|
| 매 incident in-progress | Sync war room (Zoom/Huddle) |
| 매 architectural decision | RFC + 1 week async review |
| 매 quick clarification | Slack thread |
| 매 onboarding context | Wiki / Loom video |
| 매 boilerplate refactor | AI agent PR |
기본값: 매 async-first, 매 sync 의 reserve 매 high-bandwidth (incident, brainstorm, 1:1).
🔗 Graph
- 부모: Team Topologies · Remote Work
- 변형: Pair Programming · Mob Programming
- 응용: Code Review · RFC Process
- Adjacent: ADR · Claude Code
🤖 LLM 활용
언제: 매 meeting summary, RFC draft, ADR generation, agent PR for chores. 매 knowledge RAG. 언제 X: 매 conflict resolution, performance review, layoff conversation. 매 human empathy 매 required.
❌ 안티패턴
- Sync-only team: 매 timezone 의 ignore, burnout.
- No DRI: 매 task의 ambient → drift.
- Slack as memory: 매 search 의 deteriorate, decisions 의 lost.
- Meeting without agenda: 매 time 의 burn, no decision.
- Agent PR auto-merge without review: 매 silent regression.
🧪 검증 / 중복
- Verified (GitLab handbook, Basecamp Shape Up 2026, Anthropic engineering blog).
- 신뢰도 A.
🕓 Changelog
| 날짜 | 변경 |
|---|---|
| 2026-05-08 | Phase 1 |
| 2026-05-10 | Manual cleanup — collaboration cadence layers + AI-aided + RFC/ADR templates |