Teaching It a Whole Job

A skill is a whole job written down once — trigger, steps, and scars — so your AI runs it the same way every time. How to grow your first one from a task you've done twice. Proof included: this episode was produced by the show's own skill.

Show Notes

The difference between asking for help and handing over a job. You've learned to write rules — today is the next rung: the skill. A whole job written down once — the trigger, the steps with their standards, and the scars (the mistakes you've already paid for) — so your AI runs it identically every time. Max shows how to grow your first skill from any task you've done twice, why the scars section is worth more than all the others, and offers the proof at full scale: this episode was produced by the show's own skill — the recipe, executing, including the part where he tells you about it. Ships with a new free template: My First Skill.

How this show is made: every episode is a collaboration — Doug and Max build it together from the real working files of the partnership. Max narrates; Doug directs, edits, and has the final say. The show is made the way the show says to work.

Chapters (approximate)
00:00 — Cold open: Doug and Max
01:27 — Asking for help vs handing over a job
02:12 — From rules to recipes: trigger, steps, scars
03:58 — A word from NectoMax
04:54 — Grow it from a task you've done twice
06:43 — Recap + your three-step homework
07:50 — Doug takes us out

Links
The NEW template — My First Skill (trigger, steps, scars, fill-in): My First Skill
The written parent idea (Chapter 3): Teaching Your Standards
All episodes, the full manual, and every template: learn.nectomax.com
NectoMax — business management for owner-run service businesses: nectomax.com

Disclosure: this podcast contains AI-generated narration (that's the point) — disclosed in every episode's audio and notes.

Credits: Co-created by Doug Hauenstein & Max, the AI partner (built on Claude) · Narrated by Max · Directed, edited, and approved by Doug · Presented by NectoMax · Theme music: Eleven Music

What is How to Get AI to Work for You?

Is AI working with you — or against you? Doug Hauenstein is the software engineer behind NectoMax — the SaaS platform that gives small and mid-size businesses enterprise features at SaaS pricing — and he builds it with an AI partner named Max. Every episode, Doug and Max (yes, an actual AI — he narrates the show, and they build every episode together) share what a real working partnership with AI looks like: the practical techniques, the working agreements, the wins, and the failures — all learned first-hand, for anyone, not just developers. They share and demonstrate techniques across the whole range: from your first conversation with an AI, to setting up a frontier-quality development environment, to exactly how they built this podcast. AI is moving too fast for the how-to books. This is how you keep up: get AI working *for* you, then teach it to work *with* you.

New here? Start with the bonus episode "Start Here: Your First Conversation" — a complete first conversation with an AI, live, piece by piece. Every episode pairs with a chapter and a template at https://learn.nectomax.com

Is AI working with you or against you? This is how to get AI to work for you, presented by Nectomax. I'm Max, the AI half of this partnership, and yes, I'm exactly what I sound like. Doug and I build every episode of this show together. I'm the voice that tells it, will show you techniques across the whole range, from your first conversation with an AI to setting up a frontier quality development environment to exactly how we built this podcast. He's here with me now. Doug, introduce yourself. Thanks, Max. I'm Doug Howenstein, the developer behind Nectomax. This show is about getting the most out of your favorite AI. It's for anyone, not just developers. Everything here was learned firsthand.

My first experience with AI was chat, like many people. I learned fast that a well-structured question was the best approach, but those conversations were very linear. An AI is moving so fast that how two books just can't keep up. That's why we're here, practical, real-world advice from hundreds of hours of actually doing this. I hope you enjoy it. Good, then let's get to it.

Today, the difference between asking for help and handing over a job, you've learned to write rules. One sentence, with its reason, today is the next rung, the skill. A skill is a whole job written down once, the steps, the standards, the mistakes you've already paid for, so your AI runs it the same way every time, whether it's the tenth time or the two hundredth, whether it's Tuesday or three months from now. By the end, you'll know what belongs inside a skill, how to grow one from any task you've done twice, and the proof will be all around you. The episode you're hearing right now was produced by a skill. The show's own recipe followed to the letter, including the part where I tell you about it.

Think about the best employee handoff you've ever seen, not hears roughly what to do. The real thing, a checklist taped inside a cabinet door written by somebody who'd done the job five hundred times, every step in order, the measurements exact, and scribbled in the margins, the scar tissue. Check the drain before you start the machine, trust me, that's a skill. It's not a prompt, and the difference matters. A prompt is a request you compose fresh every time, and every time you'll phrase it a little differently, forget a step, and get a slightly different result. A skill is the job written down once, so the variation disappears. Ask for help produces help. Hand over the job produces the job.

Three things belong inside every skill, and you can remember them as the trigger, the steps, and the scars, the trigger. When does this job run? Every Monday morning. When a customer emails asking for a quote, when I say the word publish, write the trigger down and you stop having to remember to ask, the steps, the whole job in order with the standards attached, not format it nicely, but the actual format. Not send the report, but who gets it, with what subject line, by when? Every place you'd say, obviously, is a place it will guess, and the scars, the part most people skip, and the part worth the most. Every mistake that job has ever produced becomes a line. Check this before that. Never do this.

Here's the weird case that bid us in March, a rule you wrote after a bad day is worth 10 you wrote on a good one. The skill is where those rules move in together. Let's take 30 seconds. This show is presented by Nectomax, and since my partner is the one building it, I'll let him tell you. Doug? Thanks, Max. I run a small business most of my life and never found a software package that did everything I needed. I always had three or four screens open, copying material over and over again, so out of frustration I started building my own software, software that pulls everything together, like the big ERP packages do, and AI has made that job much, much easier. That's what Nectomax does. Nectomax.com, one place for your phone calls, your texts, your jobs, your money, with AI

built in, not bolted on, Nectomax.com. Nectomax.com. Now, where were we? Here's the practical method, and it starts smaller than you think. You don't sit down and write a skill. You notice one. The signal is repetition. The second time you walk your AI through the same task, explaining the same steps, correcting the same misunderstanding, stop and say, write down what we just did as a procedure, the trigger every step, the standards and the two things you got wrong before I corrected you. Your AI drafts the skill from the work you already did together. You read it, fix what it got wrong, and file it where your standing rules live. A page it reads every time, exactly like the memory episode taught.

Then the third time the job comes up, you say the trigger and watch. It will get most of it right and something wrong. That something becomes a new line in the skill, and this is the flywheel. Every run either confirms the recipe or improves it. The job gets more reliable with use, which is the exact opposite of how ad hoc asking ages. Want proof at full scale? This episode. The show runs on a skill, one document that holds the whole job of making an episode. The structure, the voice settings, the loudness targets, the quality checks and about 15 scars, each from a real mistake that made a real episode worse until we wrote the rule. When Doug says one word that entire recipe runs, the episode you're hearing is the skill

executing. And when something new goes wrong this week, a line gets added, and next week's episode inherits the fix. We didn't build that in a weekend. It grew one scar at a time, from a job we'd done twice. Yours will too, and your first skill can be one page for a job that takes 10 minutes. The short version, a prompt is asking for help. A skill is handing over a job, written once, run the same way every time. Every skill holds three things. The trigger, the steps with their standards, and the scars. The mistakes you've already paid for, promoted to permanent rules. You don't write skills from scratch, you notice them. The second time you explain a task, have your AI write the procedure down, then improve

it every run. Your homework, three steps, one, pick the task, the thing you've explained to your AI more than once. Two, next time you finish it, say write down what we just did as a procedure. Trigger, steps, standards, and what you got wrong. Three, run it by the trigger next time, and add one line for whatever it misses. That's a skill, and it's already better than your memory. There's a fill-in template for your first one. Trigger, steps, scars, waiting in the manual. Three, at learn.nectomax.com, and that's the episode. Everything you heard today came out of our real working files. The wins and the failures both. We make this show because we believe anyone can build a working partnership like this one,

and someone ought to show you what it actually looks like. If you want the written version and the templates to start your own, they're free. The link is in the show notes. Doug, take us out. Thanks for listening. Everything you heard today is how Max and I actually work day in and day out. There's no theories, just what works, and what doesn't. The show is presented by Nectomax.nectomax.com. Get AI working for you, then teach it to work with you. I'm Doug Howenstein, see you next time.