task-router

To generate context briefs for Codex from a GSD plan, trigger the task-router skill to automatically package and route tasks from your active plan in .planning/ into structured .task-briefs/ documents for external executors.

Task routing in software engineering planning workflows is the process of classifying tasks from a GSD plan to decide between direct execution or external delegation, automatically preparing structured context briefs for external agents like Codex.

You route tasks to external model executors by applying routing logic defined in .claude/rules/model-routing.md, which classifies tasks from your active plan and generates structured handoff briefs for external execution.

Yes, you can use task-router to delegate work to external agents like VS Code-based executors by pre-generating structured context briefs from your active GSD plan, though actual review and retry governance are managed by model-routing rules.

You do not need a specific plan path to pre-generate task briefs; the skill accepts an active plan from the .planning/ directory by default, but you can also provide a specific plan path as input.

A limitation of automated task routing is that it is a packaging-only skill; it pre-routes tasks and generates briefs but delegates actual review and retry governance to the model-routing rules rather than handling execution directly.