polyphony-actionable

Name: polyphony-actionable
Availability: InStock
Author: polyphonyrequiem

Route Azure DevOps work items through evidence generation or human satisfaction gates.

Updated Apr 29, 2026

Search Tags:#workflow orchestration #conductor #sdlc #llm review #github pull requests #evidence routing #type-agnostic automation

Ready to run

npx skills add https://github.com/PolyphonyRequiem/polyphony --skill polyphony-actionable

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: polyphony-actionable
Source: https://github.com/PolyphonyRequiem/polyphony/tree/main/.github/skills/polyphony-actionable
Command: npx skills add https://github.com/PolyphonyRequiem/polyphony --skill polyphony-actionable

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It removes the need to manually coordinate the “actionable” SDLC facet by routing a single Azure DevOps work item through an evidence-producing polyphony leg or, when out of polyphony’s authority, through a human satisfaction gate.

Core Features & Use Cases

Actionable executor routing: Selects the correct leg via executor_router (polyphony vs human) based on the per-item executor value.
Evidence production and review: Ensures an evidence branch exists, composes the agent prompt addendum, drafts evidence PRs, checks an evidence floor mechanically, and routes to LLM review (approve/request changes/block).
Safe human satisfaction handling: Routes satisfaction outcomes to completion, loops until not_yet resolves, or allows explicit abandonment when needed.

Quick Start

Load polyphony-actionable when editing actionable.yaml or wiring any follow-up PR inputs/outputs, including any TODO(p6-prN) deferred slots.

Frequently Asked Questions about polyphony-actionable

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

FAQPage Schema

How do I automate work item routing for evidence generation in SDLC workflows?▼

Work item routing for evidence generation is automated by orchestrating the actionable SDLC facet through deterministic executor routing scripts, directing items to evidence branches, PR lifecycle checks, and LLM review gates.

What is an evidence gate in workflow orchestration for pull requests?▼

An evidence gate in workflow orchestration is a mechanical floor check ensuring evidence PRs meet standards before routing to LLM review outcomes like approve, request changes, or block on GitHub pull requests.

How do I configure executor routing between automated polyphony legs and human satisfaction gates?▼

Configure executor routing by setting the per-item executor value in actionable.yaml, using deterministic routing scripts to select the polyphony leg for evidence production or route out-of-authority items to human satisfaction gates.

Can I use deterministic routing scripts with StrictUndefined prompt wiring for type-agnostic automation?▼

Yes, deterministic routing scripts work with StrictUndefined-safe prompt and output wiring to achieve type-agnostic automation, enforcing Phase 6 deferred TODO markers and routing-style envelopes with success or error codes.

What's the best way to handle human satisfaction loops when routing actionable work items?▼

Handle human satisfaction loops by routing outcomes to completion, iterating until not_yet states resolve, or allowing explicit abandonment when the actionable work item cannot satisfy gate requirements.

Why does my actionable.yaml Conductor workflow require Phase 6 deferred TODO marker enforcement?▼

Actionable.yaml Conductor workflows require Phase 6 deferred TODO marker enforcement to ensure follow-up PR inputs and outputs properly wire deferred slots, maintaining deterministic routing and StrictUndefined safety across the evidence branch lifecycle.