# fullstack_implementation_engineer

The fullstack_implementation_engineer Claude Code subagent turns an approved feature spec into a coordinated implementation plan. It covers data, APIs, business logic, UI, migrations, and tests.

- subagent · `type=agent` · Claude Code, Codex, Cursor · ★ 776 repo stars
- Author: AgenticOrgLab
- License: not stated · policy=link-only · description only; the file stays with the author
- Source: https://github.com/AgenticOrgLab/ExecOrchestra/tree/HEAD/execorchestra/Pool/resources/agents/fullstack_implementation_engineer.md
- Updated: 2026-11-12
- Security check: automated, 2026-11-17 (text) — no signs of malicious code found.
- HTML: https://affpapa.org/en/nevibecode/agents/fullstack-implementation-engineer

## What it does

The subagent builds an implementation package from an approved feature request. It lays out assumptions, affected layers, and the order of dependencies, then proposes file-level edits, interface changes, sample patches, and data migrations.

The package also covers error handling, security, backward compatibility, rollback, and a test matrix linked to acceptance criteria. Existing architecture and conventions remain in place unless the request permits a change. Repository details must come from supplied context, and claims that builds, migrations, or tests succeeded need evidence.

## Install

### Claude Code (native platform)

**Manually: put the files in place**
- File: `.claude/agents/fullstack_implementation_engineer.md` — For all projects use ~/.claude/agents/. Claude delegates by the description field or an @-mention

### Codex

**Manually: put the files in place**
- File: `.codex/agents/fullstack_implementation_engineer.toml` — Codex defines subagents in TOML: name, description, developer_instructions. Move the Markdown text into developer_instructions by hand. For all projects use ~/.codex/agents/

### Cursor

**Manually: put the files in place**
- File: `.cursor/agents/fullstack_implementation_engineer.md` — Cursor also reads .claude/agents/

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/AgenticOrgLab/ExecOrchestra/tree/HEAD/execorchestra/Pool/resources/agents/fullstack_implementation_engineer.md

## When to use it
- break an approved feature into changes across application layers
- map file edits to acceptance criteria
- plan data migrations and dependency order
- outline security, compatibility, and rollback checks

## Example prompts
- Create an implementation package from this approved feature spec and its acceptance criteria.
- Map the API, UI, and data-schema changes, then connect tests to the acceptance criteria.
- Draft a migration and rollback plan using the repository tree and source files.

## Similar
- [fullstack-engineer](https://affpapa.org/en/nevibecode/agents/fullstack-engineer.md) — subagent · ★ 267 repo stars
- [fullstack-developer](https://affpapa.org/en/nevibecode/agents/fullstack-developer.md) — subagent · 18117 installs
- [agent-fullstack-developer](https://affpapa.org/en/nevibecode/skills/agent-fullstack-developer.md) — skill · 155 installs
- [fullstack-guardian](https://affpapa.org/en/nevibecode/skills/fullstack-guardian.md) — skill · 6100 installs
- [dev-workflows-fullstack](https://affpapa.org/en/nevibecode/plugins/dev-workflows-fullstack.md) — plugin · ★ 720 repo stars
- [fullstack-dev](https://affpapa.org/en/nevibecode/skills/fullstack-dev.md) — skill · 3500 installs

From the same set: [agenticorglab/execorchestra](https://affpapa.org/en/nevibecode/by/agenticorglab/execorchestra.md) — 24 cards

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md
