←Story detail

Trending story

Thomas Delteil published an article explaining the taxonomy of Amazon Quick agent primitives

1 reports1 story updatesUpdated Nov 7 01:34

Understand this story

AI overview

On November 7, 2026, Thomas Delteil published an article explaining the taxonomy of Amazon Quick agent primitives. This taxonomy breaks down agent work using four questions—When, What, Who, and How—corresponding to three layers: triggers, agents, and capabilities. Among these, triggers are divided into four categories: human-initiated, agent-delegated, scheduled, and event-driven; agents are defined as persistent learning executors composed of instructions, capabilities, and acquired context, with the underlying LLM being merely a replaceable parameter; capabilities encompass tools, skills, and workflows, with skills loaded via progressive disclosure and workflows fixing step order in code. Currently, this article has been published by AWS Machine Learning, and there have been no subsequent developments.

AI-generated from public reports

Latest development · Report

Amazon Quick Agent Primitive Taxonomy

Developments

1 confirmed developments

  1. Thomas Delteil published an article explaining the Amazon Quick agent primitive taxonomy

    Source:AWS Machine Learning

Reports and discussion timeline

Browse reports and discussion by time. Their evidence levels remain distinct.

Nov 7

  1. AWS Machine LearningFirst-party

    Amazon Quick Agent Primitive Taxonomy

    The Amazon Quick team proposed a taxonomy of agent primitives that breaks down agent work using four questions—When, What, Who, and How—corresponding to three layers: triggers, agents, and capabilities. Triggers fall into four categories: human-initiated, agent-delegated, scheduled, and event-driven. An agent is defined as a persistent, learning executor composed of instructions, capabilities, and acquired context, with the underlying LLM serving merely as a replaceable parameter. Capabilities encompass tools, skills, and workflows; skills are loaded via progressive disclosure, and workflows fix step order in code.

Related stories

  1. Related storiesThe AWS team built a serverless MCP server on ECS Fargate
  2. Related storiesU Mobile built AiDaH based on Amazon Bedrock AgentCore
  3. Related storiesAWS introduces enterprise-grade Agentic AI platform blueprint based on AgentCore
  4. Related storiesMoEngage uses AgentCore Gateway to turn private APIs into Agent tools