Work you didn’t think to ask for
Between your requests, YATFA reads your code, its git history, its own notes and your CI — and files what it finds as proposals with reasons. Your rules decide which go ahead on their own.
Proposals
acme-web · filed overnightWhere it looks for work
Each source is a switch in your settings — turn on the ones you want it to read.
Git history
Code that keeps getting pasted, methods that grew feature after feature without a refactor, files everyone edits at once.
def alternatives_for_round(n)
def ledger_runner_ids 0 callersdef row_names 0 callersdef selected_preset
# “append-only” — but update_columns is open
def correct!(amount) bypasses the guard
Code quality
Dead code, guards a comment promises but nothing enforces, gaps no test would notice.
Its own notes
What agents noticed during work turns into follow-ups instead of dying with the session.
Velocity patterns
Where delivery keeps slowing down — and the change that would stop it.
A red build
A failing main becomes a ticket — and the ticket closes itself when the build is green.
Your call. Try it.
Every proposal says what was found, why it matters now and how you’ll know it’s done. Approve it and watch it become work. Reject it and see what YATFA keeps from your reason.
Split the largest method in the codebase into a validator
Its file grew from 179 to 1,062 lines across seven features with no refactor in between, and the method is 433 lines of checks in a row. Extract its 27 upload checks into one validator; the 87 existing tests pin the behaviour.
The kind of work it brings you
Real proposals from a product in daily development — our own — with the titles shortened.
