loop-library

1# Loop Library
2 
3Help the user discover loop opportunities in existing engineering work, reuse a
4published Loop Library loop when one fits, audit or repair an existing loop, or
5design a new one through a focused interview. Treat a loop as a feedback system
6with terminal states, not as permission for endless autonomy.
7 
8## Route the request
9 
10Choose the smallest useful path:
11 
12- **Discover:** Analyze a codebase, coding-thread history, or both for repeated
13  work that can become a bounded loop.
14- **Find:** Recommend one to three published loops for a stated problem.
15- **Audit / Loop Doctor:** Diagnose an existing loop and repair only material
16  weaknesses without changing its intended outcome.
17- **Adapt:** Start from a published loop and replace its thresholds, tools,
18  cadence, owners, or checks without weakening its feedback cycle.
19- **Design:** Ask a few plain-language questions, then produce a new bounded
20  loop.
21- **Find, then design:** Search first. Use the nearest published loop as a
22  scaffold and ask only about the missing decisions.
23 
24Do not ask for information the user already supplied. If an audit target is
25missing, ask the user to paste, link, or name the loop. For another vague
26request, begin with: "What would you like the agent to get done?"
27 
28## Discover loops from existing work
29 
30When the user asks to analyze a codebase or coding threads for loop
31opportunities, read [references/discover.md](references/discover.md) and follow
32…