Enable Symphony

Enable Symphony

Audit a codebase and implement the Symphony pattern — continuous, automated coding agent orchestration driven by issue trackers.

Quick Start

Ask the user which mode they want:

1. Audit — Score the repo's Symphony readiness and produce a gap report
2. Implement — Generate missing files (WORKFLOW.md, hooks, agent config, CI scripts)

Reference Files

Read these as needed — do NOT load them all upfront:

File	When to read
SYMPHONY-SPEC-OVERVIEW.md	Always read first — condensed spec reference
SYMPHONY-SPEC-CONFIG-ORCHESTRATION.md	Full spec sections 1-9 (workflow, config, orchestration, workspace)
SYMPHONY-SPEC-AGENT-TRACKER-IMPL.md	Full spec sections 10-18 (agent runner, tracker, observability, security)
AUDIT-CHECKLIST.md	During audit mode — scoring rubric
CODEX-IMPLEMENTATION.md	When implementing with Codex as the agent
CLAUDE-CODE-IMPLEMENTATION.md	When implementing with Claude Code as the agent
WORKFLOW-TEMPLATE.md	When generating a starter WORKFLOW.md

Audit Mode

1. Read SYMPHONY-SPEC-OVERVIEW.md and AUDIT-CHECKLIST.md
2. Scan the repo for: WORKFLOW.md, .claude/settings.json, hooks config, CI scripts, AGENTS.md/CLAUDE.md
3. Score each dimension (0-5) per the checklist
4. Output a markdown gap report to terminal with:
   • Overall readiness score (0-100)
   • Per-dimension scores and findings
   • Prioritized recommendations

Implement Mode

1. Ask which coding agent: Codex or Claude Code
2. Ask which issue tracker: Linear, GitHub Issues, or other
3. Read the appropriate implementation guide (CODEX-IMPLEMENTATION.md or CLAUDE-CODE-IMPLEMENTATION.md)
4. Read WORKFLOW-TEMPLATE.md for the starter template
5. Generate/update these files as needed:
   • WORKFLOW.md — prompt template + front matter config
   • Agent config (.claude/settings.json for Claude Code, or codex config)
   • Workspace hooks (after_create, before_run, after_run scripts)
   • CI/orchestrator script if requested
6. Validate the generated config against the spec

Key Concepts

• Symphony is a scheduler/runner that polls an issue tracker, creates isolated workspaces per issue, and runs a coding agent session for each
• WORKFLOW.md is the in-repo contract: YAML front matter (config) + Markdown body (prompt template)
• The orchestrator owns: polling, dispatch, concurrency, retries, reconciliation, workspace lifecycle
• The coding agent owns: actual code changes, PR creation, ticket updates
• Workspace isolation is the core safety invariant

Important Rules

• Symphony is tracker-agnostic in principle; Linear is the reference implementation
• The spec is agent-agnostic; both Codex and Claude Code can fill the agent runner role
• Never generate secrets or API keys — use $VAR indirection
• Always validate workspace path containment (workspace must stay under workspace root)
• Hooks are trusted config — warn users about security implications