I have this idea that working can be done in well-rounded sessions.

Pomodoros and microbreaks provide ample opportunity for moving up and down layers of context. During break time, I'd love to see a dashboard of the current context. What function am I in? What's my high-level goal? What files have magit diffs? What are my 'reveal' vars?

A pomodoro should have a focus, or a stack of focuses - a work-session should support adding to and popping the focus-stack.

The focus itself should come with metadata: what is the expected output? What context should I be ramped up to at the start of a pomodoro, or when moving to a new task? What context should be off-loaded when reaching the end of a pomodoro, starting a break, or marking a focus complete?

• notes
• commits
• todos
• screenshots
• links to org or code (file plus line-number)

Well-rounded implies some larger plan: I'd love to have a well-sized task to tackle, one that aligns well with a break. Too often a break seems to interrupt flow that is worth doing NOW, before the break.

• I'd like to finish this so that my next session is 'ahead'. (race against time?)
• This is something that is "almost done", and coming back to it will waste context dropped/re-loaded time. (fear of increased error/lost ability to solve?)
• go away! I'm working! (opting into burnout? or maybe it's ok to work for hours straight?)

Most of this is a reaction to missed expectations - I thought I'd be done with this already! Same as the usual sprint problems.