polyphony-workflow-author

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.