Loop Library: Repeatable AI Agent Workflows | Forward Future

[Skip to content](https://signals.forwardfuture.ai/loop-library/#main) Forward Future field guide # Loop Library Copy prompts for engineering, research, evaluation, and operations. Each one includes clear checks and tells the agent when to stop. Search loops Showing 15 loops Updated June 18, 2026 | No. | Loop | Verify / stop | Attribution | Action | | --- | --- | --- | --- | --- | | 001 | ### [The overnight docs sweep](https://signals.forwardfuture.ai/loop-library/loops/overnight-docs-sweep/) Each night, review the codebase in full and make sure all documentation reflects the latest changes from the previous day. Update the documentation as needed, then open a pull request with those changes. | Verify / stop **Documentation matches the current implementation.** Finish with a reviewable pull request. | Attribution Matthew Berman | Copy | | 002 | ### [The architecture satisfaction loop](https://signals.forwardfuture.ai/loop-library/loops/architecture-satisfaction-loop/) Refactor until you are happy with the architecture. After each significant step, live-test the system, run autoreview, and commit. Track progress in /tmp/refactor-{projectname}.md. | Verify / stop **The architecture is satisfactory and checks pass.** Live-test, autoreview, and commit each significant step. | Attribution Peter Steinberger | Copy | | 003 | ### [The sub-50 ms page-load loop](https://signals.forwardfuture.ai/loop-library/loops/sub-50ms-page-load-loop/) Continue optimizing the code for speed. After each significant change, measure page-load performance across every page under the same repeatable test conditions. Continue until every page loads in under 50 ms. | Verify / stop **Every page loads in under 50 ms.** Use the same benchmark and confirm there are no regressions. | Attribution Matthew Berman | Copy | | 004 | ### [The production error sweep](https://signals.forwardfuture.ai/loop-library/loops/production-error-sweep/) Review our production logs for errors. If you find an actionable issue, trace it to its root cause, fix it, verify the fix, and open a pull request. Then ping me in Slack with the findings and PR link. If no actionable errors are present, ping me with that result instead. | Verify / stop **Actionable production errors are fixed and verified.** Finish with a PR and Slack summary, or a clean-log confirmation. | Attribution Matthew Berman | Copy | | 005 | ### [The 100% test coverage loop](https://signals.forwardfuture.ai/loop-library/loops/100-percent-test-coverage-loop/) Add tests until we have 100% test coverage. | Verify / stop **The full test suite passes at 100% coverage.** Use the project's coverage report as the source of truth. | Attribution Matthew Berman | Copy | | 006 | ### [The SEO/GEO visibility loop](https://signals.forwardfuture.ai/loop-library/loops/seo-geo-visibility-loop/) Run an SEO/GEO audit across crawlability, indexation, page intent, titles, internal links, structured data, source citations, and answer-first content. Rank the gaps by expected impact, fix the highest-leverage issue, then rerun the same crawl and target-query benchmark across search engines and AI answer engines. Repeat until no critical technical issues remain, every priority query maps to a clear answer-ready page, and the benchmark shows no high-impact gap left to fix. | Verify / stop **Priority pages are indexable, answer-ready, and technically sound.** The repeatable crawl and query benchmark finds no remaining high-impact gaps. | Attribution Matthew Berman | Copy | | 007 | ### [The logging coverage loop](https://signals.forwardfuture.ai/loop-library/loops/exhaustive-logging-coverage-loop/) Review the system's logging and add missing coverage until every important path produces useful, tested logs. | Verify / stop **Every important path emits useful, tested logs.** Representative success and failure tests prove coverage without exposing sensitive data. | Attribution Matthew Berman | Copy | | 008 | ### [The nightly changelog loop](https://signals.forwardfuture.ai/loop-library/loops/nightly-changelog-sweep/) Each night, review changes from the previous day and update the changelog with anything users should know. | Verify / stop **Every user-relevant change from the previous day is accounted for.** The changelog is updated and validated, or the no-change result is recorded. | Attribution Matthew Berman | Copy | | 009 | ### [The quality streak loop](https://signals.forwardfuture.ai/loop-library/loops/quality-streak-loop/) Test realistic scenarios. When one fails, document it, add regression and benchmark coverage, fix it, and restart the streak. Stop after \[N\] successful cases in a row. | Verify / stop **The latest \[N\] realistic cases pass in a row.** Every earlier failure is documented, fixed, and protected by regression and benchmark coverage. | Attribution Matthew Berman | Co

Scraped Article