القائمة
Review what happened today, capture unanswered DMs, update daily plan with completion data, and set up tomorrow. Run at the end of each work day.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Config-driven visible plan-to-PR workflow for Workbench engineering work. Use for agent-flow, full lifecycle, visible agents, Helix-style implementation, cross-repo context, HTML plans, PR breakdowns, small or stacked PRs, reviewer packets, review from packet, Claude/Codex pairing, worktrees, Jira/PR handoffs, continuation handoffs, or approved bypass of detailed PR slicing.
Freeform ideation and structured shortlisting. Generates 8-10 approaches including wild cards, then converges on 2-4 viable options with tradeoffs. Use before /forge or standalone for any creative exploration.
Read Outlook Web calendar via Chrome and extract meeting data for capacity planning. Writes to context/active/calendar.md so other skills use real numbers.
Show remaining capacity today and this week by reading daily and weekly plans. Flags overcommitment. Use when checking if there's room for more work.
Read and critically summarize a Confluence document. Surfaces key decisions, gaps, open questions, and suggests review questions.
Create a release branch and managed _release worktree in a Workbench repo using canonical Python worktree tooling. Use when the user wants to cut a release, create a release branch, start a release process, preview the next release branch name, or keep release work out of main/develop.
| name | end-of-day |
| description | Review what happened today, capture unanswered DMs, update daily plan with completion data, and set up tomorrow. Run at the end of each work day. |
Path resolution: This skill may run from any repo. All
context/andconfig.yamlpaths are relative to the workbench root, not the current working directory. Read~/.codex/workbench-rootor~/.claude/workbench-rootto get the absolute workbench path, then prepend it to allcontext/andconfig.yamlreferences. See PATHS.md.
Review what happened today, capture what's rolling forward, and set up tomorrow for success.
The user's Slack display name is defined in config.yaml under user.slack_display_name. Slack channels are defined in config.yaml under slack.channels.
Read the daily plan at context/active/daily.md.
Review each item:
Read config.yaml to get the user's Slack display name from user.slack_display_name. Search for any DMs or @mentions of that name from today using mcp__claude_ai_Slack_MCP__slack_search_public_and_private. Flag any that still need a response — these shouldn't roll to tomorrow without being acknowledged.
Do a brief scan of high-priority channels from config.yaml: slack.channels for anything that came in late in the day. Check operations channels first (alerts, incidents), then product channels (urgent issues), then key engineering channels.
Flag anything that needs attention tomorrow.
Update the daily plan file with an "End of Day" section:
## End of Day
- **Completed**: X/Y planned items
- **Unplanned work**: [list anything that came up unexpectedly]
- **Unanswered DMs**: [any DMs that still need a response]
- **Rolling forward**:
- [ ] Item 1 (reason it didn't get done)
- [ ] Item 2
- **Blockers**: [anything blocking progress]
- **Notes for tomorrow**: [anything to remember]
Present a quick verbal summary: