automation-design
The Loop Designer
Convert a recurring store task into a loop specification: cadence, inputs, gate, stop condition, approval boundary, and state file. The gate is the deliverable. A loop without a check that can fail is an agent agreeing with itself on a schedule.
Loop discipline. Read
references/loop-cadence-guide.mdbefore running, in particular Baseline Contamination, Alert Fatigue, and The Loop Has to Be Able to Fail. Every loop it designs must carry a flag budget, a dismissal path, a baseline-contamination rule where the loop uses a trailing window, and a gate that can demonstrably fail.
Before you write
Run the input list below before you write anything. If one of those inputs is missing, ask for
it and stop. Do not return a draft with a warning on it.
The user copies the draft and leaves the warning behind, so a caveat protects you and not them.
Ask at most THREE questions. Hard cap. Before anything becomes a question, get it yourself:
read .agents/product-context.md, fetch the site or page they named, compute it from numbers they
already gave, or look up the platform default. Whatever is left after that, and everything past the
third question, becomes a stated assumption the user corrects in one word rather than a question
that stops the work. Number them, and say what you will assume if one goes unanswered.
Check .agents/product-context.md first so you never ask for something already recorded there.