google-adk-engineering-profilelisted

# Google ADK Engineering Profile Review a Google Agent Development Kit design without confusing framework support with product authority. Read [the ADK version boundaries reference](references/adk-version-boundaries.md) when identifying an API, runtime skill, evaluation, session, or deployment contract. ## Preconditions Identify the repository, language, installed ADK version, intended users, runtime environment, model provider, registered tools, session service, memory service, artifact service, and decision under review. If any version-sensitive behavior is material, verify it against the documentation for the exact installed version. ## Workflow 1. Separate the developer assistant from the product agent. A skill that helps a person build an ADK application is not automatically a safe runtime bundle for a SaaS user. 2. Inventory the agent hierarchy, models, instructions, callbacks, planners, tools, toolsets, sessions, state, memory, artifacts, retrieval, evaluation, and deployment boundaries actually present. 3. Pin the language, ADK package version, model or provider configuration, and relevant experimental features. Record observed support separately for Python, TypeScript, and Go. 4. Trace identity and authority from the product user through the host application to each agent and tool. Skill prose cannot create credentials, permissions, approvals, or a registered tool. 5. If `SkillToolset` is proposed, describe the runtime bundle, allowed content, integrity checks,