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.