Research the behavior the application needs
Twilio documentation spans communications products, channels, helper libraries, API references, security guidance, and operational limits. An agent should start from a narrow application behavior and gather only the pages that explain its requests, identifiers, callbacks, errors, and constraints.
Include the product, channel, environment, SDK or API surface, and date of the question. Ask the agent to distinguish reference requirements from tutorial examples and to preserve page links and headings. If two pages appear to disagree, report the disagreement rather than combining them into a confident rule.
Turn the answer into bounded Linear work
Twilio Docs supplies the cited technical contract. Linear supplies the change scope, owner, acceptance criteria, and remaining investigation. A combined agent can draft an issue that links every important requirement to its source and keeps unknowns visible.
Documentation research does not prove runtime behavior. The issue should name the test environment, test recipients, observability, and rollout checks needed before production use.
