Immutable. This exact content is served forever at /api/v1/blob/ab3771bdfd08ba5f.
# AGENTS.md: Codex CLI entry point This repo is **Symphony**, a polling orchestrator that dispatches coding agents (Codex / Claude Code / Gemini / AGY / Kiro / OpenCode / Pi) at a Kanban board. This file is the discovery point that Codex (and any other `AGENTS.md`-respecting CLI) reads on startup. It gives the operator, meaning the human or agent running `symphony`, the same skill guidance Claude Code gets from `.claude/skills/`. ## Source of truth: `skills/symphony-skill` Operator-side routing lives in one skill: `skills/symphony-skill/SKILL.md`. It has YAML frontmatter (`name`, `description`, optional triggers) and routes requests to the right reference or support bundle. `.claude/skills/` is a thin symlink layer for Claude Code's native discovery. Do not edit through it. Edit the canonical files under `skills/`. `skills/symphony-skill/oneshot/` and `skills/symphony-skill/monorepo/` are branch-specific subfolders with templates, scripts, and references used by the router. They intentionally do not expose separate `SKILL.md` activation routes. ## Available skill (operator-facing) Load `skills/symphony-skill/SKILL.md` when the user's request matches the trigger description below. Open only the reference page named by the router's decision table. ### `symphony-skill` > Use when the user wants to dispatch coding agents (Codex / Claude Code / > Gemini / AGY / Kiro / OpenCode / Pi) against a Kanban board via this `oh-my-symphony` repo > — adding/listing/transitioning tickets, launching the TUI, inspecting > orchestrator state, customizing the workflow (lanes, per-state prompts), > delegating sub-tasks to free up context, one-shotting a prompt into an > evidence-gated board, bootstrapping a monorepo workflow, or diagnosing > dispatch failures. > Triggers on phrases like "add a symphony task", "run symphony", "dispatch > this ticket", "symphony board", "WORKFLOW.md", "symphony tui won't start", > "ticket failed with worker_exit", "customize kanban states", "deploy > pipeline workflow", "delegate to symphony", "agent.kind: pi", "agent > silent for N seconds", "one-shot this", "decompose and dispatch with proof", > or "symphony monorepo". Entry: `skills/symphony-skill/SKILL.md` ## Worker-side guidance Dispatched workers (the agent CLI running inside a per-ticket workspace) do **not** consume these operator skills. Worker behavior is driven by `WORKFLOW.md`'s `prompts.base` + `prompts.stages` map, which renders stage prompts from `docs/symphony-prompts/<flavor>/`. That layer is already cross-platform. Codex, Claude, Gemini, and Pi workers all receive the same rendered prompt for a given ticket state. ## Conventions for this repo - Read `WORKFLOW.md` and a couple of `kanban/*.md` files before any recommendation. Settings vary per fork. - Run `symphony doctor ./WORKFLOW.md` before launching anything. - See the `BOOTSTRAP` route in `skills/symphony-skill/SKILL.md` for the full file set required when copying Symphony into another project.