do-later

Files deferred changes as chained GitHub issues blocked behind current work.

Updated Jun 12, 2026
One-click install
npx skills add https://github.com/missingbulb/GoogleCalendarEventCreator --skill do-later-missingbulb
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: do-later
Source: https://github.com/missingbulb/GoogleCalendarEventCreator/tree/main/.claudinite/shared/packs/basics/skills/do-later
Command: npx skills add https://github.com/missingbulb/GoogleCalendarEventCreator --skill do-later-missingbulb

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When a change request arrives mid-session, acting on it immediately derails the work in flight, while postponing it risks the request being forgotten entirely. This Skill captures the deferred change as a well-defined GitHub issue that an automated queue picks up only after the current PR or issue closes. ## Core Features & Use Cases - Chained deferrals: Each deferred issue is blocked behind the previous deferral filed in the session, then behind the open PR or issue, so repeated asks execute in order. - Time-based waits: A Not-before: field holds issues until a specified ISO-8601 instant for requests like "check tomorrow" or "after the release". - Run parameters in the issue body: Model family, automerge policy, and task name ride the first lines of the issue body so the scheduled run executes with the right configuration. - Use Case: While reviewing a PR, the owner says "after this lands, rename the config module". You file an issue blocked behind the current PR with the rename brief, and the queue implements it once the PR merges. ## Quick Start Say "/do-later update the README badges after this PR merges" and the Skill files a blocked, labeled issue with the full brief for the queue to run later.

Frequently Asked Questions about do-later

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

FAQPage Schema
How do I defer a change request until after the current PR merges?▼

Invoke /do-later with the change description. The Skill files a GitHub issue containing a Blocked-by field pointing at the open PR, so the scheduler queue only starts the work after that PR closes.

How do chained deferrals work across multiple requests?▼

Each new /do-later issue is blocked behind the previous deferral filed in the same session, forming a chain. If no prior deferral exists, it falls back to the session's open PR, then the current issue, then queues immediately.

Can I schedule a deferred task for a specific time?▼

Yes, time-worded deferrals like "check tomorrow" use the Not-before field with an ISO-8601 instant. The scheduler holds the issue blocked and releases it on the first hourly pass after that moment.

What happens if the task:origin:ad-hoc label does not exist yet?▼

The GitHub API refuses unknown labels, so the issue is filed without it and the Skill reports this. The next scheduler run creates the label, and the owner can also apply it manually from the issue page.

When should the Automerge field be included in a deferred issue?▼

Include Automerge only when the owner stated a policy or after asking them directly with a proposed narrow policy such as under:docs && doc-changes. If they decline or want review, omit the field so the run returns for approval.