Repeatability
High
The requirements are structurally fixed: four PostgreSQL instances, specific features to add, a hard time limit. There is no unique judgment needed per run — the same script pattern applies every time.
Ambiguity Tolerance
High
Success criteria are concrete and enumerable: timeout enforcement, exponential backoff retry, Slack webhook on failure, state file tracking, and an 8-hour process kill. An agent can verify each requirement is present in the output.
Data & Tool Availability
Medium
The agent needs the original legacy script to refactor, plus the Slack webhook URL and PostgreSQL connection details. Without the source script, the agent must write from scratch, which is doable but less precise. These inputs are easy to provide but must be explicitly supplied.
Error Cost
Medium
A buggy script deployed to production could silently fail backups or corrupt state files, which is a real operational risk. However, the output is a script that a human can review before deployment, making the error reversible before it causes damage.
Human Judgment Required
Low
The design decisions here — retry counts, timeout values, state file format — are conventional engineering choices with well-established patterns. No taste, ethics, or relationship context is needed; a human should review the output but not co-author it.