qq-weekend-burn

The value: A Claude subscription resets its quota every week whether you used it or not, that part everyone already knows. What doesn’t happen on its own is someone actually sitting down and driving a long autonomous session by hand, every single Saturday, forever. qq-weekend-burn turns “put the unused quota to work” from a thing you keep meaning to get around to into a standing decision you make exactly once.

The benefit: Install it and walk away. It fires itself inside a recurring window you choose (Friday evening through Sunday night, say), works one real capability at a time to an actual finished state, and stands down the moment you’re back at the keyboard. You come back Monday to shipped things, not a pile of half-touched projects and a wasted week of quota.

The features:

• A recurring calendar schedule that fires itself, every week, with no re-invocation: install once
• A finish-discipline doctrine: one project worked to a real terminal state before the next starts, so a long unattended run ships finished things instead of a dozen started ones
• An intake standard: a fuzzy backlog item is never dropped; it’s tagged needs-definition and gets your single most capable model for exactly one job (writing a clear definition of done), then drops straight back to normal cheap-model execution
• A kill switch where the word you write decides the failure mode: PAUSE self-heals after a TTL, STOP holds until you clear it, anything else gets flagged loudly instead of silently obeyed
• Built on ww-keepalive (also in this repo) for the actual session-survival mechanism: the fresh-process-per-fire trick that means a 5-hour cap, a closed laptop, or a reboot never stops the schedule. You don’t invoke ww-keepalive yourself; /qq-weekend-burn does it for you.

Commands

/qq-weekend-burn   — stand up a new weekend-burn lane: write the governing doc, seed the
                      backlog, wire the recurring window function, and hand you the
                      one-paste install block for the actual schedule

How to invoke it

Deterministic, not a phrase Claude has to guess at: run /qq-weekend-burn. Claude scaffolds every file the schedule needs (the governing doc, the backlog, the window function, the state) and hands you a one-paste block to install the actual recurring trigger yourself. That last step is always yours: the platform’s safety classifier blocks an agent installing its own unattended loop, on purpose.

Key principles

• Sequence, not a cap: a productive burn finishes many things, just one at a time
• “The code ran” is not done; done is the observable finish line, verified
• A human-gated step doesn’t block the run: stage it, mark it, move to the next project
• Unused quota at reset is wasted, not saved

Part of Operator Skills, a collection of skills for running a real Claude Code setup.