AI Prompts for Coding

Work from [relevant source/files], [language/runtime/framework versions], and [required behavior or constraints]. Ask only for missing information that affects correctness; otherwise state a limited assumption. Parse [timestamp column] under [format and timezone policy] and quarantine invalid rows. Preserve existing behavior outside the requested scope and prefer the smallest necessary edit. Return the concrete deliverable this task requires (patch, query, example, checklist, or plan), a brief reason, and verification evidence or steps. Check ambiguous local times and original-value preservation. Distinguish proposed checks from actually executed checks; never invent successful runs. Use sanitized examples and placeholders for credentials or private data.

Work from [relevant source/files], [language/runtime/framework versions], and [required behavior or constraints]. Ask only for missing information that affects correctness; otherwise state a limited assumption. Compare [source records] with [target records] using [matching rules]. Preserve existing behavior outside the requested scope and prefer the smallest necessary edit. Return the concrete deliverable this task requires (patch, query, example, checklist, or plan), a brief reason, and verification evidence or steps. Report unmatched and ambiguous cases instead of guessing identities. Distinguish proposed checks from actually executed checks; never invent successful runs. Use sanitized examples and placeholders for credentials or private data.

Work from [relevant source/files], [language/runtime/framework versions], and [required behavior or constraints]. Ask only for missing information that affects correctness; otherwise state a limited assumption. Parse [document samples] for [required fields] and attach source location and confidence limits. Preserve existing behavior outside the requested scope and prefer the smallest necessary edit. Return the concrete deliverable this task requires (patch, query, example, checklist, or plan), a brief reason, and verification evidence or steps. Check missing fields and never invent unreadable content. Distinguish proposed checks from actually executed checks; never invent successful runs. Use sanitized examples and placeholders for credentials or private data.

Work from [relevant source/files], [language/runtime/framework versions], and [required behavior or constraints]. Ask only for missing information that affects correctness; otherwise state a limited assumption. Convert [input format] to [output format] in a separate destination with explicit naming. Preserve existing behavior outside the requested scope and prefer the smallest necessary edit. Return the concrete deliverable this task requires (patch, query, example, checklist, or plan), a brief reason, and verification evidence or steps. Check output completeness and avoid overwriting originals. Distinguish proposed checks from actually executed checks; never invent successful runs. Use sanitized examples and placeholders for credentials or private data.

Work from [relevant source/files], [language/runtime/framework versions], and [required behavior or constraints]. Ask only for missing information that affects correctness; otherwise state a limited assumption. Parse [log samples] using [documented format] with retained raw lines for failures. Preserve existing behavior outside the requested scope and prefer the smallest necessary edit. Return the concrete deliverable this task requires (patch, query, example, checklist, or plan), a brief reason, and verification evidence or steps. Check multiline events, malformed records, and timestamps. Distinguish proposed checks from actually executed checks; never invent successful runs. Use sanitized examples and placeholders for credentials or private data.

Work from [relevant source/files], [language/runtime/framework versions], and [required behavior or constraints]. Ask only for missing information that affects correctness; otherwise state a limited assumption. Analyze [previous export] and [new export] for added, missing, and type-changed fields. Preserve existing behavior outside the requested scope and prefer the smallest necessary edit. Return the concrete deliverable this task requires (patch, query, example, checklist, or plan), a brief reason, and verification evidence or steps. Separate schema drift from sparse data. Distinguish proposed checks from actually executed checks; never invent successful runs. Use sanitized examples and placeholders for credentials or private data.

Work from [relevant source/files], [language/runtime/framework versions], and [required behavior or constraints]. Ask only for missing information that affects correctness; otherwise state a limited assumption. Transform [sample schema] under [redaction policy] using synthetic replacements. Preserve existing behavior outside the requested scope and prefer the smallest necessary edit. Return the concrete deliverable this task requires (patch, query, example, checklist, or plan), a brief reason, and verification evidence or steps. Check relationships remain valid and originals are not copied into logs. Distinguish proposed checks from actually executed checks; never invent successful runs. Use sanitized examples and placeholders for credentials or private data.

Work from [relevant source/files], [language/runtime/framework versions], and [required behavior or constraints]. Ask only for missing information that affects correctness; otherwise state a limited assumption. Design [incremental import] using [timestamp or sequence watermark] and [late-arrival rules]. Preserve existing behavior outside the requested scope and prefer the smallest necessary edit. Return the concrete deliverable this task requires (patch, query, example, checklist, or plan), a brief reason, and verification evidence or steps. Check equal timestamps, replay, and delayed records. Distinguish proposed checks from actually executed checks; never invent successful runs. Use sanitized examples and placeholders for credentials or private data.

Work from [relevant source/files], [language/runtime/framework versions], and [required behavior or constraints]. Ask only for missing information that affects correctness; otherwise state a limited assumption. Reconcile [input totals] and [output totals] under [filter and rounding rules]. Preserve existing behavior outside the requested scope and prefer the smallest necessary edit. Return the concrete deliverable this task requires (patch, query, example, checklist, or plan), a brief reason, and verification evidence or steps. Explain every excluded row or value difference. Distinguish proposed checks from actually executed checks; never invent successful runs. Use sanitized examples and placeholders for credentials or private data.

Work from [relevant source/files], [language/runtime/framework versions], and [required behavior or constraints]. Ask only for missing information that affects correctness; otherwise state a limited assumption. Extract [archive] to [approved destination] with validated members and clear failure reporting. Preserve existing behavior outside the requested scope and prefer the smallest necessary edit. Return the concrete deliverable this task requires (patch, query, example, checklist, or plan), a brief reason, and verification evidence or steps. Check traversal, duplicate names, size limits, and retained originals. Distinguish proposed checks from actually executed checks; never invent successful runs. Use sanitized examples and placeholders for credentials or private data.

Work from [relevant source/files], [language/runtime/framework versions], and [required behavior or constraints]. Ask only for missing information that affects correctness; otherwise state a limited assumption. Model concurrent calls to [shared-state update] and identify where writes overwrite each other. Preserve existing behavior outside the requested scope and prefer the smallest necessary edit. Return the concrete deliverable this task requires (patch, query, example, checklist, or plan), a brief reason, and verification evidence or steps. Provide an interleaving and an invariant-preserving minimal fix. Distinguish proposed checks from actually executed checks; never invent successful runs. Use sanitized examples and placeholders for credentials or private data.

Work from [relevant source/files], [language/runtime/framework versions], and [required behavior or constraints]. Ask only for missing information that affects correctness; otherwise state a limited assumption. Protect [shared resource] with a lock only around operations needing atomicity. Preserve existing behavior outside the requested scope and prefer the smallest necessary edit. Return the concrete deliverable this task requires (patch, query, example, checklist, or plan), a brief reason, and verification evidence or steps. Check nested calls, deadlock risk, and long blocking work. Distinguish proposed checks from actually executed checks; never invent successful runs. Use sanitized examples and placeholders for credentials or private data.

Work from [relevant source/files], [language/runtime/framework versions], and [required behavior or constraints]. Ask only for missing information that affects correctness; otherwise state a limited assumption. Define [distributed lease] using [store capabilities] and [failure model]. Preserve existing behavior outside the requested scope and prefer the smallest necessary edit. Return the concrete deliverable this task requires (patch, query, example, checklist, or plan), a brief reason, and verification evidence or steps. Check renewal failure and stale owners continuing work. Distinguish proposed checks from actually executed checks; never invent successful runs. Use sanitized examples and placeholders for credentials or private data.

Work from [relevant source/files], [language/runtime/framework versions], and [required behavior or constraints]. Ask only for missing information that affects correctness; otherwise state a limited assumption. Revise [consumer] under [delivery semantics] so duplicate delivery has controlled effects. Preserve existing behavior outside the requested scope and prefer the smallest necessary edit. Return the concrete deliverable this task requires (patch, query, example, checklist, or plan), a brief reason, and verification evidence or steps. Check acknowledge timing and failures around persistence. Distinguish proposed checks from actually executed checks; never invent successful runs. Use sanitized examples and placeholders for credentials or private data.

Work from [relevant source/files], [language/runtime/framework versions], and [required behavior or constraints]. Ask only for missing information that affects correctness; otherwise state a limited assumption. Document convergence for [replicated workflow] using [observed delays] and [user requirements]. Preserve existing behavior outside the requested scope and prefer the smallest necessary edit. Return the concrete deliverable this task requires (patch, query, example, checklist, or plan), a brief reason, and verification evidence or steps. Separate temporary stale reads from violated invariants. Distinguish proposed checks from actually executed checks; never invent successful runs. Use sanitized examples and placeholders for credentials or private data.

Work from [relevant source/files], [language/runtime/framework versions], and [required behavior or constraints]. Ask only for missing information that affects correctness; otherwise state a limited assumption. Process [items] with [concurrency limit], explicit ordering, and error policy. Preserve existing behavior outside the requested scope and prefer the smallest necessary edit. Return the concrete deliverable this task requires (patch, query, example, checklist, or plan), a brief reason, and verification evidence or steps. Check one failure, cancellation, and maximum active operations. Distinguish proposed checks from actually executed checks; never invent successful runs. Use sanitized examples and placeholders for credentials or private data.

Work from [relevant source/files], [language/runtime/framework versions], and [required behavior or constraints]. Ask only for missing information that affects correctness; otherwise state a limited assumption. Replace [check-then-write flow] with an appropriate atomic operation under [storage contract]. Preserve existing behavior outside the requested scope and prefer the smallest necessary edit. Return the concrete deliverable this task requires (patch, query, example, checklist, or plan), a brief reason, and verification evidence or steps. Check simultaneous callers and conflict reporting. Distinguish proposed checks from actually executed checks; never invent successful runs. Use sanitized examples and placeholders for credentials or private data.

Work from [relevant source/files], [language/runtime/framework versions], and [required behavior or constraints]. Ask only for missing information that affects correctness; otherwise state a limited assumption. Design [event processing] so [entity key] operations remain ordered without serializing all work. Preserve existing behavior outside the requested scope and prefer the smallest necessary edit. Return the concrete deliverable this task requires (patch, query, example, checklist, or plan), a brief reason, and verification evidence or steps. Check multiple keys and retries of older events. Distinguish proposed checks from actually executed checks; never invent successful runs. Use sanitized examples and placeholders for credentials or private data.

Work from [relevant source/files], [language/runtime/framework versions], and [required behavior or constraints]. Ask only for missing information that affects correctness; otherwise state a limited assumption. Prevent [obsolete operation result] from replacing [newer state] using [identity or version rules]. Preserve existing behavior outside the requested scope and prefer the smallest necessary edit. Return the concrete deliverable this task requires (patch, query, example, checklist, or plan), a brief reason, and verification evidence or steps. Check deliberately inverted completion order. Distinguish proposed checks from actually executed checks; never invent successful runs. Use sanitized examples and placeholders for credentials or private data.

Work from [relevant source/files], [language/runtime/framework versions], and [required behavior or constraints]. Ask only for missing information that affects correctness; otherwise state a limited assumption. Use [lock acquisition paths] to show possible cycles and propose consistent ordering. Preserve existing behavior outside the requested scope and prefer the smallest necessary edit. Return the concrete deliverable this task requires (patch, query, example, checklist, or plan), a brief reason, and verification evidence or steps. Check release on error and nested acquisition paths. Distinguish proposed checks from actually executed checks; never invent successful runs. Use sanitized examples and placeholders for credentials or private data.

Work from [relevant source/files], [language/runtime/framework versions], and [required behavior or constraints]. Ask only for missing information that affects correctness; otherwise state a limited assumption. Pass [cancellation signal] across [operation chain] with explicit cleanup responsibility. Preserve existing behavior outside the requested scope and prefer the smallest necessary edit. Return the concrete deliverable this task requires (patch, query, example, checklist, or plan), a brief reason, and verification evidence or steps. Check cancellation before start, during work, and after completion. Distinguish proposed checks from actually executed checks; never invent successful runs. Use sanitized examples and placeholders for credentials or private data.

Work from [relevant source/files], [language/runtime/framework versions], and [required behavior or constraints]. Ask only for missing information that affects correctness; otherwise state a limited assumption. Review [cache operations] for atomic access, computation duplication, and eviction coordination. Preserve existing behavior outside the requested scope and prefer the smallest necessary edit. Return the concrete deliverable this task requires (patch, query, example, checklist, or plan), a brief reason, and verification evidence or steps. Check concurrent readers and invalidation during population. Distinguish proposed checks from actually executed checks; never invent successful runs. Use sanitized examples and placeholders for credentials or private data.

Work from [relevant source/files], [language/runtime/framework versions], and [required behavior or constraints]. Ask only for missing information that affects correctness; otherwise state a limited assumption. Deduplicate concurrent [equivalent requests] under [key rules] while handling caller cancellation. Preserve existing behavior outside the requested scope and prefer the smallest necessary edit. Return the concrete deliverable this task requires (patch, query, example, checklist, or plan), a brief reason, and verification evidence or steps. Check failed shared work and independent key requests. Distinguish proposed checks from actually executed checks; never invent successful runs. Use sanitized examples and placeholders for credentials or private data.

Work from [relevant source/files], [language/runtime/framework versions], and [required behavior or constraints]. Ask only for missing information that affects correctness; otherwise state a limited assumption. Map retries in [client], [gateway], and [worker] to avoid multiplicative retries. Preserve existing behavior outside the requested scope and prefer the smallest necessary edit. Return the concrete deliverable this task requires (patch, query, example, checklist, or plan), a brief reason, and verification evidence or steps. Check total attempts, deadlines, and idempotency requirements. Distinguish proposed checks from actually executed checks; never invent successful runs. Use sanitized examples and placeholders for credentials or private data.

Work from [relevant source/files], [language/runtime/framework versions], and [required behavior or constraints]. Ask only for missing information that affects correctness; otherwise state a limited assumption. Define [multi-service workflow] and compensations from [domain rules]. Preserve existing behavior outside the requested scope and prefer the smallest necessary edit. Return the concrete deliverable this task requires (patch, query, example, checklist, or plan), a brief reason, and verification evidence or steps. Check partial success, compensation failure, and manual recovery records. Distinguish proposed checks from actually executed checks; never invent successful runs. Use sanitized examples and placeholders for credentials or private data.

Work from [relevant source/files], [language/runtime/framework versions], and [required behavior or constraints]. Ask only for missing information that affects correctness; otherwise state a limited assumption. Repair [completion counter or latch] so failures and cancellations cannot leave it stuck. Preserve existing behavior outside the requested scope and prefer the smallest necessary edit. Return the concrete deliverable this task requires (patch, query, example, checklist, or plan), a brief reason, and verification evidence or steps. Check empty workloads and concurrent final operations. Distinguish proposed checks from actually executed checks; never invent successful runs. Use sanitized examples and placeholders for credentials or private data.

Work from [relevant source/files], [language/runtime/framework versions], and [required behavior or constraints]. Ask only for missing information that affects correctness; otherwise state a limited assumption. Plan [configuration rollout] across [instances] with mixed-version behavior. Preserve existing behavior outside the requested scope and prefer the smallest necessary edit. Return the concrete deliverable this task requires (patch, query, example, checklist, or plan), a brief reason, and verification evidence or steps. Check temporary disagreement and rollback compatibility. Distinguish proposed checks from actually executed checks; never invent successful runs. Use sanitized examples and placeholders for credentials or private data.

Work from [relevant source/files], [language/runtime/framework versions], and [required behavior or constraints]. Ask only for missing information that affects correctness; otherwise state a limited assumption. Choose buffer size and backpressure for [producer] and [consumer] using [resource limits]. Preserve existing behavior outside the requested scope and prefer the smallest necessary edit. Return the concrete deliverable this task requires (patch, query, example, checklist, or plan), a brief reason, and verification evidence or steps. Check slow consumers, shutdown, and dropped-work policy. Distinguish proposed checks from actually executed checks; never invent successful runs. Use sanitized examples and placeholders for credentials or private data.

Work from [relevant source/files], [language/runtime/framework versions], and [required behavior or constraints]. Ask only for missing information that affects correctness; otherwise state a limited assumption. Review [timeout and scheduling code] for appropriate clocks under [runtime]. Preserve existing behavior outside the requested scope and prefer the smallest necessary edit. Return the concrete deliverable this task requires (patch, query, example, checklist, or plan), a brief reason, and verification evidence or steps. Check clock jumps and stated calendar-based scheduling rules. Distinguish proposed checks from actually executed checks; never invent successful runs. Use sanitized examples and placeholders for credentials or private data.

Work from [relevant source/files], [language/runtime/framework versions], and [required behavior or constraints]. Ask only for missing information that affects correctness; otherwise state a limited assumption. Design a bounded experiment for [authorized distributed test environment] targeting [one failure mode]. Preserve existing behavior outside the requested scope and prefer the smallest necessary edit. Return the concrete deliverable this task requires (patch, query, example, checklist, or plan), a brief reason, and verification evidence or steps. Specify hypotheses, stop criteria, recovery, and observed evidence requirements. Distinguish proposed checks from actually executed checks; never invent successful runs. Use sanitized examples and placeholders for credentials or private data.

Work from [relevant source/files], [language/runtime/framework versions], and [required behavior or constraints]. Ask only for missing information that affects correctness; otherwise state a limited assumption. Use [repository files] to document setup, first run, and required configuration without inventing commands. Preserve existing behavior outside the requested scope and prefer the smallest necessary edit. Return the concrete deliverable this task requires (patch, query, example, checklist, or plan), a brief reason, and verification evidence or steps. Flag unverified steps and missing environment details. Distinguish proposed checks from actually executed checks; never invent successful runs. Use sanitized examples and placeholders for credentials or private data.

Work from [relevant source/files], [language/runtime/framework versions], and [required behavior or constraints]. Ask only for missing information that affects correctness; otherwise state a limited assumption. Build a minimal example for [API] using [actual signatures] and [supported version]. Preserve existing behavior outside the requested scope and prefer the smallest necessary edit. Return the concrete deliverable this task requires (patch, query, example, checklist, or plan), a brief reason, and verification evidence or steps. Check imports, argument names, expected output, and error handling. Distinguish proposed checks from actually executed checks; never invent successful runs. Use sanitized examples and placeholders for credentials or private data.

Work from [relevant source/files], [language/runtime/framework versions], and [required behavior or constraints]. Ask only for missing information that affects correctness; otherwise state a limited assumption. Explain [configuration sources] with exact precedence and meaningful examples. Preserve existing behavior outside the requested scope and prefer the smallest necessary edit. Return the concrete deliverable this task requires (patch, query, example, checklist, or plan), a brief reason, and verification evidence or steps. Check documentation matches supplied implementation. Distinguish proposed checks from actually executed checks; never invent successful runs. Use sanitized examples and placeholders for credentials or private data.

Work from [relevant source/files], [language/runtime/framework versions], and [required behavior or constraints]. Ask only for missing information that affects correctness; otherwise state a limited assumption. Document [decision], alternatives, constraints, consequences, and reconsideration triggers from [evidence]. Preserve existing behavior outside the requested scope and prefer the smallest necessary edit. Return the concrete deliverable this task requires (patch, query, example, checklist, or plan), a brief reason, and verification evidence or steps. Separate accepted decisions from proposals. Distinguish proposed checks from actually executed checks; never invent successful runs. Use sanitized examples and placeholders for credentials or private data.

Work from [relevant source/files], [language/runtime/framework versions], and [required behavior or constraints]. Ask only for missing information that affects correctness; otherwise state a limited assumption. Turn [error logs] and [known causes] into ordered diagnostic steps with expected observations. Preserve existing behavior outside the requested scope and prefer the smallest necessary edit. Return the concrete deliverable this task requires (patch, query, example, checklist, or plan), a brief reason, and verification evidence or steps. Avoid presenting guesses as established fixes. Distinguish proposed checks from actually executed checks; never invent successful runs. Use sanitized examples and placeholders for credentials or private data.

Work from [relevant source/files], [language/runtime/framework versions], and [required behavior or constraints]. Ask only for missing information that affects correctness; otherwise state a limited assumption. Describe [diff] using the triggering problem, resulting behavior, and actual validation evidence. Preserve existing behavior outside the requested scope and prefer the smallest necessary edit. Return the concrete deliverable this task requires (patch, query, example, checklist, or plan), a brief reason, and verification evidence or steps. Keep implementation detail only where it explains a practical limitation. Distinguish proposed checks from actually executed checks; never invent successful runs. Use sanitized examples and placeholders for credentials or private data.

Work from [relevant source/files], [language/runtime/framework versions], and [required behavior or constraints]. Ask only for missing information that affects correctness; otherwise state a limited assumption. Summarize [changes] as user-visible behavior and compatibility notes. Preserve existing behavior outside the requested scope and prefer the smallest necessary edit. Return the concrete deliverable this task requires (patch, query, example, checklist, or plan), a brief reason, and verification evidence or steps. Do not include abandoned approaches or unimplemented features. Distinguish proposed checks from actually executed checks; never invent successful runs. Use sanitized examples and placeholders for credentials or private data.

Work from [relevant source/files], [language/runtime/framework versions], and [required behavior or constraints]. Ask only for missing information that affects correctness; otherwise state a limited assumption. Use [handler code] and [response samples] to describe status codes, fields, and client recovery. Preserve existing behavior outside the requested scope and prefer the smallest necessary edit. Return the concrete deliverable this task requires (patch, query, example, checklist, or plan), a brief reason, and verification evidence or steps. Check examples reflect real implemented errors. Distinguish proposed checks from actually executed checks; never invent successful runs. Use sanitized examples and placeholders for credentials or private data.

Work from [relevant source/files], [language/runtime/framework versions], and [required behavior or constraints]. Ask only for missing information that affects correctness; otherwise state a limited assumption. Design a small safe exercise around [module] with prerequisites, expected result, and review points. Preserve existing behavior outside the requested scope and prefer the smallest necessary edit. Return the concrete deliverable this task requires (patch, query, example, checklist, or plan), a brief reason, and verification evidence or steps. Ensure it does not require production credentials or destructive actions. Distinguish proposed checks from actually executed checks; never invent successful runs. Use sanitized examples and placeholders for credentials or private data.

Work from [relevant source/files], [language/runtime/framework versions], and [required behavior or constraints]. Ask only for missing information that affects correctness; otherwise state a limited assumption. Trace [entry point] to [side effect] using supplied source references. Preserve existing behavior outside the requested scope and prefer the smallest necessary edit. Return the concrete deliverable this task requires (patch, query, example, checklist, or plan), a brief reason, and verification evidence or steps. Mark dynamic or external steps that cannot be confirmed statically. Distinguish proposed checks from actually executed checks; never invent successful runs. Use sanitized examples and placeholders for credentials or private data.

Work from [relevant source/files], [language/runtime/framework versions], and [required behavior or constraints]. Ask only for missing information that affects correctness; otherwise state a limited assumption. Create a runbook for [incident type] using [approved procedures] and [actual diagnostics]. Preserve existing behavior outside the requested scope and prefer the smallest necessary edit. Return the concrete deliverable this task requires (patch, query, example, checklist, or plan), a brief reason, and verification evidence or steps. Include precise stop and escalation conditions, not speculative commands. Distinguish proposed checks from actually executed checks; never invent successful runs. Use sanitized examples and placeholders for credentials or private data.

Work from [relevant source/files], [language/runtime/framework versions], and [required behavior or constraints]. Ask only for missing information that affects correctness; otherwise state a limited assumption. Rewrite [comment and code] to explain the invariant, reason, and relevant edge case. Preserve existing behavior outside the requested scope and prefer the smallest necessary edit. Return the concrete deliverable this task requires (patch, query, example, checklist, or plan), a brief reason, and verification evidence or steps. Check the comment does not merely repeat syntax or claim unsupported behavior. Distinguish proposed checks from actually executed checks; never invent successful runs. Use sanitized examples and placeholders for credentials or private data.

Work from [relevant source/files], [language/runtime/framework versions], and [required behavior or constraints]. Ask only for missing information that affects correctness; otherwise state a limited assumption. Document [toolchain], [supported platforms], and [dependency constraints] from supplied files. Preserve existing behavior outside the requested scope and prefer the smallest necessary edit. Return the concrete deliverable this task requires (patch, query, example, checklist, or plan), a brief reason, and verification evidence or steps. Distinguish declared support from environments actually tested. Distinguish proposed checks from actually executed checks; never invent successful runs. Use sanitized examples and placeholders for credentials or private data.

Work from [relevant source/files], [language/runtime/framework versions], and [required behavior or constraints]. Ask only for missing information that affects correctness; otherwise state a limited assumption. Define [domain terms] using [code and business rules] with examples and source references. Preserve existing behavior outside the requested scope and prefer the smallest necessary edit. Return the concrete deliverable this task requires (patch, query, example, checklist, or plan), a brief reason, and verification evidence or steps. Flag terms whose meaning cannot be established from evidence. Distinguish proposed checks from actually executed checks; never invent successful runs. Use sanitized examples and placeholders for credentials or private data.

Work from [relevant source/files], [language/runtime/framework versions], and [required behavior or constraints]. Ask only for missing information that affects correctness; otherwise state a limited assumption. Compare [old contract] and [new contract] and provide minimal consumer changes. Preserve existing behavior outside the requested scope and prefer the smallest necessary edit. Return the concrete deliverable this task requires (patch, query, example, checklist, or plan), a brief reason, and verification evidence or steps. Check defaults, error behavior, and deprecation dates only from supplied documentation. Distinguish proposed checks from actually executed checks; never invent successful runs. Use sanitized examples and placeholders for credentials or private data.

Work from [relevant source/files], [language/runtime/framework versions], and [required behavior or constraints]. Ask only for missing information that affects correctness; otherwise state a limited assumption. Audit [setup instructions] against [project files] for missing steps or incorrect commands. Preserve existing behavior outside the requested scope and prefer the smallest necessary edit. Return the concrete deliverable this task requires (patch, query, example, checklist, or plan), a brief reason, and verification evidence or steps. Identify commands needing secrets or platform-specific adaptation. Distinguish proposed checks from actually executed checks; never invent successful runs. Use sanitized examples and placeholders for credentials or private data.

Work from [relevant source/files], [language/runtime/framework versions], and [required behavior or constraints]. Ask only for missing information that affects correctness; otherwise state a limited assumption. Build a concise review checklist for [patch] focusing on contracts, edge cases, and relevant evidence. Preserve existing behavior outside the requested scope and prefer the smallest necessary edit. Return the concrete deliverable this task requires (patch, query, example, checklist, or plan), a brief reason, and verification evidence or steps. Avoid generic checklist items that do not apply. Distinguish proposed checks from actually executed checks; never invent successful runs. Use sanitized examples and placeholders for credentials or private data.

Work from [relevant source/files], [language/runtime/framework versions], and [required behavior or constraints]. Ask only for missing information that affects correctness; otherwise state a limited assumption. Describe [known debt] using observed maintenance cost and failure risk, then rank small remedies. Preserve existing behavior outside the requested scope and prefer the smallest necessary edit. Return the concrete deliverable this task requires (patch, query, example, checklist, or plan), a brief reason, and verification evidence or steps. Do not invent incidents or savings. Distinguish proposed checks from actually executed checks; never invent successful runs. Use sanitized examples and placeholders for credentials or private data.

Work from [relevant source/files], [language/runtime/framework versions], and [required behavior or constraints]. Ask only for missing information that affects correctness; otherwise state a limited assumption. Create fields for [product/module] capturing versions, minimal steps, expected/actual behavior, and sanitized evidence. Preserve existing behavior outside the requested scope and prefer the smallest necessary edit. Return the concrete deliverable this task requires (patch, query, example, checklist, or plan), a brief reason, and verification evidence or steps. Check a sample report provides enough information to reproduce. Distinguish proposed checks from actually executed checks; never invent successful runs. Use sanitized examples and placeholders for credentials or private data.

Work from [relevant source/files], [language/runtime/framework versions], and [required behavior or constraints]. Ask only for missing information that affects correctness; otherwise state a limited assumption. Explain [CLI implementation] outputs, exit codes, and error-stream behavior for automation users. Preserve existing behavior outside the requested scope and prefer the smallest necessary edit. Return the concrete deliverable this task requires (patch, query, example, checklist, or plan), a brief reason, and verification evidence or steps. Check success, invalid input, and runtime failure examples. Distinguish proposed checks from actually executed checks; never invent successful runs. Use sanitized examples and placeholders for credentials or private data.