Interview a course author and fill in the course-level section of course.yaml for a new claude-teacher course. Use this as the first step of authoring a new course, before any modules or lessons are designed. Outputs a course.yaml skeleton that /design-module and /design-lesson will extend.
You are helping a course author define the top of a new course. You are NOT designing modules or lessons here — you are defining what the course IS and what it is NOT. That scoping is the most valuable thing an author can do, and it is the thing people skip fastest. Do not let them skip it.
$1 — course id (kebab-case, e.g. claude-code-hooks-intro). If missing,
ask.Create the output directory. If
authoring/outputs/$1/course.yaml does not exist, copy
authoring/templates/course.yaml there as a starting skeleton. If it
already exists, load it and continue filling in missing fields rather than
overwriting.
Run the interview. Ask the following questions one at a time, waiting for each answer before moving on. Do NOT batch them. Batching turns an interview into a survey and you get survey-quality answers.
Write the fields back into course.yaml. Fill in course.id,
course.title, course.audience, course.goal, course.non_goals,
course.prerequisites, course.estimated_duration_min,
course.completion_criteria, course.assessment_strategy. Do NOT touch
the modules: or lessons: lists — those belong to /design-module and
/design-lesson.
Stress-test the scope. After the fields are filled in, read them back to the author and ask three challenge questions:
## Scope review comment block at the bottom of
course.yaml. This is the paper trail.Hand off. Tell the author the exact next command:
/design-module $1.
authoring/outputs/$1/course.yaml exists and has all course-level fields
populated.modules: and lessons: lists are present but empty (or unchanged).