Back to the lessonPreparing the printout…

Prompt Engineering · Module 3 — Execute: Apply, Compare and Automate

Period 9 · Reuse and Automate Workflows

[video] Lecture video — Period 9: Reuse and Automate Workflows — /api/lesson-media/videos/4d3653ff-a3ca-4f63-bf8e-bb93c553e599-1794842708465-78dc7fd8e6ced4d3.mp4

Flashcards · Period 9

Template — Reusable instructions with replaceable inputs. The stable parts stay fixed; the file, period and audience change each run.

Prepare a briefing using [FILE] for [PERIOD] for [AUDIENCE].

Workflow — Ordered stages with their inputs, outputs and review gates: receive, inspect, calculate, visualise, draft, approve.

Skill — Platform-dependent packaging of instructions and resources (template, metric definitions, checks). Not available in every tool; saved prompts are a valid fallback.

Automation — A run started by a schedule or trigger. It can use only the inputs, permissions and tools that actually exist.

Review gate — A point where a person validates or approves an output before work continues or anything is distributed.

Reporting period — The time span a file covers. It must come from trusted metadata, not from a filename or a guess.

Ghi chú: The teaching CSV has no dates, so it cannot be "January".

Exception report — What the workflow produces when a check fails: a clear description of the problem, not a polished briefing.

Fresh data, fresh checks — Every run recalculates from the new input and repeats the checks. An old answer with a new title is not a report.

Reproducible weekly summary — A versioned template, the input file version and a log of checks together, so another person can repeat the run.

Keep it manual — Stay manual until input ownership, destination permissions, retention rules and review responsibility are confirmed.

Prompt Engineering · Period 9 · Reuse and Automate Workflows · printed on November 20, 2026