菜单
Use when the user says "standup", "what's on today", "quick status", "what are we working on", "morning update", or asks for a snapshot of current work. Generates a concise status report across active tasks, blockers, today’s priorities, and agent capacity.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | standup |
| description | Use when the user says "standup", "what's on today", "quick status", "what are we working on", "morning update", or asks for a snapshot of current work. Generates a concise status report across active tasks, blockers, today’s priorities, and agent capacity. |
Generate a fast status snapshot across all active work. Designed to take under 2 minutes to read.
OFFICE_OPS/reporting/daily/ — yesterday's triage log, if one existsOFFICE_OPS/projects/ — optional active project evidenceOFFICE_OPS/incidents/ — optional blocker or failure evidenceOFFICE_OPS/employees/ROSTER.md — agent utilizationIgnore .gitkeep and folder README files as operational evidence. If no logs or project evidence exist, say the standup is based on roster capacity only.
# Standup — [DATE]
## 🟢 In Progress
- [Active task or project] — [owner agent] — [expected completion]
- [Active task or project] — [owner agent] — [expected completion]
## 🔴 Blocked / Needs Decision
- [Blocked item] — blocked by: [reason] — owner: [agent or human]
## 📋 On Deck Today
- [Task to be started today] — [assigned agent]
- [Task to be started today] — [assigned agent]
## ⚠️ Watch Items
- [Anything at risk or worth monitoring — no action needed yet]
## Agent Capacity Flags
- Overloaded (>90%): [list or "none"]
- At capacity (80–90%): [list or "none"]
Keep it short. If there is nothing in a section, omit it entirely. Do not save a standup file unless the user asks.
Use when the user says "triage my calendar", "review my day", "what meetings need prep", "find calendar conflicts", "plan my schedule", or shares calendar events. Sorts meetings into prepare, attend, reschedule, delegate, and protect-focus-time actions.
Use when the user says "run daily triage", "do daily triage", "start the day", shares a mixed batch of emails/calendar/tasks, or asks to delegate today's work across Agent Office. For email-only use email-triage; for calendar-only use calendar-triage.
Use when the user says "triage these emails", "sort my inbox", "what emails need replies", "draft replies", or shares email snippets. Sorts emails into reply, delegate, archive, schedule, and needs-decision buckets without sending anything.
Use when the user says "health check", "how is the office doing", "check team capacity", "office status", "what's overloaded", asks for an office overview, or wants risks across Agent Office. Reviews utilization, projects, incidents, escalations, and coordination gaps.
Use when the user wants Agent Office to route work to the right employee, coordinate multiple employee roles, act like an office manager, or respond as a named employee. Triggers include requests to triage work, decide who should handle something, simulate the office team, delegate across roles, use the employee roster, or run the local Agent Office as an interactive office.
Use when the user says "add a new agent", "create a new role", "hire a [role]", "onboard a [role]", asks for a new employee prompt, or wants to add a role to Agent Office. Guides role definition, employee file creation, roster updates, coordination setup, and routing alignment.