The outcome

Share an inspectable automation recipe that behaves predictably across users and environments.

Step by step

A workflow you can repeat.

  1. 01

    Select a stable manual workflow and map its inputs, outputs, dependencies, extensions, credentials, approval points, retries, and terminal states.

  2. 02

    Create a recipe with typed or clearly documented parameters, narrow instructions, pinned extensions, bounded steps, and no embedded secrets.

  3. 03

    Run it in a disposable environment with normal, missing, malformed, adversarial, tool-failure, timeout, and duplicate-execution cases.

  4. 04

    Compare results with the manual baseline, inspect every side effect and model-dependent decision, and add deterministic checks where possible.

  5. 05

    Version and review the recipe as code, document ownership and rollback, and distribute it only with required permissions and provider assumptions.

Working standard

What good use looks like.

  • Never embed credentials in recipes.
  • Pin and review extensions.
  • Test retries and duplicate execution.

Official references

Check the current product documentation.