Owning the whole path alone became possible not because people suddenly got smarter, but because leverage appeared. AI takes on the execution volume that used to require a separate pair of hands at each stretch. But leverage is an amplifier, not a replacement: it multiplies what you put into it, and it equally happily multiplies both the right direction and the mistake.
That's why the whole prior conversation about problem, contact, outcome and slice didn't become obsolete with AI's arrival — it became more important. The more powerful the amplifier, the costlier it is to get the direction wrong. A product engineer wins not because they have AI — everyone does — but because they know what to put into that AI.
What AI takes on, and what it doesn't
AI is good at taking on volume: writing code from a clear spec, breaking it into layers, sketching options, doing the routine that is plentiful and mechanical. Here it saves days and weeks, and it's exactly this that lets one person reach the stretches there weren't enough hands for before.
What AI doesn't take on is the decisions about what to do and why. Which problem we're solving, what contact with the user will show, which outcome we count as success, what we don't build — these are questions of taste, responsibility and understanding people. AI can help think them through, but it can't decide them for you: it has no skin in the game and no contact with reality of its own. Hand it these decisions and you'll get, quickly and well made, the wrong thing.
What to give the agent, what to keep for yourself
The boundary runs roughly like this. To the agent — execution and search: write from a spec, generate options, check code against rules, comb through the details. To yourself — framing and judgement: name the problem, choose the outcome, decide what goes into the slice, and assess whether the result actually relieved the pain.
A practical sign: anything that can be checked against clear rules can be given to the agent; anything that requires contact with the user and responsibility for the consequences stays with the human. A product engineer doesn't write less code by hand on principle — they move themselves higher up the path: to where it's decided what to build, while the building itself is increasingly handed to the lever.
Why the lever breaks without methodology
AI without methodology has a treacherous property: across three sessions on one task it gives three different solutions. All three work, all three incompatible. For a one-off sketch this doesn't matter; for a product that lives for years and is carried by one person, it's a slow collapse: each piece is good on its own, and together they don't add up.
Methodology fixes this by giving a shared context that outlives a single session. Use Case Pattern sets the framework — how to describe the task, how to break it into layers, which rules to hold — and the agent applies the same framework over and over. Here is the key to the whole concept: one piece of knowledge exists in two forms — the article explains to you why and how, while the paired skill holds the same rule for the agent at every step. You steer, the methodology holds consistency, the agent executes the volume. Without the middle link, the lever tears the product apart faster than you can assemble it.
Closing the arc
Six essays add up to one path. It begins with the problem, not the solution; is tested by contact with the user; is measured by the outcome metric; is compressed to the smallest valuable slice; is carried through by end-to-end ownership; and is multiplied by AI as leverage. Each step rests on the previous: the lever without a problem strikes wide, ownership without a slice drowns, an outcome without contact is made up.
Together they are the content of the product specialization — that part of Use Case Pattern thanks to which one person makes the whole product. The technical specializations give the power to build; this one answers what and why. Having mastered both sides, an engineer stops being an executor of someone else's specs and becomes the one who carries the product from a person's problem to a solved task — on their own, with methodology and AI at hand.