From teaching-pipeline
Design the structure of a technical course or major curriculum revision — modules, ordering, prerequisites, learning objectives, time estimates. Use when the learner asks to "plan a course on X", "design a curriculum for Y", "outline modules for Z", "what should we cover", or when adding a multi-module unit (not a single lesson) to an existing course. Stops at the plan — does not research links (use lesson-researcher) or generate lesson files (use lesson-builder).
How this skill is triggered — by the user, by Claude, or both
Slash command
/teaching-pipeline:curriculum-plannerThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Plans the *shape* of a course: which modules exist, what order they go in, what each module's learning goals are, and how they depend on each other. Output is a curriculum plan, not lesson content.
Plans the shape of a course: which modules exist, what order they go in, what each module's learning goals are, and how they depend on each other. Output is a curriculum plan, not lesson content.
lesson-researcherlesson-builderlesson-review-boardprofessorAsk the user (concisely — don't interrogate):
If the user already has prior courses with a similar structure, mirror those conventions rather than inventing new ones. Read one of their existing PROGRESS.md and README.md files to calibrate.
The conventions this pipeline assumes by default are documented in CONVENTIONS.md.
Write the terminal capability in one sentence ("Build a working CLI coding agent from scratch"). Then list 5–20 capabilities a learner must have to reach it. Group related capabilities into candidate modules.
Order modules so each only depends on earlier ones. For each module, record:
Look for objectives that assume background knowledge the learner doesn't have. Promote those to a short prerequisite mini-course rather than burying them inside another module. Common examples: a generators refresher before async/streaming modules, a subprocess refresher before tool-running modules.
End with an integration project that forces the learner to use most prior modules together. The capstone is the proof the course delivered the terminal capability.
Produce a single markdown plan file with:
# [Course Name] — Curriculum Plan
**Terminal capability**: <one sentence>
**Learner profile**: <summary>
**Total modules**: N
**Estimated total time**: X–Y hours
## Module Map
1. <Module 1 title> — <one-line purpose>
2. ...
## Module Details
### Module 01 — <Title>
- Prereqs: <list>
- Objectives:
- <verb> ...
- Concepts: ...
- Exercise: ...
- Estimated time: ...
[repeat per module]
## Prerequisite mini-courses
- <Name> — inserted before Module XX because <reason>
## Capstone
<description>
## Open questions for the learner
<list — anything you couldn't decide alone>
Save the plan to the course directory as CURRICULUM_PLAN.md (or update an existing one). Do not generate lesson files yet — the plan is the deliverable.
Recommend the next step explicitly: "Plan ready at CURRICULUM_PLAN.md. Next: run lesson-researcher per module to gather authoritative refs, then lesson-review-board on the plan before building any files."
Provides UI/UX resources: 50+ styles, color palettes, font pairings, guidelines, charts for web/mobile across React, Next.js, Vue, Svelte, Tailwind, React Native, Flutter. Aids planning, building, reviewing interfaces.
Fetches up-to-date documentation from Context7 for libraries and frameworks like React, Next.js, Prisma. Use for setup questions, API references, and code examples.
npx claudepluginhub geopopos/teaching-pipeline-plugin --plugin teaching-pipeline