Dispatch queue pattern for tracking pending tasks across sessions. Use when managing task continuity, understanding pending work, or implementing the /continue workflow.
/plugin marketplace add nethercore-systems/nethercore-ai-plugins/plugin install ai-game-studio@nethercore-ai-pluginsThis skill inherits all available tools. When active, it can use any tool Claude has access to.
The dispatch queue (.studio/dispatch-queue.md) tracks pending tasks for session continuity.
# Dispatch Queue
## Pending Tasks (Priority Order)
### 1. [Task Name]
- **Agent:** [fully-qualified agent name]
- **Context:** [what needs to be done and why]
- **Blocked by:** [dependencies, or "None"]
- **Added:** [when queued]
## Completed This Session
- [x] [Task] → [result/artifact]
## Notes
[Context for next session]
Add tasks:
Remove/Complete:
Agent: Use fully-qualified names: zx-procgen:asset-generator
Context: Include enough to resume: what exists, what's needed, file paths
Blocked by: None, #2, [dependency], or User decision needed
/ai-game-studio:continue reads and dispatches from queuenext-step-suggester checks queue firstrequest-dispatcher updates queue before stoppingcompletion-auditor adds remediation tasks# Dispatch Queue
## Pending Tasks (Priority Order)
No pending tasks.
## Notes
Run project-health-monitor to identify potential work.
This skill should be used when the user asks to "create a slash command", "add a command", "write a custom command", "define command arguments", "use command frontmatter", "organize commands", "create command with file references", "interactive command", "use AskUserQuestion in command", or needs guidance on slash command structure, YAML frontmatter fields, dynamic arguments, bash execution in commands, user interaction patterns, or command development best practices for Claude Code.
This skill should be used when the user asks to "create an agent", "add an agent", "write a subagent", "agent frontmatter", "when to use description", "agent examples", "agent tools", "agent colors", "autonomous agent", or needs guidance on agent structure, system prompts, triggering conditions, or agent development best practices for Claude Code plugins.
This skill should be used when the user asks to "create a hook", "add a PreToolUse/PostToolUse/Stop hook", "validate tool use", "implement prompt-based hooks", "use ${CLAUDE_PLUGIN_ROOT}", "set up event-driven automation", "block dangerous commands", or mentions hook events (PreToolUse, PostToolUse, Stop, SubagentStop, SessionStart, SessionEnd, UserPromptSubmit, PreCompact, Notification). Provides comprehensive guidance for creating and implementing Claude Code plugin hooks with focus on advanced prompt-based hooks API.