Budget continue
One command to set up a complete AI-powered development workflow with Claude Code. Persistent memory, session management, 35+ CLI tools.
npx -y skills add Enakoneschniy/claude-dev-stack --skill budget-continueAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 5 stars5 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Show 4-option continuation prompt when session budget is low. Options: remind later (CronCreate), auto-continue locally (Desktop task), auto-continue in cloud (Cloud task), continue now. Trigger when: budget warning fires, session limit reached, context is full, user sees budget warning.
SKILL.md
3.0 KB, as published. Nobody here has run it
Budget Continue Skill
When the session budget warning fires, this skill presents a 4-option continuation menu and (when invoked inside a Claude Code session) can schedule the appropriate follow-up action using native Claude Code tools.
Invocation
claude-dev-stack budget continue
Or invoke this skill directly: /budget-continue
The 4 Options
Option 1: Remind me later (CronCreate)
Creates a one-shot CronCreate reminder that fires in the current Claude Code session after a delay.
When the user selects this option inside a Claude Code session:
Use CronCreate to schedule a reminder:
Title: "Resume GSD session — budget warning"
Prompt: "/budget-continue"
Schedule: "+1h" (or user-chosen delay)
Repeat: false
Option 2: Auto-continue locally (Desktop task)
Creates a Desktop task that fires on the local machine after a delay and runs the GSD resume workflow.
When the user selects this option inside a Claude Code session:
Use the Desktop task tool:
Prompt: "/gsd-resume-work"
Schedule: "+1h" (or user-chosen delay)
Note: The machine must be on when the task fires. STATE.md is read to determine what to resume.
Option 3: Auto-continue in cloud (Cloud task)
Creates a Cloud task that runs on Anthropic infrastructure. Performs a fresh git clone and runs the GSD resume workflow autonomously — works even when the local machine is off.
When the user selects this option inside a Claude Code session:
Use the Cloud task tool:
Repo: (git remote origin URL — auto-detected)
Prompt: "/gsd-resume-work"
Schedule: "+1h" (or user-chosen delay)
Note: All state must be committed to git. GSD guarantees this via STATE.md.
Option 4: Continue now
No scheduling action. Prints a message to continue with the current session. Useful if the user decides to keep working and address the budget limit later.
What the scheduled task runs
Both Desktop and Cloud tasks run /gsd-resume-work, which reads .planning/STATE.md:
- If
stopped_atis present: resumes from that point usingresume_fileas context - If no stopped work: runs maintenance tasks (check PRs,
/gsd-next,/gsd-health)
The loop.md template (if installed to .claude/loop.md) provides the full maintenance loop instructions for scheduled tasks.
Notes
- Hooks cannot interactively invoke Claude Code tools — hence the CLI command for manual invocation.
- When invoked as a skill inside a Claude Code session, scheduling tools (CronCreate, Desktop, Cloud) are directly available.
- The budget warning message includes:
Run: claude-dev-stack budget continueas a reminder.