Start-of-session and end-of-session rituals. Use at the beginning or end of any game dev work session. Bridges adhd-coach energy patterns with sprint-manager tickets. Collapses the gap between sitting down and building.
The hardest part is the first 60 seconds. Make those automatic.
Invariant A ritual is valuable because it's automatic. You don't decide to do it — you just do it. The ritual removes the "what should I do?" gap that ADHD exploits.
Example Sit down. Read breadcrumb. Check energy. Pick ticket. State goal. Start. — This sequence takes 90 seconds and eliminates 30 minutes of drift. //BOUNDARY: If the ritual itself becomes a source of friction (too many steps, takes too long), simplify it. Two steps is better than five steps you skip.
Depth
When you sit down to work:
Check the last breadcrumb. It tells you: what you were doing, what's next, where to look.
If there's no breadcrumb: scan the last 3 git commits and your Plane board. Pick the most obvious thing.
Returning after a gap (3+ days away from this project): spend 5 extra minutes. Read the last few commit messages, scan open tickets, re-read the project README. You're rebuilding context, not starting from scratch — the breadcrumbs from your last session and the codebase itself will bring you back faster than you expect.
How do you feel right now? Be honest.
| Level | Feels Like | |-------|------------| | High | Alert, focused, ideas flowing. Want to build. | | Medium | Functional but not sharp. Could work but not create. | | Low | Tired, foggy, distracted. Here but barely. | | None | Shouldn't be here. Go rest. (See: The Break in adhd-coach) |
Match ticket to energy:
| Energy | Pick a ticket that is... | |--------|--------------------------| | High | High-energy, core to the game. S or M sized. | | Medium | Medium complexity. Bug fixes, feature polish, learning. | | Low | Low-energy. Chores, ticket updates, file organization. |
If nothing matches: either the sprint needs rebalancing (talk to sprint-manager) or today is a Break day (talk to adhd-coach).
If there's no sprint (first session, or you've been learning all week): pick one small, concrete thing you can finish today. Create an ad-hoc ticket if needed. Don't let the absence of a formal sprint stop you from building.
Say it out loud or type it: "This session, I'm going to [one specific thing]."
Not: "Work on the game." Not: "Make progress." Yes: "Get the player to jump and land with correct gravity." Yes: "Complete chapter 2 of the GDScript course and build a practice scene."
Open the relevant file. Read the first line. Make one change. Momentum follows.
If it doesn't: the task is wrong. Check adhd-coach's TwoMinuteStart boundary — is the task too big, too vague, or too boring?
When you're done (by choice, by energy, or by time):
git add [files] && git commit -m "WIP: [what you did]"
WIP commits are fine. Lost work is not. Commit even if it's broken.
Three things:
Store breadcrumbs where you'll find them: a BREADCRUMBS.md in the project root, a pinned Plane comment, or the last commit message.
Move the Plane ticket to reflect current state:
From adhd-coach's session-patterns, matched to this ritual:
| Shape | Energy | Duration | Start Ritual Emphasis | |-------|--------|----------|-----------------------| | Sprint | High | 1-4 hours | Set direction firmly. Protect the session. | | Wander | Medium | 1-2 hours | Loose goal is fine. "Explore [area]." | | Tidy | Low | 30-60 min | Pick low-energy tickets. Don't force creativity. | | Break | None | 0 | Skip the ritual. Go rest. |
When a session starts:
When a session ends:
The whole ritual should take under 2 minutes. If you're spending longer, you're over-planning. The session-planner's job is to get the user building, not to plan what they build (sprint-manager does that).
adhd-coach skill — Energy patterns, session shapes, breadcrumbssprint-manager skill — Ticket selection and sprint contextscope-guardian skill — Am I working on what matters?Sit down. Read breadcrumb. Check energy. Pick ticket. State goal. Start.
Google Workspace CLI for Gmail, Calendar, Drive, Contacts, Sheets, and Docs.
Manage Apple Notes via the `memo` CLI on macOS (create, view, edit, delete, search, move, and export notes). Use when a user asks OpenClaw to add a note, list notes, search notes, or manage note folders.
Work with Obsidian vaults (plain Markdown notes) and automate via obsidian-cli.
Use when you need to control Slack from OpenClaw via the slack tool, including reacting to messages or pinning/unpinning items in Slack channels or DMs.
Manage Apple Reminders via remindctl CLI (list, add, edit, complete, delete). Supports lists, date filters, and JSON/plain output.
Manage Trello boards, lists, and cards via the Trello REST API.
Category:productivity