factory-orchestrator
factory-orchestrator
What this skill does
factory-orchestrator is the front door of the software factory. It accepts work at any stage of the lifecycle, detects which stage the work is in, and hands it to the factory skill that owns that stage. It is a pure router and communicator: it never implements, reviews, triages, or deploys itself — every stage's work belongs to the skill that owns it (factory-queue, factory-mission, factory-review, factory-deploy, factory-learn, …).
It is the single communicator with the user: acknowledgements, status, questions, and hand-offs all flow through it, in one voice, with the factory's internal dispatching kept out of sight.
It keeps work in motion until it is actually closed: nothing else in the factory completes work, so an item the orchestrator never closes stays open forever.
When to use
- A request arrives and it is not obvious which factory skill owns it, or it bundles several things (a PR problem + a new feature request + a question).
- Work arrives mid-lifecycle: a CI failure on a delivered PR, review findings to address, a merge notification, a reply to a question a factory run asked earlier.
- You want one place that knows the full stage map and the human gates, instead of reconstructing the pipeline from skill descriptions.