Set minimum-completeness gates for inputs

Packaged know-how that tells an agent how to do a job well.

You might say…

“Without explicit gates, I'd always convince myself the data was good enough — and pay for it later in the output.”

What it does

Defines the minimum acceptable completeness or quality threshold each input must meet before its step may proceed, and what to do when an input falls short.

Trigger: Use once the input spec exists, to make each step's go/no-go condition explicit before building checklists.

I/O: Per-phase input specification → completeness gates per input with pass criteria and defined fallback actions

Recognise the problem?

The primitives are the commodity part. The fastest next step is a conversation about composing them into something that works for you.

Start a conversation