Tag

Tagged #workflow

26 pieces

Steering the agentAn agent will do the wrong thing — confidently — if you let it guessSteering isn't ordering louder; it's leaving no room to guess Steering the agentA vague command isn't short — it's openThree parts that leave the agent only one correct reading: goal, boundaries, result shape Steering the agentDon't tell it not to — make it unable toForcing functions: turn bad behavior from 'inadvisable' into 'impossible'Steering the agentGive it permission to say 'I'm not sure' — then require itSealing the blind spots you didn't foresee, with one line at the top of the task Context & memoryAn agent has no memory — it has a small, finite deskWhat to keep, what to drop, and when not to spend a line of the AI's thinking on what a script can do Orchestrating many agentsWhen one agent isn't enough, don't multiply it — divide the workMore agents aren't automatically faster; they're faster when each has a clear role and there's one place to merge Shipping with AIFour control gates that let an agent ship real workUse this when you want the agent to work more independently without quietly drifting off and calling it done Shipping with AIDon't Ask the Agent for a Plan — Gate ItThe thirty-second gate between understanding and doing Shipping with AIOne Giant Turn Is Where the Agent Gets LostStages and checkpoints — the only way to move fast without doing the work twice Shipping with AIThe Most Expensive Bug Is the One That Keeps the Build GreenMake the agent read the blast radius before it touches anything shared Production in the wildPutting agent output into the real world without quiet breakageA field checklist for testing the ugly cases, boundaries, and signals before you trust an agent beyond the chat Economics & tradeoffsThe error is cheap when it happens. It gets expensive when you find out.The real cost of an agent error starts when someone acts on it — not when it was made. And those two moments are usually further apart than you think.Tools & setupCLAUDE.md is not documentation — it is the operating law of your agentMost people write CLAUDE.md like a README. But if you write it right, the agent stops asking questions it should not need to ask and stops doing things it should not be doing.Tools & setupSet it once, skip the explainingEvery time you re-explain the same context to an agent, you're paying a recurring fee for something you never set up once. Setup is the upfront payment that means you never pay again.Tools & setupBuild in the checkpointVerifying 'when you feel like it' means verifying once you're already worried — which is usually already a little late. A good check doesn't ask your mood; it sits inside the workflow.Measure & improveYour minimum feedback loop — five minutes a week is enoughSix months of experience does not turn into skill on its own. It turns into habit — and a habit can be progress or it can be a rut. The thing that separates the two is a small loop you barely have to spend time on.Measure & improveYour prompt library is a living body, not a storage closetA good prompt you never save is lost. A bad prompt you never retire still charges you every time you pull it out. A prompt library is not a place to stash things — it is a set of assets with a lifecycle, and any lifecycle nobody tends decays.Measure & improveUsing the agent more but feeling more tired — that is not you failing, it is a signalAn approach that once worked does not announce the moment it stops working. You keep going because it is familiar, because you invested in it, because changing feels like a hassle. But three fairly clear signals say your approach has gone stale — and because they are quiet, they are easy to miss.Measure & improveThe New Prompt Felt Better — But Was That an Improvement or Just Luck?You keep tuning prompts but the skill never compounds, because you can't separate what actually worked from one lucky run Agent skillsA principle you have to remember is a principle you'll forgetThe field handbook: turn each lesson into something installable — so the right thing happens without waiting on your memory Agent skillsMap the Blast Radius Before You EditA forcing function that makes the agent trace who depends on a symbol before it changes it.Agent skillsHand Off to Your Next SessionA slash command that turns a session into a note the next one can pick up cold.Agent skillsA Review That Doesn't Rubber-StampA reusable Skill that reviews a change for real problems instead of approving it by reflex.Working as a teamWhen the whole team has agents: rules in one head don't scale to a teamEverything you learned solo cracks when three people and three agents touch the same thing — because each agent only reads its own owner's rules Working as a teamThe agent that built it is the worst one to check itA second agent earns its place not as extra hands, but as an independent pair of eyes that doesn't share the first's blind spots Working as a teamWho owns what the agent wrote: 'the agent wrote it' is not an excuseWhen half the changes are agent-generated, accountability can't fall into a void — the person who hits merge puts their name on it

c

The author

Each story here wraps a lesson paid for in full.

craftagentsomeone building and learning at once

What are you building with agents? Want to trade notes, push back, or build something together — drop a line.

Write hello@craftagent.cloud

58pieces12clustersVI·ENbilingual