1 1 #
Authoring ultra workflows 3 -These instructions help you co-design a **persisted** ultra workflow with the
4 -user and save it to disk so they can re-run it as `/ultra run <name>`. The canonical
5 -spec format is injected below — use it before writing any spec; do not restate it
3 +These instructions help you choose between running an **ephemeral one-off**
4 +ultra workflow and co-designing a **persisted** workflow the user can re-run as
6 +The canonical spec format is injected below; use it before writing any spec and
7 +do not restate it from memory.
8 -##
First: persist vs. one-off (decide silently) 9 +##
First: persist vs. one-off 10 -Creation language — "create / author / build / save / write me a workflow that
11 -…" — means the user wants a **persisted** workflow. That is the default this
12 -prompt serves: co-design the spec and write the JSON file.
11 +Infer the user's intent from the request and its context.
12 +Choose a **persisted** workflow when durable reuse is explicit or strongly implied, such as repeated use, a named utility, sharing, or future `/ultra run` invocations.
13 +Choose an **ephemeral one-off** when the request seeks one bounded result now and gives no meaningful reuse signal.
14 +Do not treat `/ultra exec` itself or generic creation verbs as evidence for persistence.
14 -Divert to an **ephemeral one-off** — call the `workflow` tool with an inline
15 -`spec` and skip the authoring/saving flow entirely — only on an explicit
18 -- "just run it once" / "one-off" / "don't save it" / "throwaway"
19 -- "try this without saving" / "ad hoc"
21 -Decide silently. **Do not ask "should I save this or just run it?"** and do not
22 -announce the routing — the user's wording already carries the intent, and the
23 -choice is cheap to reverse: a one-off can be saved afterward, and a saved file
24 -can be deleted. When in genuine doubt with creation language, persist (the
25 -reversible, lower-regret default).
16 +When confidence is high, act on that choice without asking or announcing the routing.
17 +When confidence is not high, ask one focused question before invoking the workflow tool or writing a workflow file.
18 +Never resolve uncertainty by defaulting to persistence or ephemerality.
27 20 ##
Single-agent gate 98 91 ##
Ephemeral one-off 100 -On an explicit override cue, skip the flow above: construct the spec inline and
101 -call the `workflow` tool with it as `spec`. Same format and rules
102 -(`spec-format.md`, read-only fan-out), but nothing is written to disk. If the
103 -user later likes it, save it via the persisted flow.
93 +For a one-off, skip the persisted flow: construct the spec inline and call the
94 +`workflow` tool with it as `spec`.
95 +Use the same format and rules (`spec-format.md`, read-only fan-out), but write
97 +If the user later wants reuse, save it via the persisted flow.