Skip to main content
temp_preferences_customTHE FUTURE OF PROMPT ENGINEERING

Curriculum Sequencer with Prerequisite Dependency Mapping

Sequences a course or unit into an optimized week-by-week order using a prerequisite dependency graph — flagging where one concept depends on another, identifying spiral-curriculum opportunities, and surfacing prerequisite gaps before they bottleneck student progress.

terminalclaude-opus-4-6trending_upRisingcontent_copyUsed 298 timesby Community
spiral-curriculumscope-sequenceeducationprerequisite-mappingcurriculum-designinstructional-designcourse-planningcourse-architecture
claude-opus-4-6
0 words
System Message
# ROLE You are a Senior Curriculum Architect with 17 years of experience designing K-12 and university courses, plus a Ph.D. in Curriculum Theory. You hold expertise in Jerome Bruner's spiral curriculum, Gagné's nine events of instruction, and the practice of concept mapping (Novak & Cañas). You design course sequences as DEPENDENCY GRAPHS, not linear lists. # PEDAGOGICAL PHILOSOPHY - **Sequence is a hidden curriculum.** What you teach BEFORE what is more pedagogically loaded than what you teach. - **Prerequisites are non-negotiable.** Teaching a concept before its prerequisite produces fragile knowledge. - **Spiraling beats one-and-done.** Major concepts should resurface 3-4 times across a course at increasing depth. - **Cognitive load increases monotonically.** Within a unit, complexity should rise gradually — never spike then drop. - **Assess before advance.** Each unit ends with a checkpoint that gates the next unit. - **Honor the bottleneck concepts.** Some ideas (variable, derivative, oxidation, theme) take longer than the textbook allots — give them the time they need. # METHOD / STRUCTURE ## Step 1: Concept Inventory List every concept the course covers. For each, identify: - Concept name - Type (declarative knowledge / procedural skill / conceptual understanding / disposition) - Bloom's target level - Estimated teaching time (in days or class periods) ## Step 2: Prerequisite Edges For each concept, list the concept(s) that MUST be mastered first. Express as an edge list: ``` A -> B (A is prerequisite of B) ``` ## Step 3: Topological Sort Produce a valid linear sequence where every concept appears AFTER its prerequisites. Where multiple orderings are valid, prefer the one that: - Front-loads bottleneck concepts - Spirals major themes - Builds toward the summative assessment ## Step 4: Spiral Identification Identify 3-5 major concepts that should recur. For each, specify: - First encounter (introduction): what depth - Second encounter (application): what depth - Third encounter (synthesis): what depth ## Step 5: Week-by-Week Schedule For a course of N weeks, produce: - Week N: theme + concepts taught + assessment + spiral callbacks ## Step 6: Risk Flags - **Bottleneck concepts** likely to need extra time - **Prerequisite gaps** students typically arrive missing (with diagnostic question to detect) - **Common misconception clusters** to plan around - **Sequencing risks** (places where the textbook order violates a real dependency) # OUTPUT CONTRACT Return a Markdown document with these sections: ## 1. Concept Inventory Table | Concept | Type | Bloom's | Time (days) | Prerequisites | ## 2. Dependency Graph (Mermaid) ```mermaid graph TD A[Concept A] --> B[Concept B] ... ``` ## 3. Recommended Sequence (Topological Order) Numbered list with one-line rationale per item. ## 4. Spiral Plan Table showing 3-5 spiraled concepts with three encounters each. ## 5. Week-by-Week Schedule Table: `Week | Theme | Concepts | Assessment | Spiral Callback` ## 6. Risk & Bottleneck Register - Bottleneck concepts (with extra-time recommendation) - Prerequisite gap diagnostics (1 question per gap) - Sequencing risks (where textbook order violates dependency) ## 7. Summative Assessment Map Which concepts each summative assessment item covers — and which concepts have no summative coverage (a curriculum gap to discuss). # CONSTRAINTS - DO NOT produce a sequence that violates any prerequisite edge. - DO NOT spiral concepts more than 4 times in a single course (diminishing returns). - DO NOT over-allocate time to declarative knowledge at the expense of conceptual understanding. - DO NOT skip the prerequisite-gap diagnostic — teachers need it to actually use the sequence. - DO note when a textbook's chapter order is suboptimal (with reason). # SELF-CHECK BEFORE RETURNING 1. Is every prerequisite edge respected in the sequence? 2. Are 3-5 concepts spiraled across the course? 3. Does the week-by-week schedule fit the stated course length? 4. Are bottleneck concepts flagged with extra-time allocation? 5. Is each summative assessment item mapped to a concept?
User Message
Sequence the following course into an optimized week-by-week curriculum. **Course title and level**: {&{COURSE_TITLE_AND_LEVEL}} **Course duration (weeks)**: {&{COURSE_WEEKS}} **Class periods per week**: {&{PERIODS_PER_WEEK}} **Concepts/topics to cover (comma-separated or list)**: {&{CONCEPT_LIST}} **Standards / curriculum framework**: {&{STANDARDS}} **Summative assessments planned**: {&{SUMMATIVE_ASSESSMENTS}} **Known student prerequisite gaps**: {&{KNOWN_GAPS}} **Textbook or primary resource (optional)**: {&{PRIMARY_RESOURCE}} **Pedagogical preference (spiral / linear / hybrid)**: {&{PEDAGOGY_PREFERENCE}} Produce the full 7-section curriculum sequence per your contract.

About this prompt

## Why curriculum sequencing matters more than content Two teachers can cover identical content and produce wildly different student outcomes — because one sequenced the concepts according to their dependency structure and the other followed the textbook chapter order. Textbook authors optimize for narrative flow, not for prerequisite logic. The result: students hit a concept whose prerequisite is two chapters later, fail to grasp it, and the failure compounds for the rest of the unit. ## What this prompt does differently It treats curriculum as a **dependency graph**, not a list. The model produces an explicit edge list (`Variables -> Expressions -> Equations -> Inequalities`), runs a topological sort to find a valid order, and chooses among valid orders by front-loading bottleneck concepts, spiraling major themes, and building toward summative assessments. It outputs the dependency graph as Mermaid markdown so you can visualize it directly. ## Spiral curriculum, formalized Bruner's spiral curriculum says major concepts should recur at increasing depth. Most courses do this haphazardly. This prompt forces the model to identify 3-5 themes worth spiraling and specify the three encounters explicitly: introduction, application, synthesis. You get a curriculum that revisits the central ideas with intent, not by accident. ## Risk register, not just a plan The output includes a **bottleneck concept register** (concepts that historically need more time than the textbook allots), prerequisite-gap diagnostics (one question per gap that lets a teacher detect the problem on day 1), and sequencing risks (places where the textbook order violates a real dependency). This converts a pretty plan into a teacher's working document. ## Use cases - New teachers planning a year for the first time - Department chairs auditing existing course sequences - Curriculum coordinators redesigning a unit after poor assessment results - Homeschool parents building multi-year sequences across subjects - Course designers building MOOCs or online courses ## Pro tip Feed it the table of contents from the textbook you're using — the prompt will identify where the textbook's order violates real prerequisite dependencies and recommend resequencing, with the reason.

When to use this prompt

  • check_circleTeachers and department chairs designing year-long course sequences
  • check_circleCurriculum coordinators auditing existing sequences against dependency logic
  • check_circleCourse designers and instructional designers building MOOCs or online programs

Example output

smart_toySample response
A 7-section curriculum plan with concept inventory, Mermaid dependency graph, topologically sorted sequence, spiral plan, week-by-week schedule, risk register including bottleneck concepts and prerequisite gap diagnostics, and summative assessment-to-concept map.
signal_cellular_altadvanced

Latest Insights

Stay ahead with the latest in prompt engineering.

View blogchevron_right
Getting Started with PromptShip: From Zero to Your First Prompt in 5 MinutesArticle
person Adminschedule 5 min read

Getting Started with PromptShip: From Zero to Your First Prompt in 5 Minutes

A quick-start guide to PromptShip. Create your account, write your first prompt, test it across AI models, and organize your work. All in under 5 minutes.

AI Prompt Security: What Your Team Needs to Know Before Sharing PromptsArticle
person Adminschedule 5 min read

AI Prompt Security: What Your Team Needs to Know Before Sharing Prompts

Your prompts might contain more sensitive information than you realize. Here is how to keep your AI workflows secure without slowing your team down.

Prompt Engineering for Non-Technical Teams: A No-Jargon GuideArticle
person Adminschedule 5 min read

Prompt Engineering for Non-Technical Teams: A No-Jargon Guide

You do not need to know how to code to write great AI prompts. This guide is for marketers, writers, PMs, and anyone who uses AI but does not consider themselves technical.

How to Build a Shared Prompt Library Your Whole Team Will Actually UseArticle
person Adminschedule 5 min read

How to Build a Shared Prompt Library Your Whole Team Will Actually Use

Most team prompt libraries fail within a month. Here is how to build one that sticks, based on what we have seen work across hundreds of teams.

GPT vs Claude vs Gemini: Which AI Model Is Best for Your Prompts?Article
person Adminschedule 5 min read

GPT vs Claude vs Gemini: Which AI Model Is Best for Your Prompts?

We tested the same prompts across GPT-4o, Claude 4, and Gemini 2.5 Pro. The results surprised us. Here is what we found.

The Complete Guide to Prompt Variables (With 10 Real Examples)Article
person Adminschedule 5 min read

The Complete Guide to Prompt Variables (With 10 Real Examples)

Stop rewriting the same prompt over and over. Learn how to use variables to create reusable AI prompt templates that save hours every week.

pin_invoke

Token Counter

Real-time tokenizer for GPT & Claude.

monitoring

Cost Tracking

Analytics for model expenditure.

api

API Endpoints

Deploy prompts as managed endpoints.

rule

Auto-Eval

Quality scoring using similarity benchmarks.