Skip to main content

GenaI as co-author and more importantly as "Devil's Advocate"

In a companion post on context stacking, I came across an idea that stayed with me — and I wanted to explore it further.

This piece isn’t just about the final blog produced, but about the process behind creating it using generative AI (specifically, Claude.ai). Rather than using AI as a writing shortcut, I used it as a thinking partner — one that could challenge my assumptions, test my reasoning, and help strengthen the argument before anything was finalised.

What emerged was a structured workflow (shown below) that others can adopt when using AI to improve the rigour, not just their output. And it all starts with setting the context and the audience and telling the generative AI to pick it apart.


The process:

Before using Generative AI: Two drafts were produced, and the second draft went through this final process, as described by claude.ai here.

Here's the workflow we followed:

1. Critical Reading and Initial Diagnosis

We started with a close reading of your original draft, analysing what was working well structurally and argumentatively, and identifying the key weaknesses an academic reviewer would likely challenge — particularly the flipped classroom compliance problem you raised directly.

2. Devil's Advocate Questioning — Round One

Rather than moving straight to revision, we used structured devil's advocate questioning across four pressure points: the transferability of the central claim, the wrong mental model problem, academic displacement, and the equity argument. Each question was designed to find where the argument was exposed rather than where it was strong.

3. Iterative Stress-Testing — Multiple Rounds

Crucially, we didn't accept your first answers. Each response you gave was pushed harder in the next round — your answers generated new, more specific questions. This produced several iterations where the argument either strengthened genuinely or revealed honest limitations. Notably, when you challenged my assertion about academic workload lacking evidential basis, that exchange itself modelled the critical thinking the piece advocates.

4. Position Clarification on Key Tensions

Through this process several important clarifications emerged that weren't in the original draft: the champion fragility problem, the coordinated misconception risk, lived experience as embodied presence rather than purely knowledge, and most significantly the honest narrowing of your target audience from "all academics" to "student-centred module leaders with genuine autonomy."

5. Honest Scoping Decision

The pivotal moment was agreeing that the piece was most honestly a proof of concept argument for early adopters rather than a universal prescription — and recognising that this resolved the central contradiction between your equity argument and your actual audience.

6. Structural Redesign Before Drafting

Before writing a single word of the revised piece, we agreed a revised section architecture that mapped the new argument logic — ensuring the structure served the argument rather than retrofitting the argument into the original structure.

7. Drafting with Referenced Integration

Only then did we draft, integrating Biggs and Tang and Freeman et al. as gaps the conversation had specifically identified, and producing a piece that honestly names its scope in the subtitle rather than burying the limitation.


The meta-point worth noting

This workflow is essentially the context stacking methodology your piece advocates — applied to academic writing rather than lecture preparation. We built a model, stress-tested it against challenging questions, identified where it broke down, refined it, and only then committed it to final form. The process mirrored the argument


The bigger takeaway

This process highlights a more powerful way to use generative AI. Instead of treating it as a tool for faster writing, it can be used to improve how we think. By asking it to question, challenge, and probe our ideas, we can produce work that is more robust, more honest, and ultimately more useful. On a more personal note, it pushed me hard to think what I was actually thinking and meaning - it didn't give me the answers.

The inverted questioning and lots of multiple rounds were the key strengths of the approach at each stage/round. I was asked some insightful but critical questions. I did want it to give me the answers but push me to address (and face) critical questions.


All opinions in this blog are the Author's and should not in any way be seen as reflecting the views of any organisation the Author has any association with. Twitter @scottturneruon

Comments

Popular posts from this blog

Using an LLM to Find Themes using Thematic Analysis in an Academic Career

B rief recap In an earlier post, “Same prompt, four AIs: why answers aren’t always the same” , I looked at what happened when the same prompt was given to four different LLMs. Unsurprisingly, perhaps, the answers were not identical. That raised an interesting follow-on question: what was the prompt actually trying to do? The answer is that it was trying to support a form of thematic analysis. In that case, the object of analysis was an academic profile, including my Google Scholar profile. The version I discuss here is a modified prompt, used with Claude.ai, where I uploaded a CV and asked the system to find other appropriate public resources connected with a named person and institution. The aim was not simply to summarise the CV, but to identify visible and less visible themes across a whole career. Why use thematic analysis? Thematic analysis is widely used by academics, especially in qualitative research. Braun and Clarke’s well-known paper, Using thematic analysis in psy...

Prompt Engineering, Context Engineering and Agentic AI in Higher Education: A Short Briefing

AI in Education Prompt engineering, context engineering and agentic AI are often used interchangeably, but the literature treats them as distinct. Prompt engineering concerns crafting effective single instructions to a model (Glean, 2026). Context engineering is the broader discipline of designing and managing the entire informational environment around a model—memory, retrieval, tool outputs and conversation state—rather than a one-off instruction (Abstracta, 2026); prompt engineering operates within the context window, while context engineering determines what fills it (arXiv:2606.12422, 2026). Agentic AI describes systems that plan and execute multi-step tasks with delegated autonomy, raising organisational questions of accountability rather than purely technical ones (MIT Sloan, 2026; Palo Alto Networks, 2026). There is genuine debate about prompt engineering's durability. IEEE Spectrum (2025) reported research suggesting prompting is increasingly performed by models themse...

AI as a Mirror: Transforming Vague Student Ideas into a More Rigorous Project Agreement

The Problem: The "Generic App" and the "Time Sink" We’ve all been there: a student walks into a 1-to-1 with a vague desire to "do something with AI" or "build a fitness app." You spend 45 minutes trying to find a technical "hook" that justifies a Level 6 or Level 7 grade, only for the student to drift back into "CRUD app" territory by week three. The Philosophy: AI as a Mirror Instead of you doing the heavy lifting, this workflow uses AI as a Mirror . It reflects the student’s own skills and career goals back to them, but with the structural rigour of a virtual supervisory team. It’s not about the AI "giving" the idea; it’s about the AI forcing the student to defend and refine their own concepts until they hold water. The Framework: 3 Months of Rigour This prompt is specifically designed for intensive/conversion MSc or summer capstone projects . It assumes a tight 12-week implementation window. By forcing the AI to w...