Skip to main content
Conductor is strongest when the intake path stays coherent. The goal is not to maintain one issue system for planning and another for execution. The goal is to translate incoming work into markdown tasks that fit the runtime and review loop.

​
Keep intake sane

Use GitHub issues for wider product tracking when needed, but normalize execution into the board so dispatch, session state, and review all happen in one operational flow.

​
Why this matters

If issues live in one place and execution state lives somewhere unrelated, agents and reviewers lose shared context fast.
Last modified on March 6, 2026