issue-dispatcher

GitHub issue triage is automated by reading issue bodies, labels, and context to classify work into specific categories. It then routes issues to the correct development flow, reducing manual decision-making and speeding up project initiation.

Automated issue classification reads issue content and context to categorize work as GENESIS, MULTI-COMPONENT, or SINGLE-COMPONENT. It uses these classifications to initiate a feature-roadmap, push back, or start a component flow accordingly.

The best way to handle ambiguous GitHub issues during triage is to flag them and request clarifications before routing. This ensures the issue has sufficient context to determine the correct downstream development path.

Yes, you can use GitHub issue labels and acceptance criteria to route issues. The process preserves issue URLs, labels, and discussion context, passing them to downstream agents for consistent handoffs and workflow initiation.

You need to initiate a feature-roadmap when an issue spans major refactors or multiple components. Conversely, a single-component flow is triggered for isolated single-feature work based on the issue's classified scope.

No, you do not need to manually prepare starting context. The routing process uses issue content and context to surface a recommended route and automatically prepare starting context for downstream skills.