polyphony-workflow-author

Enforce polyphony validate-derived target_state routing in Conductor workflow YAML and PowerShell scripts.

Updated Apr 29, 2026
One-click install
npx skills add https://github.com/PolyphonyRequiem/polyphony --skill polyphony-workflow-author
Or copy as Structured Prompt for Agentâ–¼
Please help me install this Agent Skill.
Skill: polyphony-workflow-author
Source: https://github.com/PolyphonyRequiem/polyphony/tree/main/.github/skills/polyphony-workflow-author
Command: npx skills add https://github.com/PolyphonyRequiem/polyphony --skill polyphony-workflow-author

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill prevents workflow authors from hardcoding state names or mixing routing decisions into the wrong layer, which can cause brittle Conductor pipelines and incorrect SDLC transitions.

Core Features & Use Cases

  • State-name safety via validation: Ensures any transition uses polyphony validate to derive the correct target_state, then applies it via twig state without literals.
  • Deterministic shell-out routing contract: Standardizes workflow → PowerShell helper → polyphony/twig verb execution so routing branches on JSON fields rather than exit codes.
  • Workflow authoring guardrails: Covers min-polyphony-version metadata, version checks via preflight, and established routing patterns for tree-walking polyphony workflows and sub-workflows.
  • Operational patterns: Provides conventions for worktree isolation, evidence PR lifecycle routing, three-vocabulary rule (events/state/categories), poll-cap loops, and router/emitter patterns.

Quick Start

Update your workflow YAML by deriving target_state with polyphony validate for the event you want, then pass that derived value into twig state in the helper script output.

Frequently Asked Questions about polyphony-workflow-author

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

FAQPage Schema
How do I prevent brittle state transitions in Conductor workflows?â–¼

To prevent brittle Conductor workflows, eliminate hardcoded state names by deriving the target_state with polyphony validate, then applying that derived value via twig state without using literal strings in your YAML or helper scripts.

How do I standardize routing logic in PowerShell helper scripts for polyphony workflows?â–¼

Standardize PowerShell helper script routing by enforcing a deterministic shell-out envelope where workflow routing branches on JSON fields rather than exit codes, keeping routing decisions out of the wrong architectural layer.

Does polyphony workflow authoring require version checks before running transitions?â–¼

Yes, polyphony workflow authoring requires min-polyphony-version metadata in your workflow files and uses preflight checks to validate version compatibility before executing lifecycle transitions across process templates.

What is the three-vocabulary rule for deterministic workflow execution?â–¼

The three-vocabulary rule for deterministic execution separates events, state, and categories in your workflow logic, ensuring polyphony and twig transitions remain isolated and predictable across process templates.

Why does my SDLC workflow route to the wrong state during tree-walking?â–¼

SDLC workflows route incorrectly during tree-walking when state names are hardcoded in YAML instead of being dynamically derived via polyphony validate, causing brittle transitions and mismatched lifecycle states.