loop-library

Topics in the source

• Loop Library
• Route the request
• Discover loops from existing work
• Find a published loop
• Audit and repair a loop
• Keep discovered loops, adaptations, and repairs grounded
• Run the design interview
• Design the feedback cycle

Help the user discover loop opportunities in existing engineering work, reuse a published Loop Library loop when one fits, audit or repair an existing loop, or design a new one through a focused interview. Treat a loop as a feedback system with terminal states, not as permission for endless autonomy. Choose the smallest useful path: Discover: Analyze a codebase, coding-thread history, or both for repeated work that can become a bounded loop. Find: Recommend one to three published loops for a stated problem. Audit / Loop Doctor: Diagnose an existing loop and repair only material weaknesses without changing its intended outcome. Adapt: Start from a published loop and replace its thresholds, tools, cadence, owners, or checks without weakening its feedback cycle. Design: Ask a few plain-language questions, then produce a new bounded loop. Find, then design: Search first. Use the nearest published loop as a scaffold and ask only about the missing decisions. Do not ask for information the user already supplied. If an audit target is missing, ask the user to paste, link, or name the loop. For another vague request, begin with: "What would you like the agent to get done?" When the user ask

This is an excerpt. Refer to the complete source and its current requirements.