← ClaudeAtlas

session-budgetlisted

Agree a plan for the rest of the usage limit window with the user. Use when the [continuum] Stop hook reports the window crossed the threshold, or when the user asks "how much budget is left", "what do we do about the limit", "we're about to run out".
TropinAlexey/continuum · ★ 1 · Data & Documents · score 72
Install: claude install-skill TropinAlexey/continuum
# Plan for the rest of the limit window ## 1. Get the facts The hook that woke you already put the numbers in its message. Use those; do not spend a tool call re-fetching. If the user asked cold, without a hook firing: ``` continuum status ``` Prints utilization and reset time for every window the provider reports. The exact reset time for the scheduler is `continuum reset` (format `HH:MM`). If `continuum` is not on `PATH`, it ships with this plugin under `bin/` — see the README's install section. Do not go hunting for the path. ## 2. State where we stopped One or two sentences: what is done, what remains, whether there are uncommitted changes. A resumed session — or the user tomorrow — has none of your context. Write for them. ## 3. Ask the user via AskUserQuestion Ask in the language the user has been speaking, not necessarily English — translate the question and every option label accordingly. Question: "The window is N% used, resets at HH:MM. What do we do?" Offer 3-4 options that fit the moment, recommended one first: | Option | What I do | |---|---| | **Finish and wrap up** | Bring the current task to a working state, run the tests, show the diff. No new work. | | **Finish the task set, then stop** | Complete the remaining planned tasks (the current TODO batch), then stop — no new scope. Offer this only when what's left is a bounded, known set that plausibly fits the remaining window; skip it if the work is open-ended. | | **Save state and schedule a resume**