subagent-hunt-orchestration

Assign each subagent one surface family with a structured brief containing target scope, dossier summary, a success condition, and a stop condition. Default roles include surface mapper, business-logic hunter, API hunter, parser hunter, chain builder, and report synthesizer.

Use it when the target is broad, the workflow is deep, or the hypothesis tree has multiple live branches. A single linear loop wastes time on large targets where parallel surface investigation is possible.

Apply deconfliction by assigning distinct roles per surface: the mapper finds, the manual hunter reasons, the API hunter compares transports, the parser hunter stresses ingestion, and the chain builder composes. Never send two subagents after the same surface with the same goal.

Each brief needs the target scope, a current dossier summary, one surface family, one success condition, and one stop condition. For example, a parser hunter stops on one validated primitive or three disproven branches.

If returned output does not change campaign state, the brief was too vague. Merge discipline requires updating the dossier, recording disproven paths, adding chain candidates, and deciding whether to deepen, pivot, or report after each return.