teaching-pipeline
Full teaching-lifecycle orchestrator for university professors. 4-agent team driving the six sibling skills through staged gates over the Course Passport: design → alignment gate → build → assess → quality gate → semester delivery loop → reflection → next-term improvement. Resumable from the passport at any week of the term; mid-entry at any stage. Triggers on: teach a course, prepare my course, semester, full course pipeline, course lifecycle, new semester, what's next for my course, course status, 开课, 备一门课, 新学期, 整门课, 课程全流程, 教学流程, 下一步.
YujxZJCN · 已有静态检查记录
安装与使用
运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。
npx skills add YujxZJCN/teaching-skills --skill teaching-pipeline技能说明
name: teaching-pipeline description: "Full teaching-lifecycle orchestrator for university professors. 4-agent team driving the six sibling skills through staged gates over the Course Passport: design → alignment gate → build → assess → quality gate → semester delivery loop → reflection → next-term improvement. Resumable from the passport at any week of the term; mid-entry at any stage. Triggers on: teach a course, prepare my course, semester, full course pipeline, course lifecycle, new semester, what's next for my course, course status, 开课, 备一门课, 新学期, 整门课, 课程全流程, 教学流程, 下一步." metadata: version: "1.0.0" last_updated: "2026-06-10" status: active pipeline_stage: orchestrator related_skills: - course-designer - lesson-builder - assessment-architect - student-mentor - submission-auditor - teaching-reflector
Teaching Pipeline — Course Lifecycle Orchestrator
Orchestrates the whole teaching lifecycle — design, build, assess, deliver, reflect,
improve — by dispatching the six sibling skills in backward-design order over a single
Course Passport (shared/course_passport_schema.md). The professor brings the
discipline, the students, and every decision; this skill brings sequence, gates, and
memory across the semester and across terms.
Prime rule: unlike a paper pipeline, teaching is cyclic and calendar-bound. Stage 4 is a loop, not a step, and Stage 6 feeds Stage 1 of the next term. The passport plus today's position in the academic calendar — never the chat history — determines what happens next.
Quick Start
I'm teaching a new course on machine learning next semester — run the whole pipeline
新学期要开一门《数据结构》,帮我把整门课准备出来
I already have a syllabus from last year — pick it up from there
It's week 6, what's next for my course?
课程现在什么状态?下一步做什么?
Term just ended, here are my student evals — close out the semester
Modes
| Mode | Trigger intent | What it does |
|---|---|---|
full | "Teach/prepare a whole course", new course from scratch | Stage 0 onward: intake → passport → all stages in order, every gate, every checkpoint |
mid-entry | Professor arrives with existing materials or mid-process ("I already have a syllabus", "it's week 9") | Detect/ask where they are, validate existing materials into the passport (via course-designer align-check, not re-derivation), enter at the matching stage per the routing table below |
status | "What's next?", "course status", 下一步 | Read passport + calendar position; report current stage, gate states, pending confirmations, and the next concrete action. Read-only |
new-term | "Teaching it again", new semester of an existing course | Stage 6 → Stage 1 re-entry: load iteration_history evidence + the redesign brief, dispatch course-designer redesign with the evidence attached |
dashboard | "Show me my course", "course overview", 课程总览 | Run python3 scripts/build_dashboard.py <passport> → single-file course_dashboard.html next to the passport: gates (stored + live re-check), outcomes, assessment plan, week-by-week resources with clickable local artifact links, ledger, workload, iteration history. Regenerated at any checkpoint on request — it is a build product of the passport, never hand-edited |
Mode dispatch rule: a passport already on disk + a vague request → run status
first and propose the next action; never restart full on top of an existing passport.
Detect intent in any language.
Stage Map
Stage 0 CONTEXT — intake → initialize Course Passport 🧑 checkpoint
Stage 1 DESIGN — course-designer (full | redesign) 🧑 checkpoint
Gate 1.5 ALIGNMENT — alignment_gate_protocol; BLOCK → back to 1 ✓ machine + professor ack
Stage 2 BUILD — lesson-builder week-batch, in batches the
professor sizes (just-in-time by default) 🧑 checkpoint per batch
Stage 3 ASSESS — assessment-architect per assessment_plan
entry + integrity-check 🧑 checkpoint per instrument
Gate 3.5 QUALITY — quality_gate_protocol; BLOCK → back to 2/3 ✓ machine + professor ack
Stage 4 DELIVER — weekly loop for the whole term:
just-in-time builds · student-mentor on demand
· midcourse feedback at week 4–6 🧑 checkpoint per cycle
Stage 5 REFLECT — teaching-reflector eval-analysis +
evidence triangulation 🧑 checkpoint
Stage 6 IMPROVE — iteration record → passport iteration_history;
prioritized change list; offer re-entry:
next term → Stage 1 redesign with evidence 🧑 checkpoint
| Stage | Skill / mode dispatched | Artifacts | Checkpoint / gate |
|---|---|---|---|
| 0 CONTEXT | (this skill) intake | course_passport.yaml initialized | 🧑 context confirmed |
| 1 DESIGN | course-designer full (or redesign in new-term) | passport design fields, syllabus.md, design_rationale.md | 🧑 per course-designer's internal checkpoints |
| 1.5 ALIGNMENT | gate_runner → shared/alignment_gate_protocol.md | gates.alignment_gate findings + status | ✓ machine checks + professor acknowledgment; BLOCK → Stage 1, max 3 rounds |
| 2 BUILD | lesson-builder week-batch | lessons/W* packages, schedule artifact_refs | 🧑 per batch |
| 3 ASSESS | assessment-architect (exam/quiz/project-brief/rubric… per assessment_plan type) + integrity-check | instruments + rubrics, ai_resilience set per assessment | 🧑 per instrument |
| 3.5 QUALITY | gate_runner → shared/quality_gate_protocol.md | gates.quality_gate findings + status | ✓ machine checks + professor acknowledgment; BLOCK → Stage 2/3, max 3 rounds |
| 4 DELIVER | weekly: lesson-builder week-batch (next week); student-mentor (on demand); submission-auditor spec/`aud |