pragman-routerlisted

# Pragman Router Shape only as much as the route requires, then select capabilities—not brands—from the user's installed and approved skill ecosystem. Adaptive behavior is the default. ## Use this skill when - You need to decide whether a request should be answered directly, shaped, researched, prototyped, or executed. - Work crosses skills/providers or includes meaningful writes, egress, cost, privacy, credentials, or reversibility concerns. - You want a compact task contract and disclosed fallback instead of blind provider selection. ## Acceleration payoff It prevents over-planning simple work and under-scoping risky work by selecting the lightest trustworthy route and preserving approval boundaries. ## Workflow 1. Honor explicit instructions about provider, method, speed, risk, side effects, and exclusions. Resolve personal context plus the selected workspace/project; personal-only and unlinked work are valid. 2. If the request is obvious, bounded, read-only, low-risk, and complete, take the Fast lane without an interview. Otherwise identify only missing fields that could change lane, capability, approval, egress, or task boundary; ask one focused question at a time. For an ambiguous Deep request, establish the desired outcome and required capabilities before naming, evaluating, recommending, or invoking any provider or brand. 3. Build the normalized route input described in [references/routing-contract.md](references/routing-contract.md). Derive effective sensitivi