返回 Skill 列表
extension
分类: 开发与工程无需 API Key

event-status-update-ptsf

通过综合Linear问题、Gmail线程和过去的对话生成ProductTank SF活动状态报告。当被问及活动状态、演讲者协调状态、即将举行的活动情况、活动准备情况或任何关于ProductTank SF的“[活动/演讲者]的状态是什么”的查询时使用。

person作者: jakexiaohubgithub

Event Status Update Workflow

Data Sources

| Source | What to Find | How to Access | |--------|--------------|---------------| | Linear | Issue status, blockers, timelines, checklist progress | linear-cli i list -t "Product Tank SF", linear-cli i get <ID>, linear-cli p get <ID> | | Gmail | Speaker communications, confirmations, pending replies | search_gmail_messages with q: "from:wmfrederick+producttanksf@gmail.com OR to:wmfrederick+producttanksf@gmail.com [speaker/event name]" | | Speaker Form Results | Speaker submissions, talk titles, bios, availability | Speaker Formgdrive:gsheets_read spreadsheetId: 1GN2mAqlv_QRdCD4cuIplw_8IbwfjwpdlHTe7CSlcagY | | Master Event Spreadsheet | Event calendar, venue info, budget, sponsor tracking | Master Eventsgdrive:gsheets_read spreadsheetId: 1RnNx_kF0YsaiG2VlcgMO1oVs56rjKBIxtQKjVsvwq2o | | Past Conversations | Prior context, issue IDs, decisions made | conversation_search |

Process

1. Gather Context

  • conversation_search for event/speaker name to find issue IDs and recent activity
  • Note the main coordination issue (e.g., PRO-42)

2. Get Linear Details

  • linear-cli p get <PROJECT_ID> --output json for project description, event date, venue, speaker details
  • linear-cli i get <ISSUE_ID> --output json for main issue status, timeline, blockers, due dates
  • Extract progress from "Event Definition of Done Checklist"

3. Check Google Sheets

  • Speaker Form Results — speaker submissions, proposed talk titles, contact info
  • Master Event Spreadsheet — event dates, venue details, budget status, sponsor commitments

4. Check Recent Communications

  • search_gmail_messages with q: "from:wmfrederick+producttanksf@gmail.com OR to:wmfrederick+producttanksf@gmail.com [speaker/event] after:[7-10 days ago]"
  • Note last contact date, what's confirmed vs pending

5. Synthesize Using Template Below

Output Template

## Event Status: **[Status]** ([Brief Context])

**Event Date:** [Date, Time]
**Speaker:** [Name] - "[Talk Title]"
**Expected Attendance:** [Number]

### ✅ What's Confirmed:
- [Speaker details, budget, sponsors, locked-in logistics]

### 🔴 What's Blocked:
[Timeline context first (e.g., "30 days behind schedule"), then numbered blockers with issue IDs]

### 📅 Last Communication:
**[Date]**: [Summary]

**Next action needed:** [Specific action with name and deliverable]

Status Labels

  • Confirmed - All major pieces locked in
  • On Track - Minor details pending, on schedule
  • At Risk - Behind schedule but recoverable
  • Blocked - Cannot proceed without external action
  • On Hold - Paused pending decision

Key Principles

  • Lead with status assessment, not details
  • Include specific dates, names, dollar amounts
  • State timeline gaps explicitly (e.g., "30 days behind")
  • End with concrete next step (who does what)
  • Focus on recent 7-10 days of activity