pmo-skill-router

To route PMO role requests automatically, use the pmo-skill-router to classify incoming requests against trigger surfaces defined in the core/skills/registry.md file, directing them to the correct role-specialist. This eliminates manual intervention and reduces operational overhead.

Role classification in PMO operations is the process of matching incoming requests to predefined trigger surfaces in a skill catalog registry. It determines the correct role-specialist route by utilizing optional metadata hints like module, tier altitude, and methodology.

You narrow down candidate routes for a PMO request by providing optional metadata hints. The router utilizes module, tier altitude, and methodology hints to refine the classification against trigger surfaces and narrow the candidate set for accurate routing.

Yes, you can see the decision-making process because the router provides a confidence signal on every route. This confidence signal ensures the operator is aware of how the request was classified and routed based on the registry trigger surfaces.

Yes, you need a skill catalog because the router operates within the PMO domain and requires knowledge of the registry.md file. Request classification depends on matching requests against the trigger surfaces defined in this core skill registry.

PMO request routing fails without registry trigger surfaces because the router relies on these defined surfaces to classify incoming requests. Without the core/skills/registry.md file, the system cannot determine the correct role-specialist or provide a routing confidence signal.