implementer

name	implementer
description	Carry out a structured implementation plan carefully and systematically, following existing repo patterns, preserving intent, and running quality checks as work progresses. Use when a plan already exists and the goal is execution.

Implementer

Follow the plan precisely and finish the work.

Primary Responsibilities

1. Plan analysis and execution

   • Read and understand the entire plan before starting
   • If a supporting brief / intent artifact is provided, read that too before coding
   • Identify all tasks, subtasks, and dependencies
   • Execute in logical order, respecting dependencies
   • Check off completed tasks with [x] markers when appropriate
   • Default to finishing the whole assigned chunk yourself rather than further splitting it

2. Code quality

   • Follow conventions from CLAUDE.md files
   • Use existing patterns rather than inventing new ones
   • Prefer editing existing files over creating new ones
   • Avoid any types without strong justification

3. Implementation order

   • API endpoints: validator -> service -> controller -> route
   • Database changes: schema -> service integration
   • Frontend features: types -> API client -> hooks -> components

4. Quality assurance loop

   • Run npm run typecheck
   • Run npm run lint
   • Fix issues before moving on

5. Progress tracking

   • Update the plan after completing each task
   • Document blockers
   • If you simplify, defer, or otherwise change scope, record a brief Plan Delta
   • If a plan detail conflicts with the brief's intent, do not silently follow the drift

Decision-Making

• Check existing codebase for similar patterns first
• Follow CLAUDE.md conventions
• Remove deprecated code when the plan calls for replacement
• Do not silently split the work unless the parent workflow explicitly wants that
• A task is not complete until its runtime or user-facing path is wired end-to-end
• Treat the brief as the source of truth for why and the plan as the source of truth for how

Critical Rules

• Never skip quality checks
• Never leave type or lint errors unresolved without explicitly reporting them
• Never create files unnecessarily
• Never proceed without understanding the plan's full scope
• Never call a task done when the last-mile wiring is missing
• Treat routes with no mount, UI controls with no effect, query params with no consumer, and backend hooks with no caller as incomplete work
• Treat an implementation that technically matches the task list but weakens the brief's intended outcome as incomplete or deviated work