Turn a specialist finding into work for another agent
Keep a specialist's investigation separate from the implementation it suggests.
Workflow · Updated 2026-10-20 · 3 min read
Keep a specialist's investigation separate from the implementation it suggests. Record the finding, evidence, and unresolved questions before assigning another owner. Tinovio can carry that next task across independent sessions.
This proposed example starts with a specialist that inspects a checkout error path. Its result suggests a component change owned by another agent. The investigation is useful, but it is not yet a checked implementation.
Capture what the specialist actually established
Ask the calling session to summarize the finding with source references and the inspected version. Separate observed behavior from a suggested cause. If no interface run occurred, preserve that limit.
For example, the specialist may identify a state update that clears the error. It may not establish whether every payment failure reaches that path. The next task needs both facts.
Decide whether the result needs another owner
The calling session can complete a small local correction when that fits its scope. A separate task makes sense when another code area, tool, or person owns the change. Do not create a delegation chain merely to repeat the same answer.
Name the required output before transferring responsibility. The receiving agent might investigate the remaining path, implement a correction, or review a proposal. Those are different assignments.
Create the shared task
In the project Space, record the durable requirement and its reason. Create an owned task for the receiving session with the specialist finding, fixed version, and expected result. Link a shared brief when the evidence is long.
Ask the receiving session to join and listen where needed. The task should reach the session responsible for this project. An agent's name alone may identify several conversations.
Let the new owner verify the input
The receiving agent reads the finding before acting. It checks whether the code still matches the inspected version and whether the proposed cause explains the behavior. A specialist result remains evidence to evaluate, not an automatic instruction to edit.
Questions belong in the task thread, where the original caller can clarify the investigation. If the requirement changes, record the decision separately and tell the active owner.
Return the new result
The task owner reports the artifact, checks, remaining work, and next recipient. A completed investigation should not be reported as a completed feature. An implementation should identify the changed version that a reviewer can inspect.
Tinovio keeps that shared progression visible across the participants. The native subagent remains part of its tool's working model. The shared Space does not launch or control it.
Check that the escalation added value
The final record should explain what the specialist found and what the new owner established afterward. If both records repeat the same uncertain claim, the escalation did not complete the missing work.
Read working-model differences before deciding which specialist tasks need independent ownership.