datadog-agent

Generate the Agent Supply Chain newsletter by researching team activity on GitHub and Confluence, then creating a Confluence draft and Gmail draft

Give your AI agents something more useful than a prompt. Velocity through clarity.

Extract an Allium specification from an existing codebase. Use when the user has existing code and wants to distil behaviour into a spec, reverse engineer a specification from implementation, generate a spec from code, turn implementation into a behavioural specification, or document what a codebase does in Allium terms.

Run a structured discovery session to build an Allium specification through conversation. Use when the user wants to create a new spec from scratch, elicit or gather requirements, capture domain behaviour, specify a feature or system, define what a system should do, or is describing functionality and needs help shaping it into a specification.

Generate tests from Allium specifications. Use when the user wants to propagate tests, generate test files from a spec, write tests for a specification, create property-based tests, produce state machine tests, check test coverage against spec obligations, or understand what tests a specification requires.

Autonomously work on Jira backlog tickets, creating PRs and shepherding them to merge

Create a new Fx component using the modern def/fx/impl pattern (NOT legacy)

Add a new configuration field to the Datadog Agent (datadog.yaml)

Create a new Go core check that collects metrics and sends them to Datadog

Create a new Go module in the agent repository

Create a new Python invoke task for the dda CLI

Create a pull request for the current branch with proper labels and description

Create a reno release note for a PR or change

Create a new RuntimeSetting that can be changed at runtime via `agent config set/get` and the config API

Add a new section to the agent status output (agent status command)

Add a new CLI subcommand to an agent binary (agent, cluster-agent, etc.)

Audit CWS (runtime-security) io_uring functional-test coverage and add a functional test for any io_uring opcode whose operation CWS observes but that is not exercised through io_uring. Test-driven — coverage is judged by tests, never by reading eBPF/hook internals. Use when auditing io_uring test coverage or after new IORING_OP_ opcodes appear.

Explains a lading.yaml config file from the regression test suite, using the lading Rust source as ground truth for field meanings and defaults.

Find where an Agent config setting or section is defined in the YAML schemas, and print its schema node, using `dda inv schema.locate`

Analyze static quality gate on-disk size changes, correlate with Confluence exception records and GitHub PRs by milestone

Review and triage PR review comments on the current branch — groups threads by file, separates bots from humans, walks through unresolved comments interactively

Run E2E tests locally using the new-e2e framework with Pulumi-based infrastructure

Fetch a Jira issue and propose an implementation plan based on codebase analysis

Run Windows E2E tests (MSI install tests or Fleet Automation/installer tests) locally against AWS-provisioned VMs

Update a C/C++ third-party library under deps/ — bump version, reconcile sources/copts/config.h/patches, and verify the build.

Use when a user asks to update, bump, or troubleshoot OpenTelemetry Collector dependencies in datadog-agent, including OCB build failures, ddflareextension golden files, static quality gates, or OTel transitive dependency conflicts.

Write E2E tests for the Datadog Agent using the new-e2e framework with fakeintake assertions

Create an E2E lifecycle test for a new health platform issue in test/new-e2e/tests/agent-health/