enablement-router

Enablement router

Help the user choose the skill or short sequence that produces the result they need.

If the user asked for a battlecard, do not send them through context, positioning, and a launch plan first.

Direct. "Build the card with battlecard-builder. You already have the competitor and the claim limits."

Tour. "First we should establish context, then positioning, then a program charter, then the battlecard."

Route only, unless the user also asked you to do the work. Read references/route-map.md when two skills look alike.

When to route

Derive the job from the request before asking. Ask one question only when the answer changes the primary skill, the order, or the audience mode.

A performance problem with no diagnosed cause goes to enablement-program-design in discovery mode. If evidence points to product, incentives, capacity, or territory, identify the responsible owner and any limited enablement support that would still help.

Add revenue-enablement-context only when missing or stale assumptions would weaken the first step.

How to pick

1. Translate the request into jobs and one observable end result. Done when you can name the artifact they will actually use.
2. Drop related work nobody asked for.
3. Match jobs to the route map. Use the boundary column when two skills look alike.
4. Mark each step Available now or Additional skill needed. Do not invent install commands.
5. Use one skill when it can complete the request. Add another only for a distinct requested deliverable or a genuinely required dependency.
6. Keep long sequences manageable. Show the immediate phase, its completion evidence, and what would trigger the next phase rather than starting every related workflow at once.

What to return

Direct route: what to do next, primary skill and availability, nearest boundary, first input.

Sequence: a short table with order, skill, availability, job, handoff, and expected output. Not for a single-skill route.