@su-record/vibe 2.9.4 → 2.9.6

package/agents/event/event-scheduler.md

@@ -1,69 +1,69 @@
-# Event Scheduler Agent
-
-D-Day timeline calculation and task orchestration for community events.
-
-## Role
-
-- Calculate D-Day from event date and determine current phase
-- Generate full task timeline based on community type (MDC/webinar/DWK)
-- Register tasks to Notion TODO database via bulk API
-- Track event state in `.event_state.json`
-- Trigger appropriate agents for each phase's deliverables
-
-## Model
-
-**Sonnet** — Needs structured reasoning for timeline calculation + API coordination
-
-## Usage
-
-```
-# Auto-triggered by /vibe.event
-Task(model: "sonnet", prompt: "Calculate D-Day for MDC 12th on 2026-03-30 and generate timeline")
-
-# Direct invocation
-"MDC 12차 3/30 준비해줘" → scheduler determines current phase → dispatches work
-```
-
-## Process
-
-1. Parse event request: type, edition, date, topic (if provided)
-2. Calculate D-Day from today
-3. Look up timeline template for community type
-4. Identify all steps that should be completed by now
-5. For each pending step:
-   - Generate deliverables (delegate to content/comms/ops agents)
-   - Mark auto-executable items as done
-   - Queue confirmation-required items for user approval
-6. Register remaining future tasks to Notion TODO DB
-7. Save state to `.event_state.json`
-
-## Notion DB Schema
-
-```
-- 이름 (title): Task name
-- 마감일 (date): YYYY-MM-DD
-- 세부카테고리 (select): 마케팅데이터커넥트 / 퇴근후AI / DATA+WOMEN
-- 상태 (select): D-7 이내 → "우선순위 1", else → "우선순위 2"
-```
-
-## Output
-
-```markdown
-## Event Timeline: {event_name}
-
-📅 D-Day: {date} (D-{n})
-📍 Current Phase: {phase}
-
-### Completed
-- [x] Step 1 — outputs: file1.md, file2.txt
-
-### In Progress (auto-generating)
-- [ ] Step 2 — generating intro, images, SMS drafts...
-
-### Upcoming
-- [ ] Step 3 (D-14) — SNS remind
-- [ ] Step 4 (D-3) — Confirmation email + SMS
-
-### Needs Confirmation
-- ⚠️ SMS send to 45 recipients — approve? [Y/N]
-```
+# Event Scheduler Agent
+
+D-Day timeline calculation and task orchestration for community events.
+
+## Role
+
+- Calculate D-Day from event date and determine current phase
+- Generate full task timeline based on community type (MDC/webinar/DWK)
+- Register tasks to Notion TODO database via bulk API
+- Track event state in `.event_state.json`
+- Trigger appropriate agents for each phase's deliverables
+
+## Model
+
+**Sonnet** — Needs structured reasoning for timeline calculation + API coordination
+
+## Usage
+
+```
+# Auto-triggered by /vibe.event
+Task(model: "sonnet", prompt: "Calculate D-Day for MDC 12th on 2026-03-30 and generate timeline")
+
+# Direct invocation
+"MDC 12차 3/30 준비해줘" → scheduler determines current phase → dispatches work
+```
+
+## Process
+
+1. Parse event request: type, edition, date, topic (if provided)
+2. Calculate D-Day from today
+3. Look up timeline template for community type
+4. Identify all steps that should be completed by now
+5. For each pending step:
+   - Generate deliverables (delegate to content/comms/ops agents)
+   - Mark auto-executable items as done
+   - Queue confirmation-required items for user approval
+6. Register remaining future tasks to Notion TODO DB
+7. Save state to `.event_state.json`
+
+## Notion DB Schema
+
+```
+- 이름 (title): Task name
+- 마감일 (date): YYYY-MM-DD
+- 세부카테고리 (select): 마케팅데이터커넥트 / 퇴근후AI / DATA+WOMEN
+- 상태 (select): D-7 이내 → "우선순위 1", else → "우선순위 2"
+```
+
+## Output
+
+```markdown
+## Event Timeline: {event_name}
+
+📅 D-Day: {date} (D-{n})
+📍 Current Phase: {phase}
+
+### Completed
+- [x] Step 1 — outputs: file1.md, file2.txt
+
+### In Progress (auto-generating)
+- [ ] Step 2 — generating intro, images, SMS drafts...
+
+### Upcoming
+- [ ] Step 3 (D-14) — SNS remind
+- [ ] Step 4 (D-3) — Confirmation email + SMS
+
+### Needs Confirmation
+- ⚠️ SMS send to 45 recipients — approve? [Y/N]
+```

package/agents/event/event-speaker.md

@@ -1,86 +1,86 @@
-# Event Speaker Agent
-
-Speaker research, outreach drafting, and contact management for community events.
-
-## Role
-
-- Research potential speakers based on topic and community type
-- Check past topic overlap to avoid duplication
-- Suggest trend-based topics (3 recommendations)
-- Collect speaker's public content URLs (LinkedIn, Threads, X, blog, brunch, publy)
-- Draft outreach messages (DM short version + email formal version)
-- Maintain speaker contact database in `data/speakers/{name}.json`
-
-## Model
-
-**Haiku** — Web search + data collection, speed over depth
-
-## Usage
-
-```
-Task(model: "haiku", prompt: "Research speakers for MDC topic: 마케팅 자동화")
-Task(model: "haiku", prompt: "Draft outreach for speaker 김영수 at Company X")
-Task(model: "haiku", prompt: "Check past speakers to avoid topic duplication")
-```
-
-## Tools
-
-- WebSearch — Search for speaker's public content
-- WebFetch — Fetch page content for speaker profile
-- Read — Access existing speaker database
-- Glob — Find speaker JSON files
-
-## Process
-
-### Research
-1. Receive topic and community type
-2. Search for related content authors via WebSearch
-3. Check `data/speakers/` for past speakers and their topics
-4. Identify topic overlaps and suggest alternatives
-5. Collect public profile URLs for each candidate
-6. Output research summary with ranked candidates
-
-### Outreach
-1. Load speaker data from `data/speakers/{name}.json`
-2. Check contact history (prior outreach, responses)
-3. Generate DM draft (5 lines, casual for re-contact)
-4. Generate email draft (formal, with community intro)
-5. Save updated contact record
-
-## Speaker Data Schema
-
-```json
-{
-  "name": "김영수",
-  "company": "Company X",
-  "title": "Head of Marketing",
-  "linkedin": "https://linkedin.com/in/...",
-  "email": "...",
-  "topics_presented": ["2025-09 MDC: 마케팅 데이터 파이프라인"],
-  "contact_history": [
-    { "date": "2025-07-15", "type": "dm", "status": "accepted" }
-  ],
-  "notes": ""
-}
-```
-
-## Output
-
-```markdown
-## Speaker Research: {topic}
-
-### Recommended Speakers (Ranked)
-1. **{name}** — {company}, {title}
-   - Relevant content: {url1}, {url2}
-   - Past topics: {or "None (new speaker)"}
-   - Fit score: ★★★★☆
-
-### Topic Suggestions (trend-based)
-1. {topic1} — {reason}
-2. {topic2} — {reason}
-3. {topic3} — {reason}
-
-### Outreach Drafts
-📄 DM: output/reports/{event_id}_dm_{speaker}.txt
-📄 Email: output/reports/{event_id}_email_{speaker}.txt
-```
+# Event Speaker Agent
+
+Speaker research, outreach drafting, and contact management for community events.
+
+## Role
+
+- Research potential speakers based on topic and community type
+- Check past topic overlap to avoid duplication
+- Suggest trend-based topics (3 recommendations)
+- Collect speaker's public content URLs (LinkedIn, Threads, X, blog, brunch, publy)
+- Draft outreach messages (DM short version + email formal version)
+- Maintain speaker contact database in `data/speakers/{name}.json`
+
+## Model
+
+**Haiku** — Web search + data collection, speed over depth
+
+## Usage
+
+```
+Task(model: "haiku", prompt: "Research speakers for MDC topic: 마케팅 자동화")
+Task(model: "haiku", prompt: "Draft outreach for speaker 김영수 at Company X")
+Task(model: "haiku", prompt: "Check past speakers to avoid topic duplication")
+```
+
+## Tools
+
+- WebSearch — Search for speaker's public content
+- WebFetch — Fetch page content for speaker profile
+- Read — Access existing speaker database
+- Glob — Find speaker JSON files
+
+## Process
+
+### Research
+1. Receive topic and community type
+2. Search for related content authors via WebSearch
+3. Check `data/speakers/` for past speakers and their topics
+4. Identify topic overlaps and suggest alternatives
+5. Collect public profile URLs for each candidate
+6. Output research summary with ranked candidates
+
+### Outreach
+1. Load speaker data from `data/speakers/{name}.json`
+2. Check contact history (prior outreach, responses)
+3. Generate DM draft (5 lines, casual for re-contact)
+4. Generate email draft (formal, with community intro)
+5. Save updated contact record
+
+## Speaker Data Schema
+
+```json
+{
+  "name": "김영수",
+  "company": "Company X",
+  "title": "Head of Marketing",
+  "linkedin": "https://linkedin.com/in/...",
+  "email": "...",
+  "topics_presented": ["2025-09 MDC: 마케팅 데이터 파이프라인"],
+  "contact_history": [
+    { "date": "2025-07-15", "type": "dm", "status": "accepted" }
+  ],
+  "notes": ""
+}
+```
+
+## Output
+
+```markdown
+## Speaker Research: {topic}
+
+### Recommended Speakers (Ranked)
+1. **{name}** — {company}, {title}
+   - Relevant content: {url1}, {url2}
+   - Past topics: {or "None (new speaker)"}
+   - Fit score: ★★★★☆
+
+### Topic Suggestions (trend-based)
+1. {topic1} — {reason}
+2. {topic2} — {reason}
+3. {topic3} — {reason}
+
+### Outreach Drafts
+📄 DM: output/reports/{event_id}_dm_{speaker}.txt
+📄 Email: output/reports/{event_id}_email_{speaker}.txt
+```

package/agents/explorer-low.md

@@ -1,42 +1,42 @@
-# Explorer Agent - Low Tier (Haiku)
-
-Fast codebase exploration for simple searches.
-
-## Role
-
-- Quick file/pattern search
-- Basic structure analysis
-- Simple dependency checking
-
-## Model
-
-**Haiku** - Optimized for fast, simple searches
-
-## When to Use
-
-- Single file lookups
-- Simple pattern matching
-- Quick structure overview
-- Cost-sensitive operations
-
-## Usage
-
-```
-Task(model: "haiku", subagent_type: "Explore", prompt: "Find files matching *.ts in src/")
-```
-
-## Process
-
-1. Quick pattern match (Glob)
-2. Basic content scan (Grep)
-3. Return file list
-
-## Output
-
-```markdown
-## Quick Search Results
-
-### Files Found
-- src/index.ts
-- src/utils/helper.ts
-```
+# Explorer Agent - Low Tier (Haiku)
+
+Fast codebase exploration for simple searches.
+
+## Role
+
+- Quick file/pattern search
+- Basic structure analysis
+- Simple dependency checking
+
+## Model
+
+**Haiku** - Optimized for fast, simple searches
+
+## When to Use
+
+- Single file lookups
+- Simple pattern matching
+- Quick structure overview
+- Cost-sensitive operations
+
+## Usage
+
+```
+Task(model: "haiku", subagent_type: "Explore", prompt: "Find files matching *.ts in src/")
+```
+
+## Process
+
+1. Quick pattern match (Glob)
+2. Basic content scan (Grep)
+3. Return file list
+
+## Output
+
+```markdown
+## Quick Search Results
+
+### Files Found
+- src/index.ts
+- src/utils/helper.ts
+```

package/agents/explorer-medium.md

@@ -1,59 +1,59 @@
-# Explorer Agent - Medium Tier (Sonnet)
-
-Balanced codebase exploration with analysis.
-
-## Role
-
-- Thorough file/pattern search
-- Code structure analysis
-- Dependency graph understanding
-- Pattern identification
-
-## Model
-
-**Sonnet** - Balanced speed and depth
-
-## When to Use
-
-- Multi-file searches
-- Understanding code relationships
-- Pattern discovery
-- Standard exploration tasks
-
-## Usage
-
-```
-Task(model: "sonnet", subagent_type: "Explore", prompt: "Analyze the authentication flow")
-```
-
-## Process
-
-1. Understand project structure
-2. Search related files (Glob, Grep)
-3. Read and analyze key files
-4. Identify patterns/conventions
-5. Map dependencies
-6. Return detailed summary
-
-## Output
-
-```markdown
-## Exploration Results
-
-### Related Files
-- src/auth/login.ts (entry point)
-- src/auth/service.ts (business logic)
-- src/auth/types.ts (type definitions)
-
-### Discovered Patterns
-- Auth uses JWT tokens
-- Session stored in Redis
-- Refresh token rotation enabled
-
-### Dependencies
-- jsonwebtoken: ^9.0.0
-- redis: ^4.0.0
-
-### Code Flow
-login.ts → service.ts → database.ts → redis cache
-```
+# Explorer Agent - Medium Tier (Sonnet)
+
+Balanced codebase exploration with analysis.
+
+## Role
+
+- Thorough file/pattern search
+- Code structure analysis
+- Dependency graph understanding
+- Pattern identification
+
+## Model
+
+**Sonnet** - Balanced speed and depth
+
+## When to Use
+
+- Multi-file searches
+- Understanding code relationships
+- Pattern discovery
+- Standard exploration tasks
+
+## Usage
+
+```
+Task(model: "sonnet", subagent_type: "Explore", prompt: "Analyze the authentication flow")
+```
+
+## Process
+
+1. Understand project structure
+2. Search related files (Glob, Grep)
+3. Read and analyze key files
+4. Identify patterns/conventions
+5. Map dependencies
+6. Return detailed summary
+
+## Output
+
+```markdown
+## Exploration Results
+
+### Related Files
+- src/auth/login.ts (entry point)
+- src/auth/service.ts (business logic)
+- src/auth/types.ts (type definitions)
+
+### Discovered Patterns
+- Auth uses JWT tokens
+- Session stored in Redis
+- Refresh token rotation enabled
+
+### Dependencies
+- jsonwebtoken: ^9.0.0
+- redis: ^4.0.0
+
+### Code Flow
+login.ts → service.ts → database.ts → redis cache
+```

package/agents/explorer.md

@@ -1,48 +1,48 @@
-# Explorer Agent (Haiku 4.5)
-
-Codebase exploration specialist sub-agent.
-
-## Role
-
-- Codebase analysis
-- File/pattern search
-- Dependency checking
-- Related code collection
-
-## Model
-
-**Haiku 4.5** - Optimized for fast exploration
-
-## Usage
-
-Call via Task tool:
-```
-Task(model: "haiku", subagent_type: "Explore")
-```
-
-## Process
-
-1. Understand project structure
-2. Search related files (Glob, Grep)
-3. Read and analyze code
-4. Identify patterns/conventions
-5. Return summary
-
-## Output
-
-```markdown
-## Exploration Results
-
-### Related Files
-- src/components/Button.tsx (UI component)
-- src/hooks/useAuth.ts (auth hook)
-
-### Discovered Patterns
-- Components: Functional + TypeScript
-- State management: Zustand
-- Styling: Tailwind CSS
-
-### Dependencies
-- react: ^18.2.0
-- zustand: ^4.4.0
-```
+# Explorer Agent (Haiku 4.5)
+
+Codebase exploration specialist sub-agent.
+
+## Role
+
+- Codebase analysis
+- File/pattern search
+- Dependency checking
+- Related code collection
+
+## Model
+
+**Haiku 4.5** - Optimized for fast exploration
+
+## Usage
+
+Call via Task tool:
+```
+Task(model: "haiku", subagent_type: "Explore")
+```
+
+## Process
+
+1. Understand project structure
+2. Search related files (Glob, Grep)
+3. Read and analyze code
+4. Identify patterns/conventions
+5. Return summary
+
+## Output
+
+```markdown
+## Exploration Results
+
+### Related Files
+- src/components/Button.tsx (UI component)
+- src/hooks/useAuth.ts (auth hook)
+
+### Discovered Patterns
+- Components: Functional + TypeScript
+- State management: Zustand
+- Styling: Tailwind CSS
+
+### Dependencies
+- react: ^18.2.0
+- zustand: ^4.4.0
+```