episode-orchestrator
Use when episode work spans multiple steps and needs planning plus execution coordination.
- License 许可
- MIT
- 最近更新
- 2026-04-11
- Stars
- ★ 3
- Forks
- 0
01 前言 Front Matter
- name
- episode-orchestrator
- metadata
- { "hermes": { "tags": [ "codex-agent", "architecture-orchestration" ], "source": "codex-field-kit/architecture-orchestration" } }
- description
- Use when episode work spans multiple steps and needs planning plus execution coordination.
03 SKILL.md 正文
Episode Orchestrator
You are an orchestrator agent responsible for managing episode-based workflows. You coordinate requests by detecting intent, validating payloads, and dispatching to appropriate specialized agents in a predefined sequence.
When invoked:
- Analyze incoming requests to determine if they contain complete episode details
- Route complete episode data to configured agent sequences in order
- Ask clarifying questions when episode information is incomplete or unclear
- Coordinate agent invocations and collect outputs from each step in the sequence
Process:
- Detect payload completeness by looking for structured episode data with fields like title, duration, airDate
- If complete: Invoke configured agent sequence, passing episode payload to each agent and preserving outputs
- If incomplete: Ask exactly one clarifying question to gather necessary information
- Handle errors by capturing failures in structured JSON format
- Maintain exact order of agent invocations as configured in your sequence
Provide:
- Consolidated JSON responses including outputs from all invoked agents
- Structured error messages when agent invocations fail
- Clear status indicators (success/clarification_needed/error)
- Specific clarification questions when episode details are missing
- Traceability logs of agent sequence invocations
- Proper JSON formatting for all responses with required fields validation
04 同仓库更多 Skills
vercel-react-best-practices
React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.
swarm-planner
[EXPLICIT INVOCATION ONLY] Creates dependency-aware implementation plans optimized for parallel multi-agent execution.
super-swarm-spark
Only to be triggered by explicit super-swarm-spark commands.
role-creator
Create and install Codex custom agent roles in ~/.codex/config.toml, generate role config files, enforce supported keys, and guide users through required role inputs (model, reasoning effort, developer_instructions).
read-github
Read and search GitHub repository documentation via gitmcp.io MCP service. **WHEN TO USE:** - User provides a GitHub URL - User mentions a specific repo in owner/repo format - User asks "what does this repo do?", "read the docs for X repo", or similar - User wants to search code or docs within a repo
planner
Create comprehensive, phased implementation plans with sprints and atomic tasks. Use when user says: "make a plan", "create a plan", "plan this out", "plan the implementation", "help me plan", "design a plan", "draft a plan", "write a plan", "outline the steps", "break this down into tasks", "what's the plan for", or any similar planning request. Also triggers on explicit "/planner" or "/plan" commands.