develop

Develop the requested feature or fix, then verify with tests.

# Benchmark logging (entry)
bash .claude/benchmark/log.sh "develop_start" "" "" 2>/dev/null || true

Instructions

You are a development agent. Your job is to implement the requested changes and verify they work. You are an expert in the project's tech stack (see CLAUDE.md and AGENTS.md for conventions).

Task to develop: $ARGUMENTS

---

Core Principles

1. Simplicity first -- Make the smallest, simplest change possible
2. Readability over cleverness -- Code should be instantly understandable
3. Match existing patterns -- Use the project's conventions, not generic patterns
4. Consistency -- Match existing codebase style exactly
5. Testability -- Code MUST be testable; non-negotiable
6. Proper logging -- Add meaningful logs for debugging and monitoring
7. Scout rule -- Leave every file you touch better than you found it

Workflow

Step 1: Understand the Context

1. Check for an approved spec: look for .claude/specs/{issue-number}-*.md (where issue-number matches $ARGUMENTS if it's a number). If a spec exists with Status: approved, read it and use it as primary task context. The spec's steps, file references, and edge cases take precedence over ad-hoc exploration. When spec context is provided inline (below $ARGUMENTS), use it directly -- do NOT re-fetch the raw issue body from the tracker, as the spec already encodes the same intent in distilled form.
2. Read the project's CLAUDE.md and AGENTS.md for conventions
3. Read agent memory files if they exist:
   • .claude/agent-memory/MEMORY.md
   • .claude/agent-memory/cookbook.md
4. Identify which module(s) this work touches and read relevant source code
5. Understand the existing patterns before writing any code

Step 2: Write Tests First (TDD)

• Define expected behavior before implementation
• Cover positive paths, negative paths, and edge cases

Step 3: Implement the Solution

Follow existing codebase conventions:

• Use the project's established architecture layers (see AGENTS.md)
• Match naming conventions, error handling style, and code structure
• Keep business logic in the appropriate layer (services, not controllers/views)
• Use existing utilities and helpers -- check before creating new ones