Analytics and advertising cookies

Google Analytics, Vercel Web Analytics, Leadsy and the TikTok Pixel stay off until you accept. The help chat starts once you have chosen. The scheduling button starts once you have chosen. Read our Privacy Policy.

Skip to content
StellarFirmStellarFirm
Book a demoJoin the waitlist
Mission manual
Esc

Type a word to search every page. Try , or .

Module 04 · Company playbooks

University

A plan for a university or a teaching lab: the Teacher plans courses and tutors students, and the Scientist backs the research.

View as Markdown
On this page

StellarFirm for universities puts two AI Agent Assistants first: the Teacher and the Scientist. The Teacher prepares your courses and tutors your students. The Scientist backs the research behind them. You are the CEO: the instructor or the head of the lab. You approve every email, calendar hold, and file that leaves the chat.

Who this is for#

CompanyA university department, a school, a teaching team, or a teaching and research lab
Team size1 to 50
Main goalSpend less time preparing material and more time with students and research
Start withOne Teacher for your main course, then a Scientist for the research group
Biggest riskA student handing in work the assistant wrote, or an unchecked solution reaching a class

Your assistants#

AssistantRole in this plan
TeacherCourse syllabi, lesson plans, worked examples, exercises with checked solutions, quizzes and exams, rubrics and feedback, slides and handouts in LaTeX, and one-to-one tutoring
ScientistLiterature searches with checked sources, experiment plans, symbolic and numerical checks, reproducible analyses, and papers in LaTeX

Hire a Teacher per subject if you teach more than one, for example a programming teacher and a mathematics teacher, each with its own focus.

Suggested house rules#

Text
House rules
1. The Teacher gives hints before answers. Full solutions only when I ask for them.
2. The Teacher never writes graded work for a student to hand in.
3. Every solution, example, and computation is checked before it is shown.
4. The Scientist never invents a result, a source, or a citation, and never calls a conjecture proved.
5. Emails to students, calendar holds, and files saved to our drive wait for my Approve.
6. Course policies and grades come from me. The assistants never make them up.

Preflight#

Launch: Day 1#

  1. Plan one lesson. Start with the next class you teach.
PromptPlan a lesson
Teacher, plan a [length] lesson on [topic] for [course and level]. Give learning outcomes, the order of activities, one worked example, and a short check for understanding at the end.
  1. Write exercises with checked solutions.
PromptExercises with solutions
Teacher, write [number] exercises on [topic] for [course], from easy to hard. Check every solution before you show it, and give a hint for each one.
  1. Start the research brief.
PromptResearch brief
Scientist, write a research brief on [question]: what is known, the key papers with their sources, the open problems, and what we could test first.
  1. Approve what goes out. Anything sent to students or saved to your drive waits in Approvals.

First week#

PromptCourse syllabus
Teacher, draft a syllabus for [course]: learning outcomes, a week by week plan, readings, and how students are assessed. Leave the grading policy for me to fill in.
PromptQuiz and rubric
Teacher, write a [length] quiz on [topics] with a marking rubric and model answers. Check every answer.
PromptSlides in LaTeX
Teacher, make lecture slides in LaTeX for [topic], with one worked example per idea. Publish them so I can edit them beside the chat.
PromptTutor a student
Teacher, tutor me as if I were a student in [course] who is stuck on [problem]. Ask me questions and give one hint at a time. Do not give the full answer.
PromptLiterature search
Scientist, find the most cited and the most recent work on [topic]. Give each source with a link, one line on what it shows, and say which you could not check.

Steady orbit#

  • Every week. Ask the Teacher for next week's lesson and exercises, and read them before class.
  • After every assignment. Ask for feedback drafts against your rubric, then edit them yourself.
  • Every month. Ask the Scientist for a literature update on your group's topics.
  • Every term. Ask the Teacher to update the syllabus from what worked.

You can set the weekly preparation as a routine, so it is waiting for you every Monday.

PromptFrom research to teaching
Scientist, summarize our latest result on [topic] in plain words. Teacher, turn that summary into a short lesson for [course].

The rest of the team#

The Teacher and the Scientist lead here, and the other assistants are there when you need them:

  • Coder: builds a course site, a small app for a lab exercise, or turns an analysis into a tool.
  • Copywriter: helps you edit grant text, announcements, and papers in your own words.

Pitfalls#

  • Answers instead of hints. Keep "hints before answers" in your house rules, and ask for full solutions only for your own answer keys.
  • Unchecked material. Read every exam and answer key before it goes to a class.
  • Made-up policies. Give the Teacher your real course policies and grading scheme. It never invents one.
  • One Teacher for everything. Hire a Teacher per subject so each one keeps its own focus.