This skill should be used when the user asks about "project status", "where did we leave off", "what's next", "continue development", "resume project", or when an orchestrator needs to persist or restore project state. Provides the format for tracking game development progress across sessions.
/plugin marketplace add nethercore-systems/nethercore-ai-plugins/plugin install zx-orchestrator@nethercore-ai-pluginsThis skill inherits all available tools. When active, it can use any tool Claude has access to.
Track progress in .studio/project-status.md for session continuity.
# Project Status: [Game Title]
## Current Phase
[Design | Assets | Implementation | Publish] ([X]% complete)
## Summary
[One sentence: current focus]
## Completed
- [x] [Task] → [artifact path]
## In Progress
- [ ] [Task] ([current step])
## Next Steps
1. [Next]
2. [Following]
## Blockers
- [Blocker] | [Resolution]
## Session Log
| Date | Agent | Action | Result |
|------|-------|--------|--------|
Session Start:
.studio/project-status.mdDuring Work: Update after completing tasks or hitting blockers.
Before Stopping: Update In Progress, Next Steps, add to Session Log.
| Phase | % | Activities |
|---|---|---|
| Creative Foundation | 0-10 | Vision, sonic identity |
| Design | 10-25 | GDD, constraints, asset specs |
| Visual Assets | 25-45 | Textures, meshes, characters |
| Audio Assets | 45-55 | Music, SFX |
| Implementation | 55-80 | Code, integration |
| Testing | 80-90 | Sync tests, optimization |
| Publish | 90-100 | Marketing, ROM, upload |
| After | Agents |
|---|---|
| Creative | creative-director |
| Design | design-reviewer, accessibility-auditor |
| Visual | art-director, asset-quality-reviewer |
| Audio | sound-director |
| Code | tech-director, rollback-reviewer |
| Pre-Publish | release-validator |
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.