---
id: wiki-2026-0508-team-collaboration
title: Team Collaboration
category: 10_Wiki/Topics
status: verified
canonical_id: self
aliases: [Team Collaboration, async work, sync vs async, RFC process]
duplicate_of: none
source_trust_level: A
confidence_score: 0.9
verification_status: applied
tags: [collaboration, remote-work, async, rfc, ai-aided]
raw_sources: []
last_reinforced: 2026-05-10
github_commit: pending
tech_stack:
  language: n-a
  framework: process
---

# 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.

### 매 응용
1. Distributed startup (3 timezones) — async-first + 2x weekly sync.
2. Open-source maintainer + contributors — RFC + GitHub Discussions.
3. AI-augmented team — agent의 boilerplate PR + human의 review.

## 💻 패턴

### RFC template
```markdown
# 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
```markdown
# 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)
```markdown
# 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
```yaml
# .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
```markdown
# 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 |