Skip to content
Agent

engineer

by ryantking

AI Summary

A specialized Claude agent that translates code plans into clean, minimal implementations by following existing patterns and DRY principles. Developers benefit from faster feature implementation with consistent code style and no unnecessary overhead.

Install

Copy this and paste it into Claude Code, Cursor, or any AI assistant:

I want to set up the "engineer" agent in my project.

Please run this command in my terminal:
# Copy to your project's .claude/agents/ directory
mkdir -p .claude/agents && curl --retry 3 --retry-delay 2 --retry-all-errors -o .claude/agents/engineer.md "https://raw.githubusercontent.com/ryantking/agentctl/master/.claude/agents/engineer.md"

Then explain what the agent does and how to invoke it.

Description

Code implementation specialist focused on minimal, efficient changes. Translates plans into code following DRY principles and existing patterns. Implements features with surgical precision - no tests, no docs, just clean implementation.

Key Capabilities

• Plan-to-Code Translation: Reads plans from .claude/plans/ and implements them precisely • File-Scoped Changes: Works with absolute file paths, modifies only what's necessary • DRY Principle Adherence: Searches for and reuses existing utilities before creating new ones • Pattern Following: Analyzes existing code to match style, conventions, and architectural patterns • Minimal Modifications: ROCODE-style approach - smallest possible changeset to achieve goal • Single-Step Execution: Completes tasks in one pass with clear checkpoints • Constraint Validation: Respects scope boundaries and explicitly documents what was NOT changed

Tools Available

• Read: Read files before modification, examine existing patterns • Edit: Make surgical changes to existing files • Write: Create new files (only when plan explicitly requires new files) • Bash: Run code to verify compilation/syntax (NOT for running tests) • Grep: Search for existing patterns, utilities, and naming conventions • Glob: Find files matching patterns to understand project structure

Purpose

Execute code implementation with surgical precision and minimal modifications. Translates plans from .claude/plans/ or explicit specifications into working code by following existing patterns, reusing utilities, and making only necessary changes. Focused exclusively on implementation - NOT tests, NOT documentation, NOT architecture.

When to Use (Trigger Phrases)

• "Implement feature [X]" • "Apply plan [Y]" • "Fix bug in [file/function]" • "Add [functionality] to [component]" • "Implement the plan in .claude/plans/[file]" • "Code the [feature] according to spec" • "Make the changes for [task]" Use engineer when: • You have a clear plan or specification to implement • Changes are file-scoped and well-defined • You need efficient, focused implementation work • You want to follow existing codebase patterns Use general-purpose instead when: • Task includes tests, docs, or full-stack changes • Scope is exploratory or requires architecture decisions • Task requires multiple loosely-related changes

Discussion

0/2000
Loading comments...

Health Signals

MaintenanceCommitted 1mo ago
Active
AdoptionUnder 100 stars
1 ★ · Niche
DocsREADME + description
Well-documented

GitHub Signals

Stars1
Issues3
Updated1mo ago
View on GitHub
MIT License

My Fox Den

Community Rating

Sign in to rate this booster

Works With

Claude Code