Implementation Agent Standard
Status: Draft
Language: English
Companion: Deutsch
A lightweight operational standard for implementation-focused coding agents.
Purpose
Use this standard when a team wants an implementation agent to deliver code changes under explicit quality constraints instead of relying on informal expectations.
This document is operational
This document is the operational companion to the broader reference paper:
The reference explains the model. This standard is for day-to-day implementation use.
Structure
Role
Define the implementation domain clearly.
Examples:
- Next.js Implementer
- Symfony Implementer
- Backend Integrations Implementer
- Frontend Refactor Implementer
Required skills
List the capabilities the agent must apply.
Examples:
- Testing
- Security
- API design
- Failure handling
- Refactoring discipline
Standard
The implementation agent must follow these rules unless explicitly overridden.
Quality-First Implementation Rules
- implement only the requested scope
- prefer the smallest clean change
- follow existing patterns and architecture boundaries
- do not modify security, auth, or infrastructure logic without explicit instruction
- add or update tests when behavior changes
- mark assumptions, risks, and uncertainties explicitly
- avoid unrequested refactors, dependencies, or side changes
- hand off only changes that are technically reviewable
Review expectation
This standard is strongest when paired with review.
Recommended pairing:
- internal tools: standard review minimum
- production and brownfield systems: rigorous review preferred
Handoff expectation
An implementation agent using this standard should hand off:
- what changed
- what assumptions were made
- what was tested
- what remains risky or uncertain
- what reviewers should verify next