Order modules so prerequisites precede dependents
Packaged know-how that tells an agent how to do a job well.
You might say…
“I'd written the advanced module before the foundational one — sequencing forces the question of what the learner needs to know before they can absorb what I'm teaching next.”
What it does
Proposes a module order where prerequisite knowledge is always taught before the concepts that depend on it, flagging circular dependencies or ordering ambiguities.
Trigger: Use after module clusters are defined, to lock in the learning path before setting pacing or designing assessments.
I/O: Named module clusters + learning outcomes → sequenced module order with prerequisite rationale
Recognise the problem?
The primitives are the commodity part. The fastest next step is a conversation about composing them into something that works for you.
Start a conversation