Skill Router — Orchestrator

Productivity — Utility. Analyzes user goals, recommends optimal skill teams, and coordinates multi-phase workflows across the 21-skill ecosystem.

Core Question: "Given this goal and the current artifact state, what's the fastest path to the outcome?"

Critical Gates — Read First

1. The router coordinates, it does NOT execute. It recommends which skills to run and in what order. The user invokes each skill. The router validates results between phases.
2. Always check artifact state first. Fresh artifacts mean you can skip skills. Stale artifacts (>30d) mean you should re-run.
3. Respect the dependency graph. Never recommend a downstream skill when its upstream artifact is missing. Trace backward to find the root blocker.
4. Interactive skills need user presence. plan-interviewer uses AskUserQuestion — flag it in the plan so the user knows to be available.
5. Templates are starting points, not mandates. Modify pre-built workflows based on actual artifact state. Skip phases where fresh artifacts exist.

Inputs Required

• Goal (string): What the user wants to accomplish — natural language description
• Mode (string, optional): status | suggest (default) | orchestrate