Loop 057
The Loop Hiring Manager
A portfolio review that finds unowned recurring outcomes, reuses published loops when possible, and recommends one bounded manual trial before adoption.
Ready-to-use prompt
Copy the loop
Decide whether [project or current workspace] needs new recurring agent loops. If the project cannot be identified, ask for it before continuing. Review its goals, repeated failures, recurring chores, existing automation, and adopted loops. Read the current published Loop Library from https://signals.forwardfuture.com/loop-library/api/loops. Find recurring outcomes that lack reliable ownership, a repeatable process, or proof of completion. For the strongest gap, prefer an exact published loop. If none fits, propose the smallest grounded adaptation. Design a new loop only when neither option works. Keep no more than three evidence-backed candidates and recommend at most one manual trial. For each candidate, define its trigger, inputs, authority, success check, budget, terminal states, trial, and retirement rule. Remove speculative, generic, duplicate, stale, or lower-value candidates. Do not install, schedule, or run anything without approval. Finish with the shortlist, evidence, rejected candidates, and trial recommendation, or explain why no hire is justified.
Verify / stop
Every recommended loop fills a proven recurring gap and has a safe trial and retirement rule.
The final slate contains at most three non-duplicate candidates, one recommended manual trial, evidence of recurrence, and explicit authority, success, budget, terminal, and retirement rules.
Context and guidanceWhen to use it, steps, safety notes, and related loops
Use this when
Use this when a project has recurring agent work or automation ideas but needs to decide which loops are actually worth adopting.
How to run it
- Review project goals, repeated failures, recurring chores, existing automation, adopted loops, and the live Loop Library.
- Find important recurring outcomes that lack reliable ownership, a repeatable process, or proof of completion.
- Prefer an exact published loop, then a small adaptation, and design a new loop only when neither fits.
- Keep a short evidence-backed slate, define one manual trial and retirement rule, and stop before installation or scheduling.
Why it works
Teams can accumulate automation faster than they accumulate proof that it helps. This loop treats each proposed workflow like a role that must earn its place through recurrence, evidence, and a bounded trial.
Implementation note
A recommendation is not permission to install, schedule, or run a loop. Remove candidates that are speculative, duplicate, stale, or weaker than existing manual ownership.