One-click install
npx skills add https://github.com/PolyphonyRequiem/polyphony --skill conductor-design
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: conductor-design
Source: https://github.com/PolyphonyRequiem/polyphony/tree/main/.github/skills/conductor-design
Command: npx skills add https://github.com/PolyphonyRequiem/polyphony --skill conductor-design

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It prevents conductor SDLC workflows from becoming inconsistent, non-reentrant, or overly agent-driven by enforcing non-negotiable design principles for state, routing, and human interaction.

Core Features & Use Cases

  • Non-negotiable workflow constraints that require explicit exceptions when violated, keeping SDLC routing deterministic and maintainable.
  • Clear decision boundaries between design vs runtime, work item state vs plans, and deterministic scripts vs judgment-oriented agents.
  • Resumable-by-state re-entry guidance that prioritizes observable artifacts (work item state, branches, merged PRs) over replaying history.
  • Human gate quality rules that define when gates belong, how to structure them, and how to make them human-readable with links.
  • Safety and reliability invariants that require preconditions, postconditions, and loop invariants to be explicitly documented.

Quick Start

When designing or reviewing a conductor SDLC workflow YAML, load this skill and apply its P1–P14 principles to every node and transition to ensure re-entry correctness and gate usage discipline.

Frequently Asked Questions about conductor-design

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

FAQPage Schema
How do I design SDLC workflow YAML for deterministic routing and safe re-entry?

Enforce P1–P14 constraints around work-item source of truth, plan-as-context separation, and state-based re-entry to keep SDLC workflows deterministic and resumable.

What are SDLC workflow invariants and why do they matter for agent prompt guidance?

SDLC workflow invariants are explicitly documented preconditions, postconditions, and loop invariants that prevent workflows from becoming non-reentrant or overly agent-driven by defining clear decision boundaries.

How do I structure human gates in a conductor workflow YAML?

Structure human gates in conductor workflow YAML by applying gate quality rules that define when gates belong, how to make them human-readable with links, and how to separate deterministic scripts from judgment-oriented agents.

Does conductor-design work with type-agnostic routing for state discovery?

conductor-design supports type-agnostic structure by enforcing explicit intent handling and type-agnostic routing without relying on plumbing-level output schema changes for state discovery and re-entry.

When should I not use agent-driven logic in SDLC workflow design?

Avoid agent-driven logic when it violates non-negotiable workflow constraints, requiring explicit exceptions to maintain deterministic routing, observable work item state, and safe re-entry over replaying history.

Best way to ensure state re-entry correctness in SDLC workflows?

Ensure state re-entry correctness by prioritizing observable artifacts like work item state, branches, and merged PRs over replaying history, guided by resumable-by-state re-entry principles.