2 min lesson
Built-in and custom subagents
Complete "Built-in and custom subagents". Check the final state against the lesson before you move on.
Check your understanding
Run this practice: Subagents — delegate the survey, keep the edit in the main thread.
Outcome: Each subagent returned one bounded deliverable, a file-and-value table and a coverage list, and the only edits in the diff are the ones I made.
Subagents — delegate the survey, keep the edit in the main thread
Built-in and custom subagents
SayTwo lanes in this retry bug: find every place backoff is configured, and check which tests already cover it. Neither needs to edit the file I'm about to fix.
DoBrief both lanes as findings-only and keep the edit in the main thread, so no two agents write the same files.
Type
List every file that sets a retry count or backoff delay for the API client. Return file, symbol, current value. Do not edit.DoSend the survey lane to a built-in research subagent.
Type
Read only these test files. Report which cases exercise retry and which paths have none. Findings only.DoSpin up a custom subagent for the test lane, scoped to the client's test folder.
SeeEach subagent runs in its own context window, so the main thread stays on the fix instead of filling with survey output.
DoRead both reports back in the main thread, write the backoff fix myself, then open the diff.
SeeEach subagent returned one bounded deliverable, a file-and-value table and a coverage list, and the only edits in the diff are the ones I made.
Learn more
Optional practice
Practice: Built-in and custom subagents
QYou've applied it. What actually proves the work is done, not just a plausible answer?