メニュー
Generate today's daily plan via the daily-plan signal, then surface session-entry items (unprocessed transcripts, intake, due signals). Run first thing in a session, or when context shifts mid-day. Updates state/signals.json after writing.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | daily-ops |
| description | Generate today's daily plan via the daily-plan signal, then surface session-entry items (unprocessed transcripts, intake, due signals). Run first thing in a session, or when context shifts mid-day. Updates state/signals.json after writing. |
Daily operating cycle. Reads session-entry state, runs the daily-plan signal, surfaces what needs attention right now.
/daily-ops — full cycle: read state, generate daily plan, surface inbox/daily-ops --plan-only — generate daily plan, skip surfacing/daily-ops --refresh — regenerate daily plan even if today's already existsRead config/state/session-entry.md. Note the counts:
Follow config/signals/daily-plan.md:
config/operator-profile.md (email + daily-plan: block) — see the signal's ## Configuration table. Defaults: scope own, lookahead 7, lookback 7, email-label empty (skip). All of the below substitute these values.calendar-scope (default own = {email} only, shared calendars excluded), today + next {lookahead} days: gws calendar +agenda --today --calendar {email} and gws calendar +agenda --days {lookahead} --calendar {email}{lookback} days of personal/daily/, today weighted most (read-only){action-email-label} Gmail label if set (default empty → skip): gws gmail users messages list --params '{"userId":"me","q":"label:{label}","maxResults":25}' then fetch each id's metadata headers_status.md across all three locations: gtd/projects/, atlas/clients/*/projects/, atlas/businesses/*/projects/gtd/actions/next/ and gtd/actions/waiting/_status + recent meetingstoday - last-touched > 1.5 × expected-cadencegtd/actions/waiting/ item, check whether it's unblocked or needs a nudge## Reasoning — focus & GTD triage.operator-profile.role and operator-profile.work-mode. If first-30-days-mode: active, lean toward setup-oriented framing; otherwise neutral. If either field is empty (early state), default to neutral.Write to intel/briefings/daily/{YYYY-MM-DD}-daily-plan.md with the signal frontmatter:
---
type: signal
shape: briefing
date: 2026-04-26
sources: ["..."]
schedule: daily
---
Body sections per the declaration:
Print to chat (after the file is written):
/process-transcripts?")After successful write:
config/state/signals.json → daily-plan.last-fired = todayIf write fails, do NOT update state. /workdesk-doctor trusts output files over state.
Daily-plan also cleans up expired inbox items as a side effect:
[AWARENESS] older than 7 days → archive to gtd/inbox/_archive/{YYYY-MM}/[QUESTION] older than 14 days → archive[REVIEW] and [ACTION] never expire — operator clears.
[REVIEW] per session). Batch beyond that.personal/. Read today's daily note; never modify it.Process unprocessed transcripts in system/intake/ into atlas/meetings, atlas/decisions, atlas/people updates, and gtd/inbox proposals. Uses Gemini 3.1 Flash Lite as the structured extractor (~$0.002/transcript, 4s latency) and Claude for vault integration (wikilink resolution, matching cross-updates, file ops, verification). Operator-confirmed per transcript. Honors matching, action-item ownership, source-documentation, and the source-processing-pattern intake → process → archive flow.
Pull raw verbatim transcripts from Granola (meetings, notes, phone calls), Google Meet standalone Transcript Docs, AND the verbatim Transcript tab inside "Notes by Gemini" Docs — into system/intake/ via three ETL scripts. Pure script orchestration — no AI synthesis, no tokens spent on extraction. Idempotent (skips already-pulled). Default lookback 7 days; flags for 14d / backfill / dry-run / status / single-source. Use when the operator says "get transcripts", "pull transcripts", "grab the last N days of transcripts", or before /process-transcripts.
Unpack complex work or a dense topic one idea at a time, checking comprehension at each step rather than delivering a wall of text. Use when the operator asks to "unpack", be "caught up", or "walked through" something — and offer it proactively before any recap, plan, or explanation long enough to overwhelm in a single message.
Owner-only release management for WorkDesk OS at BenaliHQ/workdesk-os. Pre-merge gate, release cut via scripts/release.sh, post-release smoke test against a pinned canary vault, and rollback. Use ANY time work is being landed into the workdesk-os repo or a release is being cut — downstream operators receive these changes via /update. Trigger phrases — "add this to workdesk", "get this into workdesk", "merge this to workdesk", "ship this to workdesk", "land this in workdesk", "cut a workdesk release", "release workdesk os", "tag a workdesk release", "smoke the workdesk release", "rollback the workdesk release". Also auto-trigger when working in /Users/khalilbenali/code/workdesk-os and the operator says anything about merging, shipping, releasing, or landing changes. Owner-only — not for downstream operators.
Safely start, resume, inspect, and finish isolated repo work when the operator says "work on <repo>", "start working on", "pick up <task>", "parallel session", "is anyone else working on", or "hand this off / I'm done with this task".
Plan, organize, and pressure-test multi-step projects with the GTD Natural Planning Model. A skill family: `/pobo` (guided plan), `/pobo organize` (restructure a brief/brainstorm into clean phases), `/pobo review` (adversarially pressure-test a plan). Use `/pobo --lite` for fast low-stakes planning.