polyphony-sdlc

What problem does it solve?

It solves the problem of brittle, type-specific workflow routing by providing a type-agnostic SDLC vocabulary and library of composable Conductor sub-workflows that can drive any Azure DevOps work item through plan, implement, PR, merge, and close-out.

Core Features & Use Cases

• Type-agnostic lifecycle routing: Routes purely from derived per-requirement state and EdgeGraph readiness rather than hardcoded work item type names.
• Recursive planning and parallel execution: Implements recursive planning across hierarchy levels and executes implementation in parallel through PG (processing group) batches.
• Platform-aware PR lifecycle orchestration: Chooses GitHub vs ADO PR leg workflows using an explicit interface contract and runtime metadata (e.g., tracker=ado).

Use Case: You have a heterogeneous work item tree (Epics, Issues, Bugs, and custom process types) and need one canonical orchestration workflow that consistently drives each item through SDLC without rewriting Conductor YAML when the process template changes.

Quick Start

Run the canonical SDLC entry point with your root ADO work item id by invoking conductor run polyphony@polyphony --input root_id=<ID> --web.