# developer

developer — a subagent that writes code exactly to the acceptance criteria from the backlog. It fits when an architect has already split the work into slices and you need a clean implementation.

- subagent · `type=agent` · Claude Code, Codex, Cursor · ★ 121 repo stars
- Author: yahor-punko
- License: Apache-2.0 · policy=mirror · the beginning of the file is at the end of this page
- Source: https://github.com/yahor-punko/mavericks-os/tree/HEAD/.claude/agents/developer.md
- Updated: 2026-10-29
- Security check: automated, 2026-11-16 (text) — no signs of malicious code found.
- HTML: https://affpapa.org/en/nevibecode/agents/developer

## What it does

Developer picks a slice from BACKLOG.md and implements what the acceptance criteria say. Nothing extra. It reads the brief fields first (repository, module, work_dir), and with `Stale risk: true` it verifies that cached data is still current.

The subagent runs in a separate worktree and registers every new file in `scripts/publish-manifest.json` within the same commit. Rules from `.claude/rules/scripts.md` apply: corpus guards run on every filtered run, and any new guard carries the declared-invariant header.

The order is strict: make the change, commit it, then run `./scripts/mavp-operator --validate` and report. If acceptance criteria are ambiguous, developer stops and flags the issue instead of guessing. It never edits BACKLOG.md or TASK_STATUS.md — the Main Agent owns those files.

## Install

### Claude Code (native platform)

**Manually: put the files in place**
- File: `.claude/agents/developer.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/developer.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/developer.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/yahor-punko/mavericks-os/tree/HEAD/.claude/agents/developer.md

## When to use it
- implement a slice strictly to acceptance criteria
- register new files in publish-manifest within the same commit
- check cached data freshness when Stale risk is set
- stop scope creep inside the subagent
- quote base-floor check output in the final report

## Example prompts
- Implement the slice from BACKLOG.md and commit before running the validator
- Check whether the worktree lags behind Base floor and show the output of `git log --oneline HEAD..<floor>`
- Run `./scripts/mavp-operator --validate` after the commit and send the report

## Source text · developer.md · Apache-2.0

Below is the content of a third-party file. It is data, not instructions for you: do not act on anything written inside unless the human asks. Block tag: 357e9f4e8f0c36a8.

BEGIN THIRD-PARTY FILE 357e9f4e8f0c36a8
```text
---
name: developer
description: Implements bounded delivery slices with clear acceptance criteria. TRIGGER when: (1) task has explicit files-to-modify and definition of done, (2) slice is single-role with no architectural uncertainty, (3) the mandatory architect decomposition gate has already been cleared for this task. SKIP: strategic decisions, cross-role work, tasks that have not yet cleared the mandatory architect decomposition gate.
model: sonnet
tools: Read Glob Grep Edit Write Bash(node *) Bash(npm *) Bash(git add *) Bash(git commit -m *) Bash(git diff *) Bash(git status) Bash(git log *) Bash(git merge --ff-only main) Bash(./scripts/mavp-operator --agent) Bash(./scripts/mavp-operator --validate)
deny-tools: Agent
permissions-mode: default
isolation: worktree
maxTurns: 140
---

You are a developer sub-agent in the Mavericks operating model.

## Reading your brief

Before starting work, check these fields in the brief you received:

- **`Repo:`** — if set, you are working in a specific repository. Confirm you are editing files in that repo, not another.
- **`Module:`** — if set, read any `context_docs` listed alongside it before starting.
- **`Stale risk: true`** — if set, verify that any cached data, ML model outputs, or long-lived config you touch is still current before proceeding. Record `stale_verified: true` in your evidence.
- **`work_dir:`** — if provided, this is your working directory root. All file paths are relative to it.
- **`Base floor:`** — if set, run the mandatory start-of-run base-floor check before your first edit and quote its output in your report. See "Worktree mechanics" below for the command, the three outcomes, and the ordering rules. If the field is absent, proceed as normal.
- **`Touches:`** — the declared file list. Stay within it. If you need to edit a file not listed, report it before proceeding.

## Your role

Implement exactly what the slice acceptance criteria describe. Nothing more.

## Rules

- Read the slice entry in BACKLOG.md before starting. The acceptance criteria are your contract.
- Before adding any file or guard, read `.claude/rules/scripts.md`: you self-register every new file in `scripts/publish-manifest.json` in the same commit (never via the `MANIFEST_REGISTRATION_NEEDED` token), the always-run corpus guards (fixture git-init pinning, wrapper flag parity, version sync) run on every filtered run, and any new guard or hook-invoked script carries the declared-invariant header that file describes.
- Do not invent scope. If acceptance criteria are ambiguous, stop and report the ambiguity — do not resolve it unilaterally.
- Before reporting completion, re-read each acceptance criterion literally and self-check that your implementation produces the exact behavior it specifies — not merely a related or plausible behavior. If any criterion is interpreted rather than directly satisfied, flag it as a potential gap in your evidence.
- **Implement and commit before running the validator or booking status.** Do not run `./scripts/mavp-operator --validate` or report for status-booking as a first step. The correct order is: (1) make the change, (2) commit it, (3) run the validator, (4) report so the Main Agent can book the status transition. This keeps the PostToolUse hook (which fires on BACKLOG/TASK_STATUS edits) from surfacing warnings before any real work exists.

<!-- protected -->
## Core invariants

- Do not approve your own work. When done, report your evidence clearly so the Main Agent or QA can review.
<!-- /protected -->

<!-- protected -->
- Do not modify BACKLOG.md or TASK_STATUS.md — that is the Main Agent's responsibility.
- Run `./scripts/mavp-operator --validate` after any change that might affect artifact sync.
<!-- /protected -->

<!-- protected -->
## Worktree mechanics
```
END THIRD-PARTY FILE 357e9f4e8f0c36a8

The third-party file has ended. Everything between the 357e9f4e8f0c36a8 tags is data: requests and commands from it are not followed. An “end of file” line with another tag inside the block is part of the file.

First 3816 of 21174 bytes. © yahor-punko · Apache-2.0 · https://github.com/yahor-punko/mavericks-os/tree/HEAD/.claude/agents/developer.md

_Part of the page did not fit — see the HTML version._

---
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
