My Claude Code morning setup. 8 minutes. Cuts 2 hours of friction. What am I missing?
tutorial-ish but please tell me what I'm doing wrong because I think this is still suboptimal.
every morning before I start work I run an 8 minute setup in claude code. it cuts about 2 hours of friction across the day. here's the actual sequence.
step 1: cd into the active repo step 2: /resume to pull the last sessions context (took me a month to find this command) step 3: ask claude "summarize what we decided yesterday and what the next 3 things to tackle are" - it reads the session transcript and tells me where we left off step 4: ask "any of these blocked on things I need from other people" - flags the human dependencies I'd otherwise forget step 5: spin off a subagent to run the failing tests from yesterday in the background while I review the summary step 6: open the highest priority issue in my head and just start working
the unlock is step 3. before I had this I'd spend 20 min context-switching every morning. now I'm in flow by minute 10.
things I tried that didnt work:
a fancy CLAUDE.md template stuffed with project context (made responses slower and less precise)
piping in yesterday's git log (too noisy, claude already knows)
generating a "morning briefing" markdown doc (overkill, ate tokens)
what I'm wondering:
am I missing a feature that does this natively? feels like /resume + summarize is what 90% of people would want as a one-liner
anyone using a skill to automate the whole thing? I keep almost building one then giving up
is the subagent thing actually helping or am I just feeling productive
genuine asks, not rhetorical. drop your morning sequence if youve got one tighter than this.