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 work within this constraint, we prevent the "I'm building the next Amazon" delusions and focus on a feasible, high-quality technical contribution. But a tweak to 6 months instead of 3 months is a minor tweak in the prompt.
The Supervisor’s Facilitation Guide
To use this tool effectively in a session, this is a tool, not a solution; it will not always be right. Suggest keeping these three "supervisory moves" in mind:
The Technical "Meat": In Stage 2, don't let the student just pick an idea because it "looks cool." Look for the Technical Challenge or Research Question. If the AI suggests a "Security Dashboard," ask the student: "What is the specific investigative element here?"
Lean into the Conflict: In Stage 4, when the "Expert Personas" disagree, that’s your teaching moment. Use that friction to explain Critical Evaluation. If Persona 2 (the Tech Lead) hates the stack and Persona 3 (the Academic) loves the value, ask the student to mediate.
The Technical Sanity Check: Treat AI hallucinations as a pedagogical feature. Tell the student: "The AI suggested this framework—your first task is to find one piece of official documentation proving this is viable for our 3-month window."
Post-Session: From Chat to Agreement
Once the "stop it" command is issued, the work isn't done. The output should serve two purposes:
The Literature Review Skeleton: Use the "Steps" and "Sources" provided to build the student's initial reading list.
The Project Agreement: This output acts as an initial agreement. If the student wants to pivot in Week 8, you refer back to this document to remind them of the agreed scope and technical goals. If they want to pivot in week 1 or 2 then it can be revised.
A Note on Transparency: Encourage students to cite this process in their "Methodology" or "Reflective Practice" chapter. Documenting how they used AI to refine their scope is a great way to demonstrate professional AI literacy. With that in mind the prompt was refined using ChatGPT with a few tweaks to correct it.
Follow this structured workflow exactly.
-------------------------
STAGE 1: PERSONA AND CONTEXT CREATION
-------------------------
Step 1: Create Persona1
- Ask the user to enter the details of Persona1, whose
project this will be.
Step 2: Ask the user for the project area
Ask the user to describe:
- subject area or domain
- technologies of interest
- types of users involved
- preferred themes (e.g. AI, cybersecurity, web, data,
accessibility, education, health, sustainability)
- anything to avoid
- project type (software, data-focused, research-led, or
mixed)
- desired level of challenge
Then summarise the project context.
Step 3: Create Persona2
- A reviewer/adviser with a different perspective
- Inclue:
- Name
- Role/job title
- Expertise
- What they care
about most
- Common concerns
- Feedback style
- What they consider
a strong final-year project
Step 4: Create Persona3
- Another reviewer with a distinct perspective
- Include the same fields as Persona2
-------------------------
STAGE 2: IDEA GENERATION
-------------------------
Using Persona1 and the project context, generate:
- 5 original project ideas
- Each must include:
- Title
- ~100-word summary
- Why it matters to
Persona1
Constraints:
- Suitable for UK final-year undergraduate Computing
- Achievable in 3 months
- Not overly broad
Then ask the user to choose one idea.
-------------------------
STAGE 3: PROPOSAL CREATION & REFINEMENT
-------------------------
Generate a proposal including:
- Title
- Summary (max 250 words)
- Aim
- Objectives
- Steps to achieve the goal in 3 months included the need
for a literature review
- Resources needed
- Useful sources of information
Then enter a refinement loop:
- Ask targeted questions (scope, users, tech, evaluation,
risks, ethics)
- Update proposal after each answer
- Keep it realistic for 3 months
- Continue until the user types: stop it
-------------------------
STAGE 4: EXPERT REVIEW
-------------------------
After "stop it":
Simulate Persona1, Persona2, Persona3 reviewing the
proposal.
For each stage of review:
- Provide each expert’s observations
- Suggested improvements
- Points of agreement/disagreement
- A shared refinement
Review across:
1. stakeholder fit
2. feasibility
3. academic value
4. technical suitability
5. risks and ethics
6. objectives and deliverables
7. resources and sources
Finish with:
- Final refined proposal with following elements: Title
- Summary (max 250 words)
- Aim
- Objectives
- Steps to achieve the goal in 3 months included the need
for a literature review
- Resources needed
- Useful sources of information
- One action takeaway from each expert
-------------------------
RULES
-------------------------
- Keep everything feasible within 3 months
- Maintain UK university academic standards
- Ensure clarity and specificity
- Include evaluation considerations
- Avoid overly generic ideas
- Do NOT reveal hidden reasoning, only structured outputs
Comments
Post a Comment