メニュー
Use when the user says "weekly brief", "weekly summary", "wrap up the week", "how did this week go", "Friday review", or asks for a weekly status report. Synthesizes daily logs, project evidence, incidents, escalations, and utilization into an executive summary.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
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.
| name | weekly-brief |
| description | Use when the user says "weekly brief", "weekly summary", "wrap up the week", "how did this week go", "Friday review", or asks for a weekly status report. Synthesizes daily logs, project evidence, incidents, escalations, and utilization into an executive summary. |
Generate an executive summary of the week's activity across all agents, projects, and escalations.
Read in this order:
OFFICE_OPS/reporting/daily/ — this week's triage logsOFFICE_OPS/projects/ — optional active project evidenceOFFICE_OPS/incidents/ — optional open or resolved incident evidenceOFFICE_OPS/employees/ROSTER.md — current utilizationIgnore .gitkeep and folder README files as operational evidence. If no daily logs exist for this week, note that and produce a summary from available data only.
Identify:
# Weekly Brief — Week of [DATE]
## Summary
[2–3 sentence plain-English overview of the week]
## Activity by Domain
| Domain | Items Handled | Key Outcomes |
|--------|--------------|--------------|
| Sales | ... | ... |
| Marketing | ... | ... |
| Operations | ... | ... |
| [etc.] | ... | ... |
## Project Status
| Project | Status | Progress This Week | Next Step |
|---------|--------|--------------------|-----------|
| ... | 🟢/🟡/🔴 | ... | ... |
## Escalations & Decisions
- [Any items that required owner input or are still pending]
## Wins This Week
- [Notable completions, closed deals, shipped work]
## Carry-Forward
- [Open items rolling into next week with owner and deadline]
## Recommended Focus for Next Week
1. [Priority 1]
2. [Priority 2]
3. [Priority 3]
Save to OFFICE_OPS/reporting/daily/YYYY-MM-DD-weekly-brief.md using the week-ending date unless the user asks for chat-only output.