Extra values

If the workflow you selected references {{extra.<key>}} anywhere in its prompts, the scan form asks you to fill in those values. This is the scan side of the Extra variable.

What you'll see

open·kritt reads the workflow's prompts and knows exactly which extra keys it needs. The form shows one field per expected key - for example, a workflow that uses {{extra.goal}}, {{extra.actor}}, and {{extra.permissions}} presents three inputs.

The values are required

Every expected key must be provided; the scan is rejected if any are missing or blank. Only the keys the workflow actually references are kept - extra values that the workflow doesn't use are dropped.

Once set, the values are injected into the render context, so a prompt like:

You are {{extra.actor}} trying to {{extra.goal}}.
Your permissions are "{{extra.permissions}}".

resolves with your inputs at run time.

Note

This is what makes a workflow reusable: the same blueprint scans many targets by changing only the extra values, not the prompts.

Next: model and harness.