A couple things that help me when I hit this exact wall: shrink the surface area and make the loop tiny. Pick one ridiculously small, end‑to‑end deliverable (e.g., “add X toggle with a minimal UI, ship a changelog”) and set a 15‑minute “opening ritual” where the only goal is to open the editor and write a stub or one failing test. Energy often follows action, not the other way around. If solo inertia is heavy, swap in co‑working or lightweight pairing; or open a small, well‑scoped issue to invite contributions so you’re reviewing instead of starting cold.

Also worth reframing: is this a business or a craft project? If it’s not pulling its weight commercially, put it in maintenance mode with a clear cadence and let yourself step away guilt‑free for a month. Sunlight, movement, new inputs—your brain will reset its reward signals. When you come back, protect the fun: fewer plans, more shipping, tighter feedback loops.