DEV Community

Cover image for I gave my agent 2,048 job specs so it stops improvising
rambo
rambo

Posted on Edited on

I gave my agent 2,048 job specs so it stops improvising

Every job I hand an agent starts with the same waste: the agent improvises the job spec. It guesses the inputs, guesses what a finished result looks like, guesses when to stop, and I grade the guesses at the end. The model was never the weak part. The blank prompt was.

So Zambo shipped the specs. There are now 64 task guides holding 2,048 task-specific starter recipes at https://zambo.dev/workflows/tasks/ and each starter is a ready job, not a prompt tip.

The anatomy of one starter

Each starter carries six parts, in the same order every time:

  1. Inputs, named up front, so the agent asks for what the task actually needs instead of discovering it halfway through.
  2. A copyable prompt, written for that one task.
  3. An output checklist, the shape done has to arrive in.
  4. Review checks, the questions to run before you accept the result.
  5. Stop conditions, the points where the agent stops and reports instead of pushing on and hoping.
  6. A JSON recipe, the whole starter as structured data a tool can load directly.

The starter I use most is handover-current-state, from the multi-ai-handover-plan guide: https://zambo.dev/workflows/tasks/multi-ai-handover-plan/#handover-current-state

It asks for the job as it stands right now, forces finished work and work in flight into separate piles, and will not let the agent name a next step nobody decided. Handover is Zambo's flagship, so that starter had to be the tightest one in the set.

Two more worth opening before you judge the idea:

Every starter has its own anchor link, so you can send a teammate, or another agent, the exact job instead of a page and a note saying scroll down a bit.

The resume prompt trick, for switching AIs mid-job

The 25 workflows that predated the guides are still at https://zambo.dev/workflows/ and that index gained four things in the same release: a workflow finder (find by problem or outcome), browser-saved shortcuts kept in localStorage with nothing sent to Zambo, public template links, and the one I now use daily, the resume prompt: pick up where you left off.

Practical version: a job outgrows the session it started in, or the session hits its limit, or a different AI is simply better at the next phase. Instead of pasting a summary you wrote from memory, you resume from the saved workflow state. The next AI starts from the recorded state, the checklist, and the stop conditions, not from your retelling. On Zambo, picking up in another AI is always free, which is the detail that makes the trick a habit instead of an emergency procedure.

A refusal with a receipt

The honesty test for all of this is document work. Zambo's doc_intel tool analyzes at most 24,000 UTF-16 code units per call and reports exact coverage, the source_sha256, and next_offset on every call.

A clean run, live and checkable: https://zambo.dev/run/ac016d46-b3d2-45d0-ae46-8d0c63dce9b2 (992 of 992 characters, hash matched).

The interesting case is the failure. If the source changes between parts, doc_intel refuses with code source_changed and issues a receipt for the refusal: https://zambo.dev/run/bc83e018-51df-4e2b-b461-7c5b1c35c107

That refusal consumed no quota. Most tools would silently analyze a stitched-together document that never existed at any single moment. I would rather ship the tool that stops, says why, and leaves a record of stopping.

That record is a verifiable AER-1 receipt. Plain version of the claim, because it matters: a receipt proves the saved result was not changed since it was saved. It does not prove the answer was right. AER-1 is an IETF Internet-Draft, draft-zambo-aer1-26: https://datatracker.ietf.org/doc/draft-zambo-aer1/26/

At verification this morning: 128,922 public receipts, 1,583 that day, version 4.1.0, 153 tools with 37 on the default surface, behind one MCP endpoint: https://zambo.dev/mcp

Try it

Add https://zambo.dev/mcp to the AI you already use. Every tool free once a day, plus 3 continue calls. One free wrap-up handover per day, and pickup is always free. Day Pass is $0.99 for 24 hours, the Zambo Pass is $29 for 30 days ($19 for $ZAMBO holders), and Lifetime is $250 one payment. No annual tier.

Then do not start from a blank prompt. Pick a starter: https://zambo.dev/workflows/tasks/

Top comments (0)