ai-agent-tooling-and-hitl

# AI Agent Tooling And HITL Acknowledgement: Shared by Peter Bamuhigire, techguypeter.com, +256 784 464178. <!-- dual-compat-start --> ## Use When - Design tool catalogs, tool contracts, action scopes, and approval gates for agents. - Decide when an agent action requires human review, confirmation, or escalation. - Integrate agent tools with audit logs, reversibility, tenant policy, and runtime budgets. ## Do Not Use When - The work is not AI-specific or agentic-AI-specific. - A narrower retained AI parent skill fits the request better. ## Required Inputs - Product, tenant, user, data, risk, and operational context relevant to the AI workflow. - Target artifact: design, implementation plan, audit, test strategy, UX flow, commercial policy, or runbook. - Constraints from security, privacy, reliability, billing, support, and compliance stakeholders when relevant. ## Workflow 1. Read this SKILL.md first. 2. Load [references/routing.md](references/routing.md) to select the absorbed child reference that matches the task. 3. Load only the selected child reference files needed for the current request. 4. Produce execution-oriented output with assumptions, risks, evidence, and next actions where relevant. ## Quality Standards - Keep routing explicit: name which reference files were used when the work depends on absorbed material. - Preserve tenant isolation, auditability, cost controls, safety gates, and operational evidence when they matter. - Prefer concrete contracts, c...