gsd:resume-at

Schedules a future Claude Code session to resume GSD project work at a specified time.

3.4k|487|Updated Jul 25, 2025
One-click install
npx skills add https://github.com/davepoon/buildwithclaude --skill gsd-resume-at
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gsd:resume-at
Source: https://github.com/davepoon/buildwithclaude/tree/main/plugins/gsd/skills/resume-at
Command: npx skills add https://github.com/davepoon/buildwithclaude --skill gsd-resume-at

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

When you hit a usage cap, pause for the day, or want work to kick off overnight, there is no built-in way to tell Claude Code to come back later. This Skill schedules a future session that automatically resumes your GSD project at the requested time, so HANDOFF state is restored without manual restarts.

Core Features & Use Cases

  • Flexible Time Parsing: Accepts HH:MM clock times, ISO 8601 timestamps, and relative durations like +2h or +30m, with past times rejected explicitly.
  • Custom Resume Commands: Defaults to /gsd:resume-work but supports --cmd overrides such as /gsd:execute-phase 9 or /gsd:next for targeted resumption.
  • Token-Free Fallback: Provides a pure shell wrapper (gsd-resume-at) using nohup sleep for scheduling when you have hit a rate limit and cannot spend tokens.
  • Use Case: You are approaching your quota at 5 PM. Run /gsd:resume-at +3h to schedule a session that resumes work at 8 PM during off-peak quota hours, with HANDOFF.json restored automatically.

Quick Start

Ask Claude to schedule a resume of the current project by running /gsd:resume-at with a time like 09:00 or +2h, optionally adding --cmd to pick which command fires.

Frequently Asked Questions about gsd:resume-at

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I schedule Claude Code to resume work later?

Run /gsd:resume-at with a target time such as 09:00, +2h, or an ISO 8601 timestamp. The skill schedules a future session via Claude Code's /schedule or CronCreate primitive, defaulting to /gsd:resume-work which restores HANDOFF.json state.

How to schedule a Claude session after hitting a rate limit?

Exit the rate-limited session with /exit, then run the gsd-resume-at shell wrapper from a plain terminal, for example gsd-resume-at +3h. It uses nohup sleep for an OS-level timer and consumes no Claude tokens, though it is macOS-only and does not survive reboots.

Can I schedule a specific command instead of the default resume?

Yes, pass --cmd with any command, such as /gsd:resume-at 04:00 --cmd "/gsd:execute-phase 9". The skill schedules whatever command you provide without restricting it to GSD commands.

Does the scheduled resume survive a system reboot?

Scheduling through the skill itself uses Claude Code's /schedule or CronCreate, which persists across restarts. The shell fallback wrapper uses nohup sleep and does not survive a reboot, so use the skill when tokens are available for durable scheduling.

What happens if I schedule a time that has already passed?

For HH:MM input, a passed time rolls to the same time tomorrow. For absolute timestamps already in the past, the skill reports an error with the parsed value and asks for a new time rather than silently rounding up.