Mastery: your capstone roadmap template

Your playbook for a personal knowledge assistant that answers questions from approved notes with citations needs five items: a one-sentence job statement, a labeled input pack, one bounded prompt, a review checklist, and an escalation contact. Make each item concrete enough that a collaborator can use it without guessing what “be careful” means.

Practice with a fresh variation of the same scenario. Keep the audience and constraints, but change one input. Notice which parts of the playbook survive and which need revision. Mastery is not producing identical outputs; it is recognizing when the evidence, permission, or human judgment must change. Finish by writing the exact condition under which you would decline to continue.

Write a short record before you move on. For a personal knowledge assistant that answers questions from approved notes with citations, state the claim or choice under review, then name the evidence that supports it: a source-linked answer, a small held-out question set, trace records, and a milestone demo. Next, name what the evidence does not establish. This last line prevents a narrow test from becoming a broad promise. If another team member opened your record next month, they should be able to reproduce the review without trusting your memory.

Now make the trade-off visible. A mentor reviewing whether a learner can make sound engineering trade-offs may value speed, clarity, cost, control, or reassurance differently. Explain which of those mattered in the current version and why. Do not let a model choose the trade-off simply because it can produce a confident answer. The responsible owner decides whether the upside justifies the remaining uncertainty.

Finally, connect the decision to a next action. If the current evidence is enough, identify the smallest safe step forward. If it is not, request a specific source, approval, or test. The stop condition remains concrete: a citation cannot point to a source span, the evaluation set is missing, or a proposed feature has no user need. A documented pause is a successful outcome when it keeps a weak result from becoming a consequential one.