Curriculum Design

This is an OMH curriculum-design workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).

Why This Exists

curriculum-design makes outcomes, sequence, assessment, and constraints reviewable before materials or LMS work.

Do Not Use When

• The user wants an explanation of a supplied academic paper rather than a teachable sequence; use omh-paper-learning.
• The user needs a deck, workbook, PDF, or other exported learning artifact; route packaging to omh-materials-package after the curriculum is accepted.
• The user asks to create or publish an LMS course, enroll students, grade work, or change course settings; use omh-apps with explicit authorization and observed evidence.
• The user needs only a short rewrite or one isolated worksheet prompt, not curriculum structure; use omh-content-operator.

Examples

Good example:

• Prompt: Design a six-week onboarding curriculum with learning objectives and practical assessments for new support agents.
• Expected behavior: Prepare learner constraints, scope and sequence, learning objectives, assessments, and adaptation questions.
• Why: The request needs a teachable sequence and assessment plan rather than an LMS course or exported material.

Bad example:

• Prompt: Explain the attached machine-learning paper for a beginner.
• Expected behavior: Route to paper-learning, not curriculum-design.
• Why: A supplied paper explanation is not a curriculum-design request.

Completion Checklist

• The plan names goals, non-goals, assumptions, acceptance criteria, and verification shape.
• Draft recommendations, accepted decisions, and executor handoffs are separate states.
• Rejected options or unresolved tradeoffs are recorded before handoff.

Recovery Notes