Skip to content
InfratoApp
Layers / Observability / Evals / Prompt management / loop-engineering
L

loop-engineering

UNCLAIMED

By cobusgreyling

PROMPT MANAGEMENT

loop-engineering — Practical patterns, starters & CLI tools for loop engineering with AI coding agents. Design systems that prompt and orchestrate agents (inspired by Addy Osmani and Boris Cherny). Includes loop-audit,. Listed under Prompt management in the Observability / Evals layer. 2 of 6 comparison attributes are recorded, each with the page it was read from.

Stop prompting. Design the loop. Get a score. Two npx commands.

3 OF 4 SIGNALS HELD · MISSING LOGO

Websitecobusgreyling/loop-engineering

What it runs on, and what runs on it

0 cited edges
The differentiator

Computed from the stack graph, both directions. Every cited edge links the page it was read from; a vendor-added one links the vendor’s own source — this is the reason to be here rather than on the vendor’s own site.

No edges on record for loop-engineering.

Nothing in the directory documents depending on it, and its own docs do not name what it runs on. An edge is only stored when a source states it.

Submit a documented integration →

From cobusgreyling? No claim is needed for this: a link to your docs that names what loop-engineering runs on is enough.

Open-source signals

DOWNLOADS 30D
not measured
LAST COMMIT
not measured

A HOLLOW RING IS UNMEASURED, NOT ZERO · WE DO NOT SUBSTITUTE A PARENT COMPANY’S REPOSITORY FOR A PRODUCT THAT HAS NONE

Price

We hold no price for this product.

This is open-source software: you can run it yourself and the licence costs nothing. If the project also sells a hosted service, we do not yet hold the page it prices it on. If that changes — or if you publish /.well-known/pricing.json — it appears here with a capture date.

How we read prices →

What its categories ask

2 answered · 4 unanswered

6 questions declared by Prompt management. Most rows across the directory read like these.

ATTRIBUTEANSWEREVIDENCE · SOURCE
LicenceOpen source
“Open source · Tool-agnostic · Production-ready · 8 patterns · Interactive tools Stop prompting. Design the loop. Get a score. Run one command in any repo. @cobusgreyling/loop is the front door ( init + doctor ). loop-init still works. Prints your Loop Ready score plus the first run line.”
2026-10-06
Open sourceYes2026-09-23
Deploymentno answer on record
Git-backedno answer on record
Prompt versioningno answer on record
Web UIno answer on record

A ROW WITH NO ANSWER IS NOT A ROW WITH A “NO” · A VENDOR MAY ANSWER A BLANK ONE, MARKED VENDOR CLAIMED WITH ITS SOURCE · A DOCUMENTED VALUE IS DISPUTED, NOT OVERWRITTEN, AND STAYS VISIBLE WHILE WE RE-READ THE SOURCE

Practitioner reviews

Nobody has written one yet.

A review here is structured, not a star: hardware, scale band, what broke in production, and whether you would choose it again.

NO PERCENTAGE IS SHOWN UNDER FIVE REVIEWS · NO STAR RATINGS, EVER

Also in this category

18 products in Prompt management. Comparison defaults to within the category — pairing this with a GPU cloud would produce a page that means nothing.

langfuseUSED BY 16COMPARE →
academic-research-skillsNO DEPENDENTS RECORDEDCOMPARE →
academic-research-skills-codexNO DEPENDENTS RECORDEDCOMPARE →
acontextNO DEPENDENTS RECORDEDCOMPARE →
agency-agents-zhNO DEPENDENTS RECORDEDCOMPARE →
agentsNO DEPENDENTS RECORDEDCOMPARE →
cangjie-skillNO DEPENDENTS RECORDEDCOMPARE →
cavemanNO DEPENDENTS RECORDEDCOMPARE →

USED BY = LISTED PRODUCTS DEPENDING ON IT, IN THIS DIRECTORY

Frequently asked

Is loop-engineering open source?
Yes — it is listed as open source, and its repository is the source for the activity figures on this page rather than anything the project says about itself.
What does a blank mean on the loop-engineering page?
That nobody has told us, not that the answer is no. A hollow ring is "no answer on record", which is a different state from a recorded no — and the two look different on purpose. A blank is an absence of evidence, and this page shows how many of its questions are in that state rather than quietly leaving them out.
Where do the loop-engineering figures come from?
Each one is read from a public page — usually the vendor's own documentation or pricing page — and carries a link to it with the date it was read. Nothing here is estimated, averaged across sources, or inferred from a similar product. If a figure cannot be traced to a page, it is not published.
Can loop-engineering change what this page says?
They can claim the listing and supply or correct values, which are then labelled as theirs. They cannot remove the page, hide a comparison they are losing, or change a figure somebody else recorded with a source. Nothing on the page is for sale. How the site is paid for is set out under money and independence at /our-data#sec5.
Something here is wrong — how do I fix it?
Dispute the value. Every figure links to the page it was read from, so a dispute names the value and gives a source that contradicts it. That is the only lever anyone has over this page, and it is the same lever for the vendor, a competitor and a reader.
Is this listing run by cobusgreyling?
No. It is built from public sources, and no value on it came from the company. Its website is on shared hosting, so an email address cannot prove who owns it and there is no claim by address. A correction with a source can be sent instead. A claim lets the company write the tagline, description and logo, and answer blank questions or add dependencies, each marked as theirs with a source. Prices, licence and OSS figures stay as the directory read them, category changes only through our review, and each can be disputed with a source.

Cite this page

A model that quotes us should quote us correctly. The reading and its date sit inside the citation rather than beside it, because a quotation carrying only a URL goes wrong the week the URL changes.

infratoapp, “loop-engineering — Prompt management”, read 6 October 2026. Licence: Open source as published at cobusgreyling.github.io. https://www.infratoapp.com/products/loop-engineering

What loop-engineering can and cannot change here

Claiming cobusgreyling lets its admins and editors change the tagline, description, logo, docs link and deployment model of every product that org owns — live, labelled as theirs, and logged. Answers to blank questions and dependencies go live too, marked as the owner’s and sourced; a documented answer cannot be overwritten. Everything else on this page is a stated fact with a dispute route: price, licence and OSS figures. Those columns are ungranted at the database level, so they are not a feature we withheld — they are a write that cannot happen. Name, category, website, pricing page and package names can be changed by the owner only through our review. A dispute never deletes a value; it marks it and publishes the correction.

cobusgreyling’s website is on shared hosting, so an email address cannot prove who owns it and there is no claim by address. If you maintain it, send a correction with a source.

Maintain cobusgreyling? Ask us to verify you.