Loop directory

A cheap model watches your tracked sources nightly; the expensive model writes only the monthly synthesis.

Keep an aging ledger of unpaid invoices and draft the next nudge at each threshold — you send it.

Stay silent on normal days and page you with a pre-investigated cause only when a metric breaks its expected band.

Draft the repeated 80% of a proposal or RFP from your answer library and flag the new 20% for a human.

Each week, compare how work actually happened against the written SOP and flag where they've drifted apart.

Categorize transactions against history and hand a human a clean exception list — it never files anything.

Turn every unread email into a decision — do, delegate, defer, or drop — with the top reply already drafted.

Let analytics find the exact moment users give up, then rewrite the words on that one screen.

Compile app-store reviews and support into a roadmap ranked by how much pain each issue causes.

Sweep where people talk about you each week, cluster the complaints and asks, and deliver the loudest one as a drafted implementation plan.

Turn the pre-purchase questions people ask in DMs, comments, and emails into a reusable, deduplicated answer bank.

Start from 'I thought it did X' support tickets and walk back to the exact page sentence that over-promised.

Draft the next batch of ad creative before your current set fatigues — nothing launches without you.

Watch a curated list on X each morning, rank what's actually working, and draft your take in your own voice ready to review.

Keep your content pipeline stocked with fully-specified briefs mined from your own search traffic, so writers never start from a blank page.

Read competitors' newly published articles and the keywords they target, then plan your moves against the gaps they leave open.

Every week, ask the AI engines the same 'best [category]' questions your buyers ask, log where your brand ranks, and track the trend over time instead of guessing.

Catch thin or duplicate template-generated pages and flag them for a human before Google penalizes the set.

Each week, find the buyer questions people ask ChatGPT and Perplexity that your site doesn't answer yet, and close exactly one of those gaps.

Split a large mechanical job into 2–5 independent Codex lanes, each isolated in its own worktree with a frozen acceptance bar and binding judge, then block the final merge behind a full integration judge.

praetor is a Claude Code plugin that runs a plan → freeze acceptance bar → dispatch → independent fresh-context judge → resolve loop. Claude plans and judges, Codex executes; a FAIL from the judge cannot be overridden, with at most 2 retries before a loud takeover.

Run an agent repeatedly on a single refactoring task, persisting filesystem state between iterations until tests pass.

Ralph runs a generator and evaluator in tandem until all user stories pass acceptance criteria and browser tests.

Run your static analyzer on the security ruleset, fix one high-severity finding at a time, re-verify, and loop until zero remain or 10 turns pass.

Pick the oldest untriaged issue, validate it against the current build, then label it, close if obsolete, or document repro steps—one per turn until the queue empties or 12 iterations pass.

Every Friday at 2pm, draft release notes from merged PRs into releases/DRAFT.md and verify all links resolve.

Query the catalog for unindexed foreign keys, create a migration per missing index, and verify each with a full test run until all FKs are covered or 6 turns complete.

Every night at 3am, dump the production schema and diff it against migrations, filing issues for any drift found.

Pull the slowest PostgreSQL statement, optimize its query plan with an index or rewrite, verify the improvement, and repeat until all captured queries run under 100ms or hit eight iterations.

Re-invoke a specific PR review skill every 20 minutes until the review completes or you stop it.