saranskumar Goal
Design automation scripts that are predictable, maintainable, and safe to run.
When to Use
- A script automates repetitive developer or operator work.
- The task is environment-sensitive or configuration-heavy.
- The team needs a durable replacement for a copy-pasted shell sequence.
Instructions
- Define inputs, outputs, side effects, and runtime.
- Choose the right language or scripting surface.
- Add dry-run, logging, and safety behavior where relevant.
- Clarify when the script should evolve into a package or CLI.
Constraints
- Avoid machine-specific assumptions.
- Keep secrets out of scripts and logs.
- Make destructive behavior explicit.
Output Format
- script design
- runtime and input/output notes
- safety features
- escalation path
Examples
- "Design a script to rotate logs and archive artifacts."
- "Plan an automation script for developer environment setup."