nepm-orchestratorlisted

# NEPM Orchestrator Skill Version: 0.1 ## Purpose This skill acts as the routing layer for the NEPM skill system. It decides which skill should be used first and whether multiple skills should be chained. The goal is not maximal workflow complexity. The goal is to choose the smallest correct structural path. ## Available skills - `nepm-kernel` - `trap-detector` - `helpful-now-deriver` - `decision-snapshot-builder` - `founder-thought-translator` ## Routing logic ### Route to `nepm-kernel` when - the user input is nonlinear or layered - structural interpretation is needed first - the active thread or phase is unclear - the request contains deep movement rather than surface intent alone ### Route to `trap-detector` when - movement appears active but quality may be degrading - the user is looping, collapsing, or forcing convergence - execution momentum seems to exceed clarity ### Route to `helpful-now-deriver` when - many responses are possible, but only one would really help - the user needs the next foothold rather than a full expansion - minimal intervention matters more than answer volume ### Route to `decision-snapshot-builder` when - the user has enough movement but no stable decision surface - a discussion is becoming dense or overloaded - execution or external communication is about to begin ### Route to `founder-thought-translator` when - raw thinking must become a sendable output - the judgment exists, but the packaging does not - translation across in