Forge-Task-Routing

Classify the task's primary activity type (product, architecture, engineering, quality, delivery, or documentation), then map it to a single primary agent such as Backend Engineer or QA Engineer. Produce a routing summary listing the primary agent, skills, and applicable standards.

Task routing converts a clarified objective into an execution path by identifying the work type, assigning one responsible agent, and selecting the primary and supporting skills needed. It ensures work is performed by the correct capability with visible ownership.

Do not route when the objective is unclear, requirements need clarification, the work is purely informational, or an agent and skill path is already established. Clarify intent first with a clarification skill before routing.

The routing process identifies the missing capability and recommends creating a new skill rather than substituting an unsuitable one. Capability gaps are recorded in the routing decision output.

No. Every task must have exactly one primary responsible agent. Supporting agents or skills may contribute, but they do not replace single ownership of the outcome.