using-research

To route ambiguous research requests, the skill evaluates the query against references/children.json and directs it to the single narrowest applicable child skill for execution. It enforces a single-child routing policy to ensure consistent handoffs.

Use a research routing workflow when a request is research-heavy and could map to investment, market-framework, or broad-synthesis workflows but lacks clarity. It determines if a specific sub-skill is required or if no narrow routing is needed.

No, you cannot route research queries to multiple child skills in parallel. The skill enforces a single-child routing policy, selecting exactly one primary child skill or deciding that no specific research skill is needed.

If the best-fit child skill for your research is missing, the routing workflow prompts you to install it. It checks references/children.json for boundaries and prompts installation when necessary to avoid execution failures.

The routing workflow prefers domain-specific artifacts first and uses references/children.json as the source of truth for boundaries. It selects the narrowest applicable child skill, such as investment-research, market-research, or research-assistant.

Yes, the research router supports broad-synthesis and market-framework workflows. It evaluates ambiguous research requests that could map to these workflows and routes them to the single most appropriate, narrowly scoped child skill.