Start with the job to be done

The working assignment is to run a thirty-minute weekly practice loop that improves one real workflow for a busy learner who wants durable skill rather than tool chasing. That sentence is narrower than “use A weekly AI habit.” It identifies a deliverable and a reviewer. Write a definition of done with three layers: the output must satisfy the audience's need; factual or functional claims must be traceable; and a named person must own the final decision. Consistency beats novelty. One checked experiment each week produces transferable judgment; browsing new tools without measuring work does not.

Start by separating tasks. The model may draft, classify, transform, compare, or suggest. It may not silently approve, publish, grade, deploy, cite, or consent on someone's behalf. For this assignment the authoritative material is one recurring task, baseline time/quality, a small prompt change, saved output, verification note, and retrospective. Anything absent from those inputs is either an explicit assumption or an unanswered question.

Use this prompt as a realistic starting contract:

This week I want to improve meeting-note follow-up. Baseline: 25 minutes and occasional missed owners. Design one 30-minute practice: a sanitized sample, one constrained prompt, a checklist for owner/date/source accuracy, and a five-minute retrospective. Keep the tool fixed and change only one prompting variable.

Notice what the prompt does: it states the setting, limits the output, names forbidden behavior, and requests evidence that can be reviewed. It does not ask the model to “make it amazing.” If a constraint matters, make it testable. Replace “be accurate” with a source boundary, formula check, test command, rights ledger, or approval step.

A useful response would look like this: A bounded weekly experiment with a baseline, one controlled change, an output check, and a decision to keep, revise, or discard the technique. That description is intentionally observable. “Looks good” is not acceptance. The operator must compare against the baseline, verify every owner and due date against source notes, record failure cases, and repeat on a second sanitized example before adopting. Keep the source material beside the draft so review means comparison, not memory.

Run the work through choose → baseline → practice → check → reflect → repeat. Stop when an authoritative input is missing, a high-risk claim lacks evidence, private material cannot be safely removed, or the proposed action exceeds the permission granted. Escalation is successful workflow behavior, not model failure.

Common framing mistakes are collecting prompts without testing; changing tool and task simultaneously; counting speed while quality falls; skipping reflection; automating before understanding. Prevent them by writing a one-paragraph job card: user, decision, deliverable, source of truth, constraints, reviewer, and stop condition. This card becomes the anchor for every later prompt.