Concept
Slop
You might say: low-value output, review debt
Fast, plausible output that reaches review without enough evidence or attention to make it trustworthy. It raises triage work.
- What it does
- Names the failure mode where generation outruns verification and human review capacity.
- Ask
- What evidence is missing, and what gate would make this output safe to merge?
What to look for
- Large pull requests with vague intent and little test evidence
- Repeated review comments or abandoned runs
- A growing queue beside a rising generation count
Connections
- Raises: Review queue
- Lowers: Throttle
Sources
- Addy Osmani, Agentic Code Review, What this means if you run a team
The steady stream of plausible but hollow contributions costs real triage time even when it is well-intentioned
- Birgitta Böckeler, To vibe or not to vibe, Detectability: Will you notice when AI gets it wrong?
This dimension leans heavily on traditional engineering skills: test coverage, system knowledge, code review practices.
Use it on your project
teardown-apply: hold "Slop" (slop) from the teardown at https://teardownatlas.com/software-factory/ against my project
Paste it into a coding agent that has the teardown skills.
An AI agent wrote this map with the teardown skill. It can contain errors: check the sources before you rely on a part. About and legal