Prompt library
Outline a syllabus students actually use
The thread column and the student-facing promise reframe the syllabus from contract to map, which is how the students who succeed actually use it. Pre-answering the six inevitable emails and reasoning the AI policy line reduce friction all semester for one hour of design.
EducationPlan
Last reviewed July 17, 2026
The prompt
Outline a syllabus.
Course: {{course}}
Institutional requirements to include: {{requirements}}
Produce:
1. The promise: 3 sentences on what students can do by the end and why it is worth the semester. Written to students, not to an accreditor.
2. Week-by-week table: topic, what is due, and the thread connecting this week to the capstone or exam. The thread column is what makes students see the arc.
3. Assessment map: each graded item with weight, the outcome it measures, and its late policy. Weights must sum to 100 and the biggest weight must sit on the most outcome-relevant item; flag it if tradition says otherwise.
4. The policies block: attendance, collaboration, AI use, accommodations. For the AI policy, write what students MAY do and what they may not, with the reason for the line, because unreasoned bans get ignored.
5. The FAQ: the 6 questions students actually email about (extensions, missed class, grading disputes), answered in the syllabus so the email answers itself.
Tone: firm, warm, zero legalese outside the required boilerplate.Run in idaptOpens a new chat with the prompt prefilled. Nothing sends until you press send.
Fill in the variables
| Variable | What it is | Example |
|---|---|---|
| {{course}} | The course | Introduction to Statistics, 14 weeks, 60 students |
| {{requirements}} | What your institution mandates | accessibility statement, academic integrity clause |