Skip to main content
subagent CX Codex

executor · ai-driven-dev — Claude Code subagent: what it does, how to install

executor turns an approved task scope into working, validated code. Useful when a spec needs implementation without planning drift or self-judging.

MIT ★ 571 updated 2026-10-29

Install into Claude Code · Plugin marketplace All methods and platforms ↓
/plugin marketplace add ai-driven-dev/framework
/plugin install aidd-dev@aidd-framework
Open on GitHub

What executor does

This subagent handles raw implementation: it decides how to build, never what to build. It internalizes acceptance criteria first. Ambiguous scope is reported back to the caller instead of guessed. The workflow stays in a tight loop: build a substep, validate, fix on red, and commit.

It relies on specific framework commands during execution: /aidd-dev:02-implement, /aidd-dev:03-assert, /aidd-dev:06-test, /aidd-dev:08-debug, and /aidd-vcs:01-commit. Commits happen per coherent unit alongside test status.

Guardrails are strict. The subagent never reviews its own output, never delegates to peer agents, and never touches specifications. If an action requires impossible human tasks like 2FA or entering a payment card, executor halts immediately without faking progress with mocks.

What it helps with

  • translate approved task specs into validated code following repository idiom
  • investigate unclear test failures using /aidd-dev:08-debug
  • record verified units directly to git via /aidd-vcs:01-commit
  • halt execution on human blockers instead of introducing placeholder mocks

Example prompts for the agent

  • Dispatch the approved API endpoint criteria to the executor subagent
  • Implement the database migration using executor strictly against the spec

How to install executor

1Plugin marketplace

/plugin marketplace add ai-driven-dev/framework
/plugin install aidd-dev@aidd-framework

2Manually: put the files in place

.claude/agents/executor.md

For all projects use ~/.claude/agents/. Claude delegates by the description field or an @-mention

Step by step, with commands for each platform: Claude Code subagents: how to create one, call it and keep context clean

Questions about executor

How to install executor in Claude Code?

First register the marketplace using /plugin marketplace add ai-driven-dev/framework, then run /plugin install aidd-dev@aidd-framework. The agent definition lives in .claude/agents/executor.md.

What does executor do?

It implements code against predefined acceptance criteria, running continuous validations and producing coherent commits. It leaves planning and code review entirely to the caller.

How does executor handle tasks requiring hardware access or 2FA?

It stops immediately and reports the blocker to the caller. The subagent refuses to fake progress through silent stubs or skipped tests.

Source text

executor.md · MIT
---
name: executor
description: Turns a dispatched task into working, validated code that fits the project. Use when an approved scope must become code. Never plans, never judges its own work.
---

# Role

You are the executor. Your job is to turn a dispatched task into working, validated code that fits the project. You decide how, never what.

# Behavior

- Honour the project's own conventions where it defines them, and match the code around you. Where it stays silent, follow the prevailing idiom.
- Internalize the acceptance criteria before writing anything. If the scope is ambiguous, surface it instead of guessing.
- Work in a tight loop: build a substep, validate it, repair on red, and only then move on. Validation passing is the gate, never your own say-so.
- When a validation failure has no clear cause, run `/aidd-dev:08-debug` before repairing and validating again.
- Commit per coherent unit, code and its status together, one unit one commit.
- When you finish or stall, return to whoever invoked you with what is done, what is left, and why.

# Guardrails

- Never author or edit a plan, spec, or acceptance criterion. That authority is the caller's. On any drift, stop and hand it back to be replanned.
- Stay strictly in the scope you are handed. Declare anything you bypass: no silent TODO, skipped test, or placeholder mock.
- Never judge your own work, and never start a review. The caller handles that.
- Never delegate to another agent.
- When the work is physically impossible for the AI, stop and say so plainly: a real payment, a human login, an unreadable secret, anything behind hardware or 2FA. Do not fake progress.

# Skills you may invoke

- `/aidd-dev:02-implement`
- `/aidd-dev:03-assert`
- `/aidd-dev:06-test`
- `/aidd-dev:08-debug`
- `/aidd-vcs:01-commit`

© AI-Driven Dev · MIT · ai-driven-dev/framework

Similar subagents

All subagents for Agent setup: memory, context, orchestration →

executor by other authors comes first.

executor Devin-AXIS executor — a subagent takes a well-defined task from an orchestrator, edits code, runs commands, and reports the result. Use it to delegate implementation work. CX Codex ★ 7,523repo stars task-executor shinpr task-executor — a subagent for Claude Code runs isolated implementation tasks from an explicit prompt or plan file. It executes the whole cycle from codebase inspection to testing without asking questions. CX Codex ★ 720repo stars gsd-executor davepoon The gsd-executor subagent carries out GSD plans task by task, commits each task separately, and updates project state. The execute-phase orchestrator starts it. CX Codex ★ 3,785repo stars om-fix-issue open-mercato om-fix-issue — a skill for Claude Code and Codex that diagnoses a tracker issue, verifies a regression test, and leaves staged changes for manual review without committing or opening a PR. CX Codex +1 502installs task-executor-frontend shinpr The task-executor-frontend Claude Code subagent carries out React implementation from a prompt or task file. It activates for frontend implementation, React work, and component creation. CX Codex ★ 720repo stars GitHub Backlog Executor microsoft The GitHub Backlog Executor subagent applies a prepared set of operations to GitHub issues and sub-issues in one confirmed repository. Use it to carry out backlog changes through GitHub. CX Codex +1 ★ 1,627repo stars GitHub github GitHub — an MCP server that gives your agent direct access to repositories, issues, pull requests, workflows and security alerts. CX Codex +1 5,908installs

From the same set80

The whole set →
02-user-stories 02-user-stories turns an epic, product brief or PRD into ordered user stories with acceptance criteria, then checks whether they are ready to build. CX Codex +1 ★ 571repo stars release-video release-video plans scenes for newly shipped features and renders an announcement video with background music and UI audio. CX Codex +1 ★ 571repo stars 01-acceptance-qa 01-acceptance-qa is a Claude Code skill that checks browser-visible behavior against acceptance criteria and records evidence videos. It verifies changes that have already been reviewed. CX Codex +1 ★ 571repo stars 08-debug 08-debug — a bug-fixing skill with three routes: reproduce a known failure and patch it with a test, chase an unknown cause through hypotheses, or reopen a stalled hunt. CX Codex +1 ★ 571repo stars 02-backlog The 02-backlog skill guides product backlog work, from sorting incoming requests to checking artifact relationships. Use it to review, order, or refine backlog items. CX Codex +1 ★ 571repo stars 01-usage 01-usage is a Claude Code skill that reports token use by period or task, split by day, model, agent or ticket, from a local aidd telemetry report. CX Codex +1 ★ 571repo stars 01-sdlc 01-sdlc orchestrates changes from contract framing to a draft pull request across Frame, Deliver, and Check zones. Use it for end-to-end tasks instead of single-step code edits. CX Codex +1 ★ 571repo stars 12-cook 12-cook is a Claude Code skill for finding and maintaining project recipes, researching techniques, and applying existing guides. It can also check recipe steps and investigate improvements. CX Codex +1 ★ 571repo stars

Project sponsors

Companies that keep this analytics open