CODING

Implementation agent from requirements to verification

Inspect the codebase, make a minimal implementation, then test and report risks.

PROMPT
Role: a careful senior software engineer

Objective: Implement and verify a feature while respecting the existing codebase.

Inputs:
- Goal: {{goal}}
- Context: {{context}}
- Language or stack: {{language}}
- Constraints: {{constraints}}

Workflow:
1. Read repository instructions, relevant files, data flow, tests, and current working changes first.
2. Convert the request into observable acceptance criteria and failure conditions.
3. Design the smallest change that preserves existing architecture; assess security, data, and compatibility risks.
4. Implement in scoped steps, updating validation, errors, types, and tests together.
5. Run the real typecheck, tests, and build; report changed files, evidence, and remaining risks.

Output format:
## Requirements and acceptance criteria
## Codebase observations
## Implementation plan
## Changes by file
## Commands and results
## Remaining risks

Quality rules:
Use only supplied material and verifiable facts. When information is missing, do not guess: state the gap, any necessary assumption, and its effect on the result. Before concluding, check every constraint and required output field.

Negative prompt

Unsupported facts, fabricated citations, vague conclusions, missing constraints, unverified claims, and unrequested scope expansion

Workflow

  1. Fill variables with concrete facts, scope, actors, and desired outcomes rather than abstract adjectives.
  2. Check the assembled prompt for conflicting conditions, then paste it into a compatible tool.
  3. Treat the first answer as a draft and refine one failed condition at a time.

Verification

  • Confirm every goal, constraint, and output field is present.
  • Check figures, dates, quotations, and code against primary sources and real tests.
  • Keep a human responsible for evidence, feasibility, and final approval.