Step 1 — Learn the decision criteria

Read references/source-selection.md for its decision tree — the signals (data origin, update frequency, data volume) that map onto each destination family. Don't select a source yet; this is only so Step 2's inspection knows which points to spot and highlight.

Step 2 — Inspect

Spawn inspect (see Subagent protocol). It finds the GridControl/TreeListControl/View target (or reports none exists), classifies the three signals per references/code-inspection.md, and returns a files-of-interest list.

Skip delegation only when no sub-agent/subtask dispatch tool exists at all, or the target and signals are already known from earlier in this conversation — then inspect inline using references/code-inspection.md yourself. This fallback is scoped to this step only — it never extends to Steps 5/6 (see there).

Step 3 — Ask only what's unresolved

Ask about any signal inspect left unresolved — one question at a time via a structured tool if available (AskUserQuestion, Copilot's askQuestions), inline chat otherwise. State what was inferred from code first. If the developer already stated a signal in their request, treat it as known — never re-ask it.

Step 4 may not begin until every signal is resolved — answered by the developer, or already known from code/request. An unresolved signal (Data Volume most often, since references/code-inspection.md treats it as ask-only by default) is a hard stop here, not a value to carry forward and default. Mentioning the assumption to the developer after generating code is not a substitute for asking before — if you catch yourself about to write "I'm assuming X rows" instead of asking, that is this step being skipped; go back and ask instead.

Step 4 — Select the source

Apply source-selection.md's decision tree (read in Step 1) to map (origin, frequency, volume) onto a destination family and its pinned doc URL(s). Every input to the tree must already be a resolved value from Step 2/3 — never feed it an unresolved signal (see the tree's own note on this).

Step 5 — Fetch the facts

Spawn doc-fetch with urls = the family's pinned URL(s) from step 4. It returns namespaces, API symbols, one code example, limitations, and a Gaps field — never write code from memory instead of this step.