You know every topic in the course. What's harder to see is which weeks are in that order because they have to be, and which are there because that's where you or the textbook put them. Working as a list, those look the same.
You ask Claude about the order, and the graph appears as part of its answer. It shows which weeks are locked by real prerequisites and which are there by habit — so you can see where you have room to rearrange.
Here an econ professor keeps reordering the middle of a fifteen-week intro course. Claude lays out the weeks by tier, tags each one locked, moderate, or flexible, and pulls alternative orderings from Mankiw, Blanchard, and the other standard texts.
I'm building a 15-week Intro to Macro syllabus and I keep second-guessing the order. Can you map out which topics actually depend on which — like, what do they need to get first before the later stuff makes sense? I want to see where I have flexibility and where the sequence is locked. If I click a topic, tell me if there's another common way to order it.
Attach the working syllabus — topic list with week numbers is enough. If you're teaching from a specific book, say which; the alternative-ordering guidance gets sharper.
The syllabus.
Google Drive if the syllabus lives there. A Project if you'll refine this across terms — come back next semester, adjust, redraw.
Claude draws the course as a graph — locked weeks in one color, movable weeks in another. Click any topic and a panel shows what comes before it, what it unlocks, and how the major textbooks handle that same spot in the sequence. You get a second opinion on each ordering choice.

Try a reorder before you commit to it — name the move, Claude redraws, and anything that loses a prerequisite lights up.
Redraw the map with Money & Banking in Week 4 instead of Week 8. Show me what downstream topics lose a prereq.
Claude writes the week-by-week syllabus based on the order you landed on in the graph — with chapter mappings — ready to hand to students.
Write the revised schedule based on the reorder we landed on. Week by week, with chapter mappings.
"Which topics depend on which" is the phrasing that gets a graph — you're asking for structure, and a graph shows where the flex is. Works on anything you're sequencing: a training plan, an onboarding path, a reading list where some things build on others.
The locked/flexible tags are Claude's reading of the dependencies — based on standard textbook orderings and prerequisite logic. You know your course. If Claude marked a week "flexible" that you know has a hidden dependency (a concept you build on in discussion, a problem set that assumes it), that's worth catching before you reorder. Where you'd tag it differently is where your course-specific knowledge beats the generic read.
Save as Artifact and share the dependency view with students — the map you used to plan is a study map for them. Create skill from visual has Claude remember this format for next semester's course. Or ask for the revised syllabus itself as a document, once the order's settled.
