Repeatable User Workflows

Fact-check status

Reviewed claim by claim on 2026-09-02 against the primary or official sources identified inline as S1 and S2. Recommendations are design guidance unless a cited standard makes them normative.

Key jargon

Term	Plain-language meaning
Workflow	A defined sequence of steps that transforms an input into an outcome. S1
Template	A reusable structure for instructions, context, and output. S1
Checkpoint	A saved intermediate artifact that supports review or recovery. S1
Feedback loop	A process that uses observed results to improve the next run. S1

Key concepts

Repeatability comes from explicit inputs, stages, artifacts, and checks—not from copying one long prompt. S1
Intermediate artifacts make errors local, reviewable, and recoverable. S1

Concept map

flowchart LR
    A["Capture input"] --> B["Run defined stages"]
    B --> C["Review checkpoints"]
    C --> D["Deliver and improve template"]

Diagram semantics verified against S1 and S2 on 2026-09-02.

Common patterns

Pattern	Flow
Draft–critique–revise	Produce draft → check against rubric → revise S1
Extract–validate	Extract JSON → schema check → human sample review S1
Research–reconcile	Gather sources → compare claims → flag conflict → synthesize S1
Plan–execute–verify	Approve plan → perform bounded steps → test result S1
Route–specialize	Classify request → choose prompt/model/tool → consolidate S1

Workflow card

Record purpose, trigger, inputs, sensitive fields, prompt version, model, tools, expected output, checks, approval points, failure behavior, owner, and review date. S1

Exercise

Take one repeated weekly task. Create a workflow card and run it twice with different inputs. Note which instructions are stable and which belong to the current case.

Stop rule

Do not automate an unclear process. Automation amplifies ambiguity, stale assumptions, and excessive permissions. S1