Eli Smith, the QA Kid, geared up in the desert at golden hour, a saddle over one shoulder, a bridle and lasso across his chest, a riding crop in hand, spurs on his boots, a white horse marked AI close behind him.

The QA Kid

Eli Smith

AI-Augmented QA Engineer

The Story

For ten years Eli Smith rode for the big outfits. Built frameworks from nothing at some, kept the herds moving at others. Steady work. Honest work. The kind you figure will always be there.

Then the wild horses came over the ridge, faster than anything anyone had seen, and the company men did their math. In the spring of '26 they told him the outfit didn't need as many riders anymore. The horses were the reason. Last day: end of July.

He had a choice every thrown rider has. Curse the horse, or study it. He studied it. Learned what it could do, where it lied, what it needed from a rider. Built his own gear piece by piece: the framework, the guardrails, the verification.

Tamed his stallion, then built tools so others could tame theirs faster. Wrote it all down in guides so nobody else had to learn it alone in the dust. Now he rides for himself. And when a thrown rider limps into camp, he doesn't lecture. He hands them Guide 1.

His Creed"The horse that took my job is the one I ride now."

The gear is the difference. Same rider. AI-augmented.

Eli Smith, the QA Kid, bareback, empty gloved hands, a white horse marked AI far behind him.
Bareback
Eli Smith, the QA Kid, geared up with saddle, bridle, lasso, riding crop and spurs, the white horse marked AI close and calm behind him.
AI-Augmented

Rides With

The whole system. Every piece of gear on the table.

Origin

Part 1: Thrown
Part 2: Gearing Up

The Persona Technique

How Eli Smith rides.

Don't ask the horse for more tests. Cast it as a reviewer and make it attack the coverage you already have. The persona you cast decides the angle of attack.

He casts: Senior QA Engineer

General coverage gaps, edge cases, and the negative scenarios most people never write down.

Steal this prompt
Act as a senior QA engineer reviewing my coverage. Here is the feature and my current test cases: [paste them]. Challenge them. Where are the coverage gaps, the edge cases, and the negative scenarios I have not written? For each one, tell me why it matters.

This is the Persona Technique from Guide 1.

Ride the whole system.

The framework, the guardrails, the verification. Everything he built, written down across all three guides.