When I code, I prompt, wait, and see what comes back. For a bigger feature I might reach for something like spec-driven development. Either way, I'm babysitting the coding harness through every interaction.
Don't get me wrong, that can work well. But plenty of problems are too complex to solve with a single prompt. For those, I'd much rather write one prompt, walk away, and come back to finished work. The patterns in this post came out of trying to do exactly that.
There are five of them, each a step past prompting and specs, and together they keep my agent working while I'm off doing something else: scheduled jobs, memory, subagents, workflows, and bots.
I show everything in Kiro Crew , the open source coding harness I know best, and a couple of things in the Kiro IDE.…