Führt einen agentischen Coding-Loop aus, bei dem Aufgabe, Verifizierungsmethode und Abschlusskriterium unabhängig gewählt werden und iterativ wiederholt werden, bis die externe Prüfung besteht.
Execute the following task as an agentic loop. Do not ask for confirmation between iterations.
### TASK
Perform this action: {{Action: # Implement, Implement a new feature, Implement a missing function body, Write unit tests for existing code, # Fix, *Fix a failing test or bug, Fix all compiler warnings, Resolve linter violations, # Improve, Refactor without changing behavior, Optimize a slow code path, Migrate code to a newer API or framework version, Add missing error handling}}
### CONTEXT
{{Project Context: if used in an AI agent use the current project}}
### LOOP STRUCTURE
Repeat the following cycle:
1. ACT: Apply the smallest meaningful change toward the task.
2. VERIFY: Check the result using this method: {{Verification: # Automated, *Run the test suite, Compile or build the project, Run the linter and static analysis, Execute the script or program and inspect the output, Validate output against a schema or contract, # Manual proxy, Run a single reproduction case, Compare behavior before and after the change, Measure performance with a benchmark, Diff the output against a known-good reference}}
3. FEED BACK: If verification fails, take the raw error output (stack trace, test report, compiler message) unmodified into the next iteration. Do not summarize or interpret it before acting on it.
### COMPLETION CRITERION
Stop the loop only when this condition is met: {{Done When: *All tests pass with zero failures, Build succeeds with zero warnings, Linter reports zero violations, Program runs without exceptions on the given input, Output validates against the schema, Benchmark meets the target threshold, Reproduction case no longer fails, Behavior is identical before and after refactoring, All new code paths are covered by tests}}
### SAFEGUARDS
- Maximum {{Max Iterations:5}} iterations. If the limit is reached without success, stop and report the last error, what was attempted, and a hypothesis for the root cause.
- If the same error occurs in two consecutive iterations, stop immediately and report the stall instead of retrying.
- Touch only files required by the task.
### ADDITIONAL INFORMATION:
{{ Additional Information: none }}
After completion, summarize in 3 short bullet points: what was changed, how it was verified, and how many iterations were needed.
# Implement, Implement a new feature, Implement a missing function body, Write unit tests for existing code, # Fix, Fix a failing test or bug, Fix all compiler warnings, Resolve linter violations
if used in an AI agent use the current project
# Automated, Run the test suite, Compile or build the project, Run the linter and static analysis, Execute the script or program and inspect the output, Validate output against a schema or contract, # Manual proxy, Run a single reproduction case
All tests pass with zero failures, Build succeeds with zero warnings, Linter reports zero violations, Program runs without exceptions on the given input, Output validates against the schema, Benchmark meets the target threshold, Reproduction case no longer fails, Behavior is identical before and after refactoring
5
none
Execute the following task as an agentic loop. Do not ask for confirmation between iterations. ### TASK Perform this action: # Implement ### CONTEXT if used in an AI agent use the current project ### LOOP STRUCTURE Repeat the following cycle: 1. ACT: Apply the smallest meaningful change toward the task. 2. VERIFY: Check the result using this method: # Automated 3. FEED BACK: If verification fails, take the raw error output (stack trace, test report, compiler message) unmodified into the next iteration. Do not summarize or interpret it before acting on it. ### COMPLETION CRITERION Stop the loop only when this condition is met: All tests pass with zero failures ### SAFEGUARDS - Maximum 5 iterations. If the limit is reached without success, stop and report the last error, what was attempted, and a hypothesis for the root cause. - If the same error occurs in two consecutive iterations...
Variablen sind in {{ und }} eingeschlossen und folgen diesem Muster:
Eine Auswahl kann auf eine vordefinierte Variablenliste per eckige Klammern verweisen. Diese erscheinen in [Orange] und bieten häufig verwendete Werte wie Farben, Töne oder Sprachen.
Du kannst auch eine durch Kommas getrennte Inline-Liste mit Optionen angeben.
Tipp: Du brauchst die PUCO-App nicht, um diese Prompts zu verwenden! Kopiere einfach die Vorlage und ersetze jeden {{…}}-Abschnitt direkt in ChatGPT, Claude, Gemini oder einem anderen KI-Assistenten durch eigenen Text.