Creative extension
Take something you've just learned and apply it somewhere nobody asked you to, which is the cheapest available test of whether you understood it.
Learning that only works inside tonight’s conversation has not transferred yet.
Draft and critique in loops. Invent a constraint that actually binds. Carry an idea into a new context and see what breaks.
This family is for essays, design briefs, long projects, and the moment after “I kind of get it” when you still cannot make anything.
Take something you've just learned and apply it somewhere nobody asked you to, which is the cheapest available test of whether you understood it.
Borrow a working framework from a field you know into one you're working in, and tell whether the import is doing real work or just sounding good.
Run several rounds of structured critique on your own work, and come out the other side having improved your writing rather than having had it improved for you.
Grade your own work against the criteria it will actually be graded by, before you hand it in, and find the gap between what you think you've produced and what's on the page.
Solve a new problem by finding a structurally similar solved one, mapping roles deliberately, then transferring the solution method without copying surface features.
Build a growing structured record you can reconstruct unaided, notes that compound, instead of chat logs that vanish.
Turn a concept into a one-page teaching aid for a future student, then have it critiqued, because designing instruction exposes what you don't yet own.
Turn a vague interest into a question that can actually be answered in the space and time you have.
Extract the outline of a draft you've already written, and see the structure you actually produced rather than the one you intended.
Map a field's arguments and disagreements while verifying each source, so a "lit review" isn't a paraphrased pile of abstracts the model invented.
Have your proposed method attacked before you run it, so you fix design flaws on paper instead of after weeks of sunk cost.
Argue the outline before writing prose, so structure fights happen before you've invested in sentences you won't delete.
Review someone else's work to sharpen your own standards: training the evaluative eye you'll need on your next draft.
Predict the hardest questions on your work and prepare answers, so viva, defence, and audience Q&A stop being pure ambush.
Keep successive drafts and analyse how your own thinking changed, so revision becomes visible learning, not just cleanup.
Generate five to eight versions of the same piece, rank them, and articulate the criteria: training evaluation, not just production.
Deliver and get feedback on structure, pacing, and clarity, so the first audience isn't the one that grades you.
Work to a deliberately restrictive brief to force invention: using limits as a design tool rather than waiting for inspiration.
Invent restrictions on your own work that force you to understand it better than doing it the easy way ever would.
Work with a persistent companion across a long piece of work, keeping goals, decisions, and next actions coherent without handing authorship to the model.
Analyse how a writer achieves an effect, then attempt it, stealing craft on purpose instead of vaguely "reading good prose."
Have a body of work assessed for development over time, seeing trajectory and recurring weaknesses, not only the latest piece.
Invent deliberately silly constraints and create inside them: using play to open moves serious briefs sometimes block.