skill-router
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
- 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.
- Always check artifact state first. Fresh artifacts mean you can skip skills. Stale artifacts (>30d) mean you should re-run.
- Respect the dependency graph. Never recommend a downstream skill when its upstream artifact is missing. Trace backward to find the root blocker.
- Interactive skills need user presence.
plan-intervieweruses AskUserQuestion — flag it in the plan so the user knows to be available. - 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
Output
More from hungv47/prod-skills
plan-interviewer
Interviews the user to clarify a vague idea into a concrete spec — asks probing questions, identifies gaps, and produces a structured PRD. Produces `.agents/spec.md`. Not for breaking an existing spec into tasks (use task-breakdown) or designing technical architecture (use system-architecture).
10code-cleanup
Audits and refactors existing code for readability, maintainability, and dead code removal without changing behavior. Produces `.agents/cleanup-report.md` and applies fixes in-place. Not for diagnosing business problems (use problem-analysis) or writing documentation (use technical-writer).
8technical-writer
Generates documentation from a codebase — READMEs, API references, setup guides, runbooks, and architecture docs with consistent structure and terminology. Produces documentation files in the project. Not for specifying what to build (use plan-interviewer) or restructuring code (use code-cleanup).
8system-architecture
Designs technical blueprints — tech stack selection, database schema, API design, file structure, and deployment plan for a defined product or feature. Produces `.agents/system-architecture.md`. Not for unclear requirements (use plan-interviewer) or task decomposition (use task-breakdown).
8task-breakdown
Decomposes a spec or architecture into buildable tasks with acceptance criteria, dependencies, and implementation order for AI agents or engineers. Produces `.agents/tasks.md`. Not for clarifying unclear requirements (use plan-interviewer) or designing architecture (use system-architecture).
7artifact-status
Scan .agents/ — report what exists, what's stale, and the critical path to your next goal. Run at session start or when deciding what to do next.
1