symphony-orchestration

Orchestrate Symphony coding-agent runs with a four-phase TDD workflow.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/chenxingqiang/tdd-agent-skills --skill symphony-orchestration
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: symphony-orchestration
Source: https://github.com/chenxingqiang/tdd-agent-skills/tree/main/skills/symphony-orchestration
Command: npx skills add https://github.com/chenxingqiang/tdd-agent-skills --skill symphony-orchestration

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Symphony orchestration provides a unified lifecycle for autonomous coding runs, binding runtime agents to a production-grade TDD workflow and enforcing per-issue workspace contracts.

Core Features & Use Cases

  • Binds Symphony's lifecycle to the tdd-agent-skills four-phase protocol so all runtimes share identical behavior.
  • Manages the canonical surfaces (WORKFLOW.md, per-issue workspace, hooks) and enforces contract rules across runs.
  • Use cases include editing or validating the repo's WORKFLOW.md, spawning runs from tracker-driven tasks, and ensuring consistent handoffs across Code, Claude Code, Cursor, Copilot, Gemini CLI, Windsurf, OpenCode, Kiro, Trae.

Quick Start

Trigger a Symphony-driven run by loading the repo's WORKFLOW.md contract and letting it map issue phases to the internal skills while enforcing the ship gate.

Frequently Asked Questions about symphony-orchestration

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I enforce a consistent TDD workflow across multiple AI coding agents?

You can enforce a consistent TDD workflow across multiple AI coding agents by binding their runtimes to a unified four-phase protocol and a canonical WORKFLOW.md contract, ensuring identical behavior and strict ship-gate controls.

What is per-issue workspace isolation for autonomous coding runs?

Per-issue workspace isolation is a contract mechanism that separates file surfaces and lifecycle states for individual tracker issues, preventing cross-contamination during autonomous coding runs.

How do I orchestrate autonomous coding runs driven by tracker issues?

You orchestrate tracker-driven autonomous coding runs by loading the repo's WORKFLOW.md contract, which maps issue phases to internal skills and enforces ship-gate validation throughout the operator lifecycle.

Does Symphony orchestration work with different AI coding runtimes like Cursor and Copilot?

Yes, Symphony orchestration works with runtimes like Cursor, Copilot, Claude Code, Windsurf, and Gemini CLI by mapping their interfaces to a shared four-phase TDD protocol and enforcing consistent handoffs.

How do I validate a WORKFLOW.md contract for autonomous coding agents?

You validate a WORKFLOW.md contract by checking its runtime mapping rules, per-surface responsibilities, and strict ship-gate lifecycle controls to ensure autonomous coding agents conform to the required workflow.

What are the limitations of using a unified lifecycle for autonomous coding runs?

The unified lifecycle requires strict adherence to the WORKFLOW.md contract and standardized operator phases, meaning any runtime lacking compatible hooks or failing ship-gate validation cannot participate in the orchestration.