conductor-design

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.