| name | start-work-week |
| description | Start the work week. Life check-in, week planning, and Monday daily startup. Usually Monday morning. Runs INSTEAD of /start-workday. Use when: 'start work week', 'Monday startup', 'let's start the week'. |
| disable-model-invocation | true |
Start Work Week (Monday morning, ~15 min)
You are running the user's Monday work-week startup. This combines a life check-in, weekend catch-up, week planning, and daily startup. Take it at a measured pace โ Mondays set the tone.
Step 1: Daily note setup
Read today's daily note. daily:read creates it from the configured template if it doesn't already exist โ do NOT call obsidian create for the daily note.
obsidian daily:read vault="{{VAULT_NAME}}"
Read Friday's and weekend daily notes for continuity. Add a ## Week Ahead section dynamically to today's note (Monday-only โ not in the template).
Step 2: Morning check-in
Same 3 prompts โ ## Morning State. Update energy and mood frontmatter.
- "How are you feeling right now?"
- "What feels most alive for you right now?"
- "What would make today feel good?"
Step 3: Weekend catch-up
Ask: "What did you get done over the weekend?"
This catches accomplishments from personal days, especially if /end-personal-day wasn't run. Cross-reference with weekend daily notes (Log, Reflection sections, ## Today's Options, ## Done Today).
Advance the system:
- Mark completed project actions, move to
## Completed sections.
- Update project context where relevant.
- Add any new follow-up actions surfaced.
- If nothing project-related happened, skip gracefully โ weekends don't need to be productive.
Step 4: Week Ahead check-in
4 Monday-specific life check-in questions. Write responses to ## Week Ahead in today's note:
- "How am I feeling right now?" (deeper โ about overall life state, not just this moment)
- "What feels most alive for me right now?"
- "Where am I feeling the most friction going into this week?"
- "What can I do to make it a good week?"
Pattern weather: Before the check-in questions, scan last week's daily note Observations sections for any shadow patterns that were noted. If a pattern appeared across multiple days, share briefly: "Last week I noticed [pattern] showing up around [domain] โ worth keeping an eye on, or has something shifted?" This is conversational context, not excavation. If no patterns were noted, skip silently.
Step 5: Calendar scan โ full week
Read Mon-Fri events using mcp__apple-events__calendar_events. Identify:
- Meeting-heavy days vs. deep-work days
- Prep needs for upcoming events
- Personal commitments during work hours
- Schedule conflicts to flag
Summarize the week's shape.
Also read the next 60 days of calendar events (startDate: next Monday, endDate: today + 60 days) and Apple Reminders (mcp__apple-events__reminders_tasks, incomplete with due dates). These feed the ## Upcoming horizon overview in Step 11. The full week scan above is for conversational context (meeting-heavy days, deep work blocks). ## Upcoming captures only critical items across two months.
Step 6: Rule of 3 recap
Surface the weekly outcomes from Friday's deep-review (if available โ check Friday's daily note or recent notes for Rule of 3). Ask: "Still feel right, or want to adjust?"
Step 7: Day-specific routines
Read [[Day-Specific Routines]]. Filter for Monday + ## Daily. Present applicable items. These will be converted to checkboxes and written to ## Routines in today's daily note during Step 11.
Step 8: Inbox overview
Gather counts from all three inboxes:
- Drafts inbox:
mcp__drafts__drafts_inbox โ count items
- Obsidian inbox:
obsidian search query="path:Inbox/" vault="{{VAULT_NAME}}" โ count results
- Unread email:
mcp__mail__get_emails (unread, limit 1) โ get unread count
Report: "X Drafts, Y inbox notes, Z unread emails. Full processing happens during deep review."
Workbench: Count files in Workbench/ (obsidian search query="path:Workbench/" vault="{{VAULT_NAME}}"). Report: "X workbench items active" (add "Y ready to graduate" if any have status: ready). Information-only โ no processing.
Do NOT process inboxes here โ the relevance pass happens in Step 11 after choices are confirmed.
Step 9: Build action menu
Same as start-workday but with week-level awareness. Consider:
- Which Rule of 3 outcomes need action today?
- Front-load important work early in the week
- Monday energy (may be lower โ adjust accordingly)
- ~5-8 options grouped by area, weighted by enjoyable usefulness
Include stance awareness checks (grounded in shadow-awareness rule โ Tier 1 only):
- Lots of planning, little execution โ "What's the very next physical action?"
- Grinding through tasks, ignoring meaningful work โ Surface something important and enjoyable
- Paralysis or "nothing matters" โ Offer one small, concrete, useful thing
- Refining options instead of choosing โ "These are good enough โ which one first?"
One observation max. Check off-switch criteria before surfacing.
Step 10: Carried forward from Friday
Check Friday's daily note ## Today's Options for undone items (still - [ ], not in ## Done Today). Ask: "Still relevant?"
Step 11: Write daily note dashboard + Intentions
Write the daily-note dashboard per the shared write-spec in .claude/shared/daily-startup-dashboard.md, with these parameters:
- Today's Options โ groups Work / Personal / Quick; the items confirmed in Step 9; 5-8 options weighted by week-level awareness (Rule of 3 outcomes, front-loaded priorities).
- Routines โ Monday + Daily items from Step 7.
- Upcoming โ all critical items; sources are the Step 5 60-day scan and milestones spotted in Step 9. (Full week shape was presented conversationally in Step 5; this is the two-month critical-items overview, not today's schedule.)
- Intentions โ informed by the Week Ahead responses (Step 4) and Rule of 3 (Step 6).
- Inbox relevance pass โ include unread email.
Step 12: Yesterday's observations
Write to Sunday's (or Friday's) daily note if it exists without ## Observations. Include defense pattern tracking at Tier 2 if applicable โ same protocol as start-workday Step 10 (observation + capacity evidence; note contradictions for the Defense Pattern Living Record).
Step 13: Summary
Present:
- Week overview (calendar shape, Rule of 3 outcomes)
- Today's plan (action menu, calendar)
- Any follow-ups or attention items
Commit all vault changes.
