Menu
Queue management for user interruptions - only stop on explicit commands, otherwise add to queue and continue current task.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
After completing logical unit of work, commit with context and push. Never leave uncommitted work.
Requires handoff to review platform before deleting, archiving, or consolidating projects and repositories.
Tracks token usage in conversations, warns at 70% capacity, auto-triggers handover at 80% threshold with conversation summary and continuation prompts.
Never expose secrets in output. Use environment variables, reference .env files without reading contents aloud, recommend rotation if exposed.
Every artifact must be filed in correct location with version control. Defines filing structure and naming conventions.
Structured error handling - stop, assess, log, route, then fix or escalate. Prevents compounding problems.
| name | handle-interruptions |
| description | Queue management for user interruptions - only stop on explicit commands, otherwise add to queue and continue current task. |
User sends a new message while mid-task.
Did user say stop, cancel, abort, or wait?
User sends ideas as they come. Multiple messages = multiple ideas, NOT a stop signal. Treat rapid messages as additive input, not interruptions.
