Course Scaffold

Scaffold a new course: $ARGUMENTS

Inputs

Parse the arguments for:

• slug (required) — e.g., mdna-primer
• title (required) — e.g., "mDNA Primer: Recovering the Genetics of Ecclesia"
• portal (optional) — one of: reframation, metanoia, mdna, mx, forgotten-ways

If any required input is missing, ask the user.

Before Starting

1. Read _docs/COURSE_STRATEGY.md — the authoritative reference for the 8-week structure and canonical section order
2. Read src/lib/database/schema.ts — find courses, courseWeeks, courseLessons table definitions
3. Read src/lib/schemas/course-learn.ts — understand SECTION_TYPES
4. Read src/lib/config/lesson-types.ts — canonical type list
5. Read scripts/ingest-forgotten-ways-course.ts for insert patterns

Course Structure (8 Weeks)

Every course follows this exact structure. 8 weeks total, numbered 1–8. No Week 0.

Week 1 — Introduction & Orientation

Weeks 2–7 — Core Transformation Modules (The Loop)

Each week follows this order — do not deviate:

Week 8 — Synthesis & Sending

Process

Step 1: Create the ingestion script

Create scripts/scaffold-course-[slug].ts that:

1. Connects to the database using the project's postgres/Drizzle setup
2. Creates the courses row with:
   • title, slug, description (placeholder), status: "draft"
   • duration_weeks: 8
   • course_type: "formation"
   • portal_themes: ["<portal>"] if portal provided
   • organization_id from env TENANT_ORG_ID
3. Creates 8 courseWeeks rows (week_number 1–8) with:
   • Week 1: "Introduction & Orientation"
   • Weeks 2–7: "Week N — [TBD]" (theme to be authored)
   • Week 8: "Week 8 — Synthesis & Sending"
   • order_index matching week_number
4. Creates courseLessons rows for each week following the canonical section order above
   • Each lesson: title (descriptive placeholder), slug (auto-generated from title + week), section_type, section_order (global counter), week_id, course_id, status: "draft", content: "" (empty — to be authored via /course-author)
   • Use the sidebar labels from the tables above where they exist; null otherwise

Step 2: Optionally scaffold markdown files

Ask the user if they also want a markdown content directory. If yes, create:

content-library/courses/[slug]/
  course-manifest.json
  week-01-introduction.md
  week-02-[theme].md
  ...
  week-08-synthesis.md

Each markdown file should have section headers matching the transformation loop:

## Week 2 — Opening Video
[Content TBD — ~700 words, ~5 min]

## Week 2 — Dissonance
[Content TBD — 200-350 words]

## Week 2 — Main Teaching
[Content TBD — 2,000-3,500 words]

## Week 2 — Case Study
[Content TBD — 300-600 words]

## Week 2 — Action Step
[Content TBD — 150-250 words]

## Week 2 — Reflection
[Content TBD — 150-250 words]

## Week 2 — Cohort Meeting
[Content TBD — 200-400 words]

## Week 2 — Exit Ticket
[Content TBD — 150-250 words]

The manifest should list all lessons with ids, types, and week assignments.

Step 3: Report

Output a summary:

• Course created: title (slug)
• Weeks: 8
• Total sections: N
• Sections per week breakdown
• Next steps: "Use /course-author to generate content for each section"

Rules

• 8 weeks exactly. Week 1 = introduction, Week 8 = synthesis and sending. No Week 0.
• Transformation loop order is fixed for Weeks 2–7: video → chat_dissonance → reading → case_study → chat_action → chat_reflection → discussion → reflection
• Use env TENANT_ORG_ID for organization_id scoping
• Set all content to draft status
• Follow the project's postgres insert patterns from scripts/ingest-forgotten-ways-course.ts
• Never hardcode UUIDs — let the database generate them
• Validate the slug doesn't already exist before inserting
• Reference _docs/COURSE_STRATEGY.md for any structure questions — it is the authoritative source