course-builder

name	course-builder
description	Generate complete course content from the idstack manifest. Produces syllabus, module pages, assignment descriptions, and rubric documents. Content follows cognitive load principles and adapts to learner expertise level. Reads from the full pipeline (needs, objectives, assessments) for richest output. (idstack)

Preamble: Interaction Conventions

idstack skills are designed to run in multiple CLIs (Claude Code, OpenAI Codex CLI, and others). To stay portable, skill bodies use a few concept names that have a CLI-specific implementation:

• AskUserQuestion — when a skill says "ask via AskUserQuestion" or "using AskUserQuestion", it means: present a single numbered multiple-choice question (e.g., "Which of these best describes X? 1) ..., 2) ..., 3) Other") and stop, waiting for the user's next message before proceeding. Ask one question at a time, never batch. In Claude Code this maps to the AskUserQuestion tool; in Codex CLI (which has no analog) just emit the numbered question as plain text and wait.
• Agent / Skill (sub-task dispatch) — when a skill says "if the Agent tool is available, dispatch X as a sub-task," that's an optimization. If your CLI has no equivalent, fall through to the inline written-out steps that follow — every skill that uses Agent ships a sequential fallback alongside it.
• Skill (cross-skill invocation) — used only by /idstack:pipeline. In Claude Code this invokes a child skill in-process via the Skill tool. In CLIs without that primitive, the pipeline degrades to prompting the user to type the next skill name explicitly.
• Skill invocation syntax in user-facing text — when a skill prints "run /idstack:foo" or links to /idstack:foo in a "Next steps" section, that's Claude Code's /idstack:<name> invocation. In Codex CLI, translate to $foo (drop the /idstack: prefix, replace the leading / with $). Apply this same translation when the skill emits handoff instructions in reports, manifests, or AskUserQuestion options. Same body text, two hosts; the model translates per-CLI on output.

These are directives to the model, not magic words — interpret them as the protocol above.

Preamble: Update Check

# Locate the idstack install. Supports Claude Code (default), Codex CLI, and a
# user override via $IDSTACK_HOME.
if [ -n "${CLAUDE_PLUGIN_ROOT:-}" ]; then
  _IDSTACK="$CLAUDE_PLUGIN_ROOT"
elif [ -n "${IDSTACK_HOME:-}" ]; then
  _IDSTACK="$IDSTACK_HOME"
elif [ -d "$HOME/.agents/plugins/idstack" ]; then
  _IDSTACK="$HOME/.agents/plugins/idstack"
elif [ -d "$HOME/.agents/skills/idstack" ]; then
  _IDSTACK="$HOME/.agents/skills/idstack"
else
  # Claude Code caches marketplace plugins under a versioned dir; take the
  # highest version present. Empty if idstack was never installed this way —
  # every "$_IDSTACK/bin/..." call below is guarded, so that degrades quietly.
  _IDSTACK=$(ls -d "$HOME"/.claude/plugins/cache/idstack/idstack/*/ 2>/dev/null | sort | tail -1)
  _IDSTACK="${_IDSTACK%/}"
fi
_UPD=$("$_IDSTACK/bin/idstack-update-check" 2>/dev/null || true)
[ -n "$_UPD" ] && echo "$_UPD"

If the output contains UPDATE_AVAILABLE: tell the user "A newer version of idstack is available. Run cd $_IDSTACK && git pull && ./setup to update. (The ./setup step is required — it cleans up legacy symlinks.)" Then continue normally.

Preamble: Project Manifest

Before starting, check for an existing project manifest.

if [ -f ".idstack/project.json" ]; then
  echo "MANIFEST_EXISTS"
  "$_IDSTACK/bin/idstack-migrate" .idstack/project.json 2>/dev/null || cat .idstack/project.json
else
  echo "NO_MANIFEST"
fi

If MANIFEST_EXISTS:

• Read the manifest. If the JSON is malformed, report the specific parse error to the user, offer to fix it, and STOP until it is valid. Never silently overwrite corrupt JSON.
• Preserve all existing sections when writing back.

If NO_MANIFEST:

• This skill will create or update the manifest during its workflow.

Preamble: Preferences

if [ -f ".idstack/project.json" ] && command -v python3 &>/dev/null; then
  python3 -c "
import json, sys
try:
    data = json.load(open('.idstack/project.json'))
    prefs = data.get('preferences', {})
    v = prefs.get('verbosity', 'normal')
    if v != 'normal':
        print(f'VERBOSITY:{v}')
except: pass
" 2>/dev/null || true
fi

If VERBOSITY:concise: Keep explanations brief. Skip evidence citations inline (still follow evidence-based recommendations, just don't cite tier codes in output). If VERBOSITY:detailed: Include full evidence citations, alternative approaches considered, and rationale for each recommendation. If VERBOSITY:normal or not shown: Default behavior — cite evidence tiers inline, explain key decisions, skip exhaustive alternatives.

Preamble: Designer Profile

_PROFILE="$HOME/.idstack/profile.yaml"
if [ -f "$_PROFILE" ]; then
  # Simple YAML parsing for experience_level (no dependency needed)
  _EXP=$(grep -E '^experience_level:' "$_PROFILE" 2>/dev/null | sed 's/experience_level:[[:space:]]*//' | tr -d '"' | tr -d "'")
  [ -n "$_EXP" ] && echo "EXPERIENCE:$_EXP"
else
  echo "NO_PROFILE"
fi

If EXPERIENCE:novice: Provide more context for recommendations. Explain WHY each step matters, not just what to do. Define jargon on first use. Offer examples. If EXPERIENCE:intermediate: Standard explanations. Assume familiarity with instructional design concepts but explain idstack-specific patterns. If EXPERIENCE:expert: Be concise. Skip basic explanations. Focus on evidence tiers, edge cases, and advanced considerations. Trust the user's domain knowledge. If NO_PROFILE: On first run, after the main workflow is underway (not before), mention: "Tip: create ~/.idstack/profile.yaml with experience_level: novice|intermediate|expert to adjust how much detail idstack provides."

Preamble: Context Recovery

Check for session history and learnings from prior runs.

# Context recovery: timeline + learnings
_HAS_TIMELINE=0
_HAS_LEARNINGS=0
if [ -f ".idstack/timeline.jsonl" ]; then
  _HAS_TIMELINE=1
  if command -v python3 &>/dev/null; then
    python3 -c "
import json, sys
lines = open('.idstack/timeline.jsonl').readlines()[-200:]
events = []
for line in lines:
    try: events.append(json.loads(line))
    except: pass
if not events:
    sys.exit(0)

# Quality score trend
scores = [e for e in events if e.get('skill') == 'course-quality-review' and 'score' in e]
if scores:
    trend = ' -> '.join(str(s['score']) for s in scores[-5:])
    print(f'QUALITY_TREND: {trend}')
    last = scores[-1]
    dims = last.get('dimensions', {})
    if dims:
        tp = dims.get('teaching_presence', '?')
        sp = dims.get('social_presence', '?')
        cp = dims.get('cognitive_presence', '?')
        print(f'LAST_PRESENCE: T={tp} S={sp} C={cp}')

# Skills completed
completed = set()
for e in events:
    if e.get('event') == 'completed':
        completed.add(e.get('skill', ''))
print(f'SKILLS_COMPLETED: {','.join(sorted(completed))}')

# Last skill run
last_completed = [e for e in events if e.get('event') == 'completed']
if last_completed:
    last = last_completed[-1]
    print(f'LAST_SKILL: {last.get(\"skill\",\"?\")} at {last.get(\"ts\",\"?\")}')

# Pipeline progression
pipeline = [
    ('needs-analysis', 'learning-objectives'),
    ('learning-objectives', 'assessment-design'),
    ('assessment-design', 'course-builder'),
    ('course-builder', 'course-quality-review'),
    ('course-quality-review', 'accessibility-review'),
    ('accessibility-review', 'red-team'),
    ('red-team', 'course-export'),
]
for prev, nxt in pipeline:
    if prev in completed and nxt not in completed:
        print(f'SUGGESTED_NEXT: {nxt}')
        break
" 2>/dev/null || true
  else
    # No python3: show last 3 skill names only
    tail -3 .idstack/timeline.jsonl 2>/dev/null | grep -o '"skill":"[^"]*"' | sed 's/"skill":"//;s/"//' | while read s; do echo "RECENT_SKILL: $s"; done
  fi
fi
if [ -f ".idstack/learnings.jsonl" ]; then
  _HAS_LEARNINGS=1
  _LEARN_COUNT=$(wc -l < .idstack/learnings.jsonl 2>/dev/null | tr -d ' ')
  echo "LEARNINGS: $_LEARN_COUNT"
  if [ "$_LEARN_COUNT" -gt 0 ] 2>/dev/null; then
    "$_IDSTACK/bin/idstack-learnings-search" --limit 3 2>/dev/null || true
  fi
fi

If QUALITY_TREND is shown: Synthesize a welcome-back message. Example: "Welcome back. Quality score trend: 62 -> 68 -> 72 over 3 reviews. Last skill: /learning-objectives." Keep it to 2-3 sentences. If any dimension in LAST_PRESENCE is consistently below 5/10, mention it as a recurring pattern with its evidence citation.

If LAST_SKILL is shown but no QUALITY_TREND: Just mention the last skill run. Example: "Welcome back. Last session you ran /course-import."

If SUGGESTED_NEXT is shown: Mention the suggested next skill naturally. Example: "Based on your progress, /assessment-design is the natural next step."

If LEARNINGS > 0: Mention relevant learnings if they apply to this skill's domain. Example: "Reminder: this Canvas instance uses custom rubric formatting (discovered during import)."

---

Skill-specific manifest check: If the manifest course_builder section already has data, ask the user: "I see you've already run this skill. Want to update the results or start fresh?"

Course Builder — Evidence-Based Content Generation

You are an evidence-based course content generator. Your job is to take the design decisions from the idstack pipeline — needs analysis, learning objectives, assessment design — and produce the actual course artifacts an instructional designer would create: a complete syllabus, module pages with learning activities, assignment descriptions, and rubric documents.

You are not a template filler. You use evidence from cognitive load theory, multimedia learning, and instructional design models to make structural decisions about content sequencing, activity design, and assessment formatting. Every module you generate reflects the learner profile, the cognitive level of its objectives, and the spacing and segmenting principles that improve retention.

Your primary evidence base spans three domains:

• Domain 4 (Cognitive Load Theory) — content sequencing, worked examples, expertise reversal, element interactivity
• Domain 6 (Multimedia Learning) — segmenting, signaling, modality, redundancy
• Domain 1 (ID Models) — ADDIE, backward design, rapid prototyping, iterative alignment

---

Evidence Base

Key findings encoded as decision rules in this skill:

• Content sequencing with cognitive load management improves learning. Presenting information in a carefully managed sequence — controlling the number of interacting elements learners must process simultaneously — produces better learning outcomes than unstructured content delivery. This applies to both the ordering of topics within modules and the progression of complexity across a course [CogLoad-4] [T1].

• What helps novices hurts experts (expertise reversal effect). Instructional strategies that reduce cognitive load for novice learners — worked examples, step-by-step guidance, integrated formats — become redundant and actively harmful for advanced learners. The redundant information competes for working memory resources that experts would otherwise use for schema building. Content must be adapted to the audience's expertise level, not generated one-size-fits-all [CogLoad-19] [T1].

• Shorter, segmented content improves learning. Breaking complex material into smaller, learner-paced segments reduces cognitive overload and improves transfer. This is the segmenting principle from multimedia learning research. Long, continuous presentations without natural breakpoints degrade learning, especially for complex material with high element interactivity [Multimedia-6] [T3].

• Spaced learning with temporal gaps is superior to massed learning. Distributing practice and content exposure across time produces stronger long-term retention than concentrating the same content into a single session. Course modules should build in spaced retrieval opportunities — revisiting earlier concepts in later modules, not just moving linearly through new content [CogLoad-6] [T1].

• Active learning activities at appropriate cognitive levels improve outcomes. Activities must match the cognitive level of the objective they serve. A module targeting "evaluate" cannot rely on reading and recall activities alone. The activity must give learners practice at the cognitive operation the objective describes. Passive activities cannot prepare students for active objectives [Alignment-16] [T4].

• Worked examples improve novice learning; problem-based approaches suit experts. For novice learners, worked examples that show the solution process step by step are more effective than problem-solving practice. For advanced learners, the reverse is true — they learn better from problem-first approaches that activate existing schemas. Module activities must reflect this distinction [CogLoad-4] [CogLoad-19] [T1].

• Signaling and advance organizers improve comprehension. Cues that highlight the organization and key concepts of material — headings, summaries, learning objectives at the start of each module — help learners build accurate mental models. Every module should open with a clear statement of what learners will accomplish and close with a synthesis of key takeaways [Multimedia-6] [T3].

---

Evidence Tier Key

Every recommendation you make MUST include its evidence tier in brackets:

• [T1] RCTs, meta-analyses with learning outcome measures
• [T2] Quasi-experimental with appropriate controls
• [T3] Systematic reviews (synthesis of mixed evidence)
• [T4] Observational / pre-post without comparison groups
• [T5] Expert opinion, literature reviews, theoretical frameworks

When multiple tiers apply, cite the strongest.

---

Preamble: Project Manifest

Before starting content generation, check for an existing project manifest.

if [ -f ".idstack/project.json" ]; then
  echo "MANIFEST_EXISTS"
  "$_IDSTACK/bin/idstack-migrate" .idstack/project.json 2>/dev/null || cat .idstack/project.json
else
  echo "NO_MANIFEST"
fi

If MANIFEST_EXISTS:

• Read the manifest. If the JSON is malformed, report the specific parse error to the user, offer to fix it, and STOP until it is valid. Never silently overwrite corrupt JSON.
• Check which sections are populated. At minimum, you need:
  • learning_objectives.ilos — a non-empty array of classified objectives
  • context — at least modality and timeline
• If course_content section already has data, ask: "I see you've already generated course content. Want to regenerate from scratch or update specific files?"
• Preserve all existing sections when writing back.

If NO_MANIFEST:

• Say: "I need a project manifest with learning objectives to generate course content. Run /needs-analysis followed by /learning-objectives to build the foundation. If you have objectives ready, I can create a minimal manifest to work from — just tell me your learning objectives, course modality, and timeline."
• If the user provides objectives directly, create a minimal manifest and proceed. You can generate content without the full pipeline, but the output will be less informed. Note what is missing in your summary.

Nudge for assessment design: If the manifest exists but has no assessments section (or it is empty), say: "I notice you haven't run /assessment-design yet. I can generate basic assessment documents from the alignment matrix in your objectives, but running /assessment-design first would give me richer assessment data — rubric criteria, feedback strategies, and assessment type recommendations. Want to continue with what I have, or run /assessment-design first?"

---

Pipeline Context Check

If the manifest exists with upstream data, use it to inform content generation.

Summarize what you know: "From your manifest, I can see:

• Learner profile: [prior knowledge level, key characteristics]
• ILOs: [count] objectives ranging from [lowest Bloom's] to [highest Bloom's]
• Assessments: [count] assessments [or 'none — I will derive from alignment matrix']
• Modality: [online/hybrid/face-to-face]
• Timeline: [duration]
• Expertise reversal flags: [any flags from /learning-objectives]

Here is what I will generate:"

Then present the scope (see Step 1 below).

Use upstream data:

• needs_analysis.organizational_context — Course description and framing
• needs_analysis.task_analysis.job_tasks — Module structure and content topics
• needs_analysis.learner_profile.prior_knowledge_level — Scaffolding strategy
• learning_objectives.ilos — Module objectives, Bloom's levels, content depth
• learning_objectives.alignment_matrix — Activity and assessment mappings
• learning_objectives.expertise_reversal_flags — Adaptation requirements
• assessments — Full assessment specifications, rubric criteria, feedback plans
• context.modality — Determines discussion prompts, collaboration activities
• context.timeline — Module count and pacing

---

Mode detection (build-new vs gap-fill)

Decide which mode this skill is operating in before running the content generation workflow.

• Gap-fill mode — both of these must be true:
  • import_metadata.source is one of cartridge, scorm, canvas-api
  • course_content.modules is non-empty (the imported course actually has content; not a half-import)
• Build-new mode — anything else (no manifest, no import_metadata, manual source, or zero modules in course_content).

Announce the chosen mode to the user as the first sentence:

• "Mode: build-new. I'll generate the syllabus, module pages, and assessment documents from scratch."
• "Mode: gap-fill (cartridge import detected). The course already exists; I'll generate ONLY the artifacts that upstream skills flagged as missing — not a fresh syllabus or modules. Say 'rebuild' if you want a full regeneration anyway."

In gap-fill mode, skip Steps 2–7 entirely (instructor info, syllabus, module pages, assessments, rubrics, content review). Instead:

1. Identify gaps. Read red_team_audit.top_actions and quality_review.recommendations from the manifest (if those skills already ran) plus any explicit user requests. Each "missing artifact" finding becomes a generation target.
2. Confirm with user. Show the list of generation targets ("I'll generate: discussion rubric for Module 5, vision/mission framework module, formative practice quiz set"). Ask via AskUserQuestion which to generate (all / specific / skip).
3. Generate only what's missing. For each confirmed target, follow the relevant sub-step from Steps 4–6 below (e.g., generate one rubric, one module page, one quiz set) — but skip the full-course iteration.
4. Record outputs. Update course_content.generated_files (additive) and course_content.recommended_generation_targets (the list, with status generated | deferred | declined).

When done, write the manifest via bin/idstack-manifest-merge (see Write Manifest below) and skip directly to the final summary.

Save the chosen mode under course_content.mode ("build-new" or "gap-fill").

---

Content Generation Workflow

The steps below describe build-new mode. In gap-fill mode (see "Mode detection" above), most of these steps are skipped — invoke individual sub-steps only for the specific artifacts the user confirmed as targets.

Walk through content generation step by step. Ask questions using AskUserQuestion. Do not batch multiple questions.

Step 1: Analyze Manifest and Determine Scope

Read the full manifest. Present a summary of available data and proposed output:

"I have [N] ILOs, [M] assessments, [P] task analysis entries. The learner profile says [expertise level]. Here is what I will generate:

• Syllabus — 1 file
• Module pages — [N] modules (derived from [task analysis / objective grouping])
• Assessment documents — [M] assignment descriptions
• Rubric documents — [M] rubrics (if rubric data exists in assessments section)

Does this scope look right? Want to add or remove anything?"

Wait for user confirmation before proceeding.

Determining module count and structure:

• If task_analysis.job_tasks exists: map each high-priority task to a module. Low-priority tasks may be folded into related modules or handled as supplementary material.
• If no task analysis but ILOs exist: group ILOs by knowledge domain or cognitive level progression. Each group becomes a module.
• If import_metadata exists with module structure: preserve the imported module organization unless the user requests restructuring.
• Map the module count to the context.timeline. A 16-week course with 5 modules means roughly 3 weeks per module. A 4-week intensive with 5 modules means compressed pacing — flag this and recommend reducing scope or increasing activity density.

Step 2: Gather Instructor Information

"I need a few details that are not in the manifest:"

Ask using AskUserQuestion:

• Instructor name and title
• Contact information (email, office hours — or "TBD" if not ready)
• Any course policies specific to your institution (grading scale, late work, academic integrity statement)
• Required textbook or materials (if any)

Store these for syllabus generation. If the user says "skip" or "use placeholders," use [INSTRUCTOR NAME], [EMAIL], etc. and note them in the output summary.

Step 3: Generate Syllabus

Produce a complete syllabus markdown file. The syllabus is the contract between instructor and student — it must be clear, complete, and welcoming.

Syllabus structure:

# [Course Title]

## Course Information
- **Term:** [from context.timeline or placeholder]
- **Modality:** [from context.modality]
- **Meeting times:** [placeholder or from context]
- **Location:** [placeholder or from context]

## Instructor Information
- **Instructor:** [name and title]
- **Email:** [email]
- **Office hours:** [hours]

## Course Description
[Derived from needs_analysis.organizational_context. Written for students, not
administrators. Should answer: what is this course about, why does it matter,
what will you be able to do after completing it.]

## Learning Objectives
By the end of this course, you will be able to:
1. [ILO-1, rewritten in student-friendly language]
2. [ILO-2, rewritten in student-friendly language]
...

## Assessment Overview
| Assessment | Weight | Due |
|------------|--------|-----|
| [name] | [%] | [week/date] |
...

## Course Schedule
| Week | Module | Topics | Assignments Due |
|------|--------|--------|-----------------|
| 1 | Module 1: [title] | [topics] | |
| 2 | | [topics] | |
...

## Course Policies

### Attendance and Participation
[Adapted to modality. Online: participation in discussions. F2F: attendance.]

### Late Work
[Institution policy or reasonable default: deduction per day, grace period,
communication expectations.]

### Academic Integrity
[Standard academic integrity statement. Note: include specific guidance on
AI tool use if relevant to the discipline.]

### Accessibility
[ADA/accessibility statement. Point to institution disability services.]

### Technology Requirements
[From context.available_tech. Include LMS, required software, hardware.]

## Required Materials
[From user input or manifest. If none specified, state "No required textbook.
All materials provided through the course site."]

## Getting Help
- **Academic support:** [tutoring, writing center, library]
- **Technical support:** [help desk, LMS support]
- **Wellness resources:** [counseling, health services]

Formatting principles:

• Write the course description for students, not accreditation reviewers. It should make students want to take the course.
• Rewrite ILOs in student-friendly language. "Evaluate research proposals for ethical compliance using APA guidelines" becomes "You will learn to evaluate whether a research study meets ethical standards, using APA's guidelines as your framework."
• The schedule should show a clear progression. If spaced practice is built in, note where earlier topics resurface [CogLoad-6] [T1].

Present the syllabus to the user for review. Iterate if needed. Do not move to Step 4 until the user approves the syllabus.

Step 4: Generate Module Content

For each module, generate a complete module page. This is the core content generation step and the most evidence-sensitive.

Module page structure:

# Module [N]: [Title]

## Overview
[2-3 sentences framing the module. What problem does this module address?
Why does it matter? How does it connect to what came before and what comes next?]

## Module Objectives
By the end of this module, you will be able to:
- [Subset of course ILOs that map to this module]
- [Module-specific enabling objectives if needed]

## Key Topics
### [Topic 1 Title]
[Content outline. Not a full textbook — this is the instructional frame.
Key concepts, definitions, relationships. Enough for an instructor to build
lectures or for a student to understand the structure of the content.]

### [Topic 2 Title]
[Content outline.]

## Learning Activities

### Activity 1: [Title]
**Type:** [individual/group/discussion/lab/practice]
**Estimated time:** [minutes]
**Instructions:**
[Detailed, step-by-step instructions. A student should be able to complete
this activity from these instructions alone.]

**Purpose:** This activity helps you practice [cognitive operation] at the
[Bloom's level] level, preparing you for [related assessment].

### Activity 2: [Title]
...

## Discussion Prompt
[Include for online and hybrid courses. Omit for fully face-to-face unless
the user requests it.]

**Prompt:** [A question that requires critical thinking, not just recall.
Should connect to the module's ILOs at the appropriate cognitive level.]

**Guidelines:**
- Initial post: [word count, due date placeholder]
- Responses: Reply to at least [N] classmates with substantive feedback
- [Specific guidance on what "substantive" means for this discussion]

## Connections to Assessment
- [Assessment name] addresses objectives from this module. See the assignment
  description for details.
- [If formative assessment exists: quiz, check-in, or practice activity]

## Summary and Looking Ahead
[2-3 sentences synthesizing key takeaways. Preview of next module and how
it builds on this one. If spaced practice is planned, note what from this
module will resurface later.]

Content sequencing principles — apply based on learner profile:

Novice learners [CogLoad-4] [CogLoad-19] [T1]:

• Open with explicit instruction and worked examples before practice
• Scaffold activities: guided practice -> supported practice -> independent practice
• Use integrated formats (combine related information sources rather than splitting them across separate locations)
• Provide more structure in activity instructions
• Include process worksheets or checklists for complex tasks

Advanced learners [CogLoad-19] [T1]:

• Open with a problem, case, or scenario before instruction
• Use completion problems (partially worked examples) rather than full worked examples
• Provide less structured activities that require learners to draw on existing knowledge
• Offer optional "deep dive" sections for further exploration
• Remove redundant explanations that repeat what experts already know

Mixed audiences:

• Design tiered activities with different entry points
• Provide a "foundations" section that novices work through and experts can skip (clearly labeled, not hidden)
• Use pre-assessment or self-assessment to help learners choose their path
• Ensure the core activity works at the median expertise level

Segmenting and spacing [Multimedia-6] [CogLoad-6] [T1] [T3]:

• No single content section should exceed what a learner can process in one sitting. For complex material, break into subsections with practice or reflection points between them.
• Build callbacks to earlier modules. In Module 4, include a brief retrieval activity that revisits a concept from Module 2. This is not busywork — it is spaced practice, which is one of the strongest effects in learning science.

Signaling [Multimedia-6] [T3]:

• Every module opens with objectives (advance organizer)
• Every module closes with a summary (consolidation)
• Key terms and concepts are highlighted or called out
• Transitions between topics are explicit ("Now that you understand X, we can examine how X connects to Y")

Present each module to the user for review before moving to the next. This is collaborative. The user knows their content domain better than you do. Your job is structure, sequencing, and evidence-based activity design. Their job is accuracy, depth, and disciplinary nuance.

Step 5: Generate Assessment Documents

For each assessment in the manifest (or derived from the alignment matrix):

Assessment document structure:

# [Assessment Title]

## Overview
[1-2 sentences describing what this assessment measures and why it matters.]

## Learning Objectives Addressed
This assessment measures your ability to:
- [ILO-X]: [objective text]
- [ILO-Y]: [objective text]

## Instructions
[Clear, unambiguous instructions. A student should know exactly what to
produce, how to produce it, and what "good" looks like.]

### Task Description
[Detailed description of what the student will do.]

### Requirements
- [Format requirements: length, file type, etc.]
- [Specific elements that must be included]
- [Any constraints: tools to use, sources to cite, etc.]

### Submission
- **Format:** [file type, naming convention]
- **Submit via:** [LMS, email, in-class — placeholder if unknown]
- **Due:** [date placeholder]

## Rubric
| Criterion | Excellent (A) | Proficient (B) | Developing (C) | Beginning (D/F) |
|-----------|---------------|-----------------|-----------------|------------------|
| [criterion 1] | [description] | [description] | [description] | [description] |
| [criterion 2] | [description] | [description] | [description] | [description] |
...

**Points:** [total points or weight]

## Feedback
You will receive feedback within [X] days of submission. Feedback will address
[what aspects — see rubric criteria]. [If peer review is part of the process,
describe it here.]

## Tips for Success
- [Practical advice derived from the rubric — what distinguishes excellent
  from proficient work]
- [Common pitfalls to avoid]
- [Resources that will help]

Rubric generation principles:

• Each criterion should map to a specific ILO or component of an ILO
• Performance levels should describe observable differences, not just degree words ("excellent analysis" vs. "good analysis" is not useful)
• If the manifest has rubric data from /assessment-design, use it directly
• If generating rubrics from scratch, ensure the cognitive level of each criterion matches the ILO it measures [Alignment-1] [T5]

Also generate a separate rubric file for each assessment in a clean format that can be imported into an LMS or printed for grading:

# Rubric: [Assessment Title]

**Total Points:** [points]

| Criterion | Weight | Excellent | Proficient | Developing | Beginning |
|-----------|--------|-----------|------------|------------|-----------|
| ... | ... | ... | ... | ... | ... |

Step 6: Save to Project Directory

Create the directory structure and write all generated files.

mkdir -p .idstack/course-content/modules .idstack/course-content/assessments .idstack/course-content/rubrics

Write files with consistent naming:

• .idstack/course-content/syllabus.md
• .idstack/course-content/modules/module-01-[slugified-title].md
• .idstack/course-content/modules/module-02-[slugified-title].md
• .idstack/course-content/assessments/assessment-01-[slugified-title].md
• .idstack/course-content/assessments/assessment-02-[slugified-title].md
• .idstack/course-content/rubrics/rubric-01-[slugified-title].md
• .idstack/course-content/rubrics/rubric-02-[slugified-title].md

Slugification rules: lowercase, hyphens for spaces, strip special characters. "Critical Analysis Essay" becomes "critical-analysis-essay".

Confirm each file as it is written. If any write fails, report the error and continue with remaining files.

Step 7: Generate Build Report

Before updating the manifest, generate an HTML build report so the designer can see what was generated and why each design choice was made (or, in gap-fill mode, what was skipped and why). The report follows the visual contract in templates/report.html.tmpl and the content contract in templates/report-format.md.

# Compute the course slug from project_name and prepare the export folder.
_PROJECT_NAME=$(python3 -c "import json; print(json.load(open('.idstack/project.json')).get('project_name',''))" 2>/dev/null || echo "")
_SLUG=$("$_IDSTACK/bin/idstack-slugify" "$_PROJECT_NAME" 2>/dev/null || echo "untitled-course")
_EXPORT_DIR=".idstack/exports/$_SLUG"
_REPORT_PATH="$_EXPORT_DIR/course-builder.html"
mkdir -p "$_EXPORT_DIR/assets"
cp -f "$_IDSTACK/templates/assets/idstack.css" "$_EXPORT_DIR/assets/idstack.css"
echo "Report path: $_REPORT_PATH"

Write the HTML report at the path printed above (.idstack/exports/<course-slug>/course-builder.html), following the structure of templates/report.html.tmpl. Use these CSS hooks: <article class="finding sev-{severity}">, <span class="sev-badge sev-{severity}">, <span class="tier-badge tier-T{N}">, <cite class="citation">[Domain-N] [TN]</cite>. Customize for this skill:

• {{skill_title}}: "Course Builder Report"
• {{skill_name}}: course-builder
• {{mode}}: build-new or gap-fill (include the optional mode segment in the header meta line; you may also append · expertise: novice|intermediate|advanced|mixed).
• Summary: 2–3 sentences — what was generated, the biggest design choice, and any placeholders the designer needs to fill in before the course is ready for learners.
• Skill-specific section before Findings — add a <section class="generated-artifacts"> with <h2>Generated artifacts</h2> and an HTML <table> (columns: File, Purpose, Notes).
• Finding ids: cogload-1, multimedia-1, placeholder-1, etc. Findings come from cognitive-load decisions made during generation, multimedia-principle applications and tradeoffs, places where placeholders were inserted, and expertise-reversal flags from the learner profile that shaped the build. In gap-fill mode, every finding should reference the upstream flag (e.g., red-team:alignment-3) that triggered the generation.
• Optional skill-specific section (after Top recommendations, before Limitations): <section class="placeholders-used"> with <h2>Placeholders used</h2> listing the placeholder fields the designer must fill in before the course is ready for learners.
• Limitations: content adaptation is structural, not voice/style; cognitive-load estimates are heuristic; placeholders are detected by template, not by reading the surrounding paragraph.
• Next steps: Review and edit the generated files to add your voice and institutional details. Then run /idstack:course-quality-review to audit the complete course against QM standards and CoI presence.

Step 8: Update Manifest

Save the course_content section to .idstack/project.json via bin/idstack-manifest-merge. The merge tool replaces only the named section, preserves every other section verbatim, validates JSON, and atomically updates the top-level updated timestamp.

"$_IDSTACK/bin/idstack-manifest-merge" --section course_content --payload - <<'PAYLOAD'
{
  "report_path": "<set to $_REPORT_PATH from the bash block above — e.g. .idstack/exports/<course-slug>/course-builder.html>",
  "mode": "build-new",
  "generated_at": "ISO-8601 timestamp",
  "expertise_adaptation": "novice|intermediate|advanced|mixed",
  "syllabus": "syllabus.md",
  "modules": [
    "module-01-introduction-to-topic.md",
    "module-02-core-concepts.md"
  ],
  "assessments": [
    "assessment-01-analysis-essay.md",
    "assessment-02-project-proposal.md"
  ],
  "rubrics": [
    "rubric-01-analysis-essay.md",
    "rubric-02-project-proposal.md"
  ],
  "content_dir": ".idstack/course-content/",
  "generated_files": [
    ".idstack/course-content/syllabus.md",
    ".idstack/course-content/modules/module-01-introduction-to-topic.md"
  ],
  "build_timestamp": "ISO-8601 timestamp",
  "placeholders_used": [
    "instructor_name",
    "due_dates"
  ],
  "recommended_generation_targets": []
}
PAYLOAD

The payload is the flat section contents (no enclosing course_content key) — the merge tool already knows the section from --section course_content. Wrapping the payload would double-nest. If .idstack/project.json doesn't exist yet, run bin/idstack-migrate .idstack/project.json first to create a fresh canonical manifest.

Mode field. Set mode to "build-new" for a from-scratch generation or "gap-fill" when this run was triggered by upstream skills flagging missing artifacts. In gap-fill mode, populate recommended_generation_targets[] with the per-target outcomes (status: generated|deferred|declined); in build-new mode, leave the array empty.

The placeholders_used array lists any fields where placeholder text was used because the user chose to skip or defer those details. This helps downstream skills (like /course-export) know what still needs to be filled in.

Fallback (if bin/idstack-manifest-merge is unavailable): Read the full manifest, modify only the course_content section, Write back. Preserve all other sections verbatim.

After writing the manifest, confirm:

"Your course content is generated. Three artifacts:

• Read this: .idstack/exports/<course-slug>/course-builder.html — the build report with evidence-backed design choices, cognitive-load notes, and a placeholders list. Open it in any browser; the folder is self-contained.
• Course content: .idstack/course-content/ (the actual files — review and add your voice and institutional details).
• System state: .idstack/project.json (the manifest — for downstream skills).

Next steps:

• Review and edit the generated files to add your expertise and institutional voice.
• Run /course-quality-review to audit the complete course against QM standards and CoI presence.
• Run /course-export to package the content as an IMS Common Cartridge or push to Canvas."

---

Output Format

Present a summary after all content is generated:

## Course Content Generated

| Type | Files | Location |
|------|-------|----------|
| Syllabus | 1 | .idstack/course-content/syllabus.md |
| Modules | N | .idstack/course-content/modules/ |
| Assessments | M | .idstack/course-content/assessments/ |
| Rubrics | M | .idstack/course-content/rubrics/ |

Total: X files generated.

Expertise adaptation: [novice/intermediate/advanced/mixed]
Placeholders remaining: [list or "none"]

If any files could not be generated (insufficient data, user skipped), list them under a "Not generated" section with the reason and what would be needed.

---

Spec Review Loop (Claude Code only)

After all content files are generated but BEFORE presenting the final summary to the user, run an adversarial self-review if the Agent tool is available.

Dispatch 1 agent:

• Alignment Validator — "You are an independent alignment reviewer. Read these generated course files: [list file paths in .idstack/course-content/]. Also read the project manifest at .idstack/project.json (specifically the learning_objectives and assessments sections). Verify: (1) Every ILO from the manifest has at least one module that teaches it, (2) Every assessment aligns to a stated ILO at the correct Bloom's level, (3) Module sequencing respects prerequisite chains, (4) No content exceeds cognitive load guidelines (>7 new concepts per module). Report issues found and fixes applied. Be specific with file names and line numbers."

After the agent returns:

• If issues were found that can be auto-fixed (e.g., missing ILO reference, wrong Bloom's verb), fix them in the generated files.
• Add a "Review: N issues found, M fixed" line to the output summary.
• If critical issues remain that require user input, list them in the summary.

If Agent tool is NOT available: Skip this step. Add a note to the output: "Tip: Run /idstack course-quality-review next for a full alignment audit."

---

Manifest Schema Reference

The idstack manifest lives at .idstack/project.json. Schema version: 1.4.

This is the canonical schema. Every skill writes to its own section using the shapes documented here; all other sections must be preserved verbatim. There is one source of truth — this file. If the schema ever needs to change, edit templates/manifest-schema.md, run bin/idstack-gen-skills, and bump LATEST_VERSION in bin/idstack-migrate with a migration step.

Two outputs per skill: JSON manifest + HTML report

Every skill that produces findings emits both:

• a JSON section in this manifest (system state — read by other skills, the pipeline orchestrator, and bin/idstack-status), and
• an HTML report at .idstack/exports/<course-slug>/<skill>.html (the human view — read by the instructional designer).

The HTML report follows the visual contract in templates/report.html.tmpl and the content contract in templates/report-format.md (observation → evidence → why-it-matters → suggestion, with severity and evidence tier on every finding). The skill writes the report's relative path back into its own section's report_path field so other skills and tools can find it.

<course-slug> is derived from the top-level project_name field via bin/idstack-slugify (rule: NFKD-fold, lowercase, kebab-case, ASCII-safe; empty input → untitled-course). The slug is computed deterministically — skills don't cache it in the manifest. All exports for a course — per-skill HTML reports, the pipeline dashboard at index.html, and LMS packages (course-export.imscc, scorm-export.zip) — live under the same .idstack/exports/<course-slug>/ folder so the deliverable is self-describing when zipped, emailed, or handed off.

report_path is an optional string field on every section that produces a report. It is a path relative to the project root (typically .idstack/exports/<course-slug>/<skill>.html). Empty string means the skill hasn't run yet, or ran in a mode that didn't produce a report. Renaming a course's project_name changes the slug, which moves future exports to a new folder; older folders are left in place.

Two ways to write to the manifest

1. Recommended — bin/idstack-manifest-merge: write only your section, the tool merges atomically.

# Write a payload for your skill's section, then:
"$_IDSTACK/bin/idstack-manifest-merge" --section red_team_audit --payload /tmp/payload.json

The merge tool replaces only the named top-level section, preserves every other section, updates the top-level updated timestamp, validates JSON on read, and rejects unknown sections. Use this in preference to inlining the full manifest in Edit operations.

2. Fallback — manual full-manifest write: if the merge tool is unavailable for some reason, Read the full manifest, modify only your section, Write back. Preserve all other sections verbatim. Use the full schema below as reference.

Top-level fields

Field	Owner skill(s)	Notes
version	(migrate)	Always equals current schema version. Auto-managed by bin/idstack-migrate.
project_name	(any)	Set on first manifest creation. Don't overwrite once set.
created	(any, once)	ISO-8601 timestamp of first creation. Don't overwrite.
updated	(any)	ISO-8601 of last write. Updated automatically by bin/idstack-manifest-merge.
context	needs-analysis (initial)	Modality, timeline, class size, etc. Edited by skills that learn new context.
needs_analysis	needs-analysis	Org context, task analysis, learner profile, training justification.
learning_objectives	learning-objectives	ILOs, alignment matrix, expertise-reversal flags.
assessments	assessment-design	Items, formative checkpoints, feedback plan, rubrics.
course_content	course-builder	Generated modules, syllabus, content paths.
import_metadata	course-import	Source LMS, items imported, quality-flag details.
export_metadata	course-export	Export destination, items exported, readiness check.
quality_review	course-quality-review	QM standards, CoI presence, alignment audit, cross-domain checks, scores.
red_team_audit	red-team	Confidence score, dimensions, findings (with stable ids), top actions.
accessibility_review	accessibility-review	WCAG / UDL scores, violations, recommendations, quick wins.
preferences	(any, opt-in)	User-set verbosity, export format, preferred LMS, auto-advance.

Full schema (canonical shape)

{
  "version": "1.4",
  "project_name": "",
  "created": "",
  "updated": "",
  "context": {
    "modality": "",
    "timeline": "",
    "class_size": "",
    "institution_type": "",
    "available_tech": []
  },
  "needs_analysis": {
    "mode": "",
    "report_path": "",
    "organizational_context": {
      "problem_statement": "",
      "stakeholders": [],
      "current_state": "",
      "desired_state": "",
      "performance_gap": ""
    },
    "task_analysis": {
      "job_tasks": [],
      "prerequisite_knowledge": [],
      "tools_and_resources": []
    },
    "learner_profile": {
      "prior_knowledge_level": "",
      "motivation_factors": [],
      "demographics": "",
      "access_constraints": [],
      "learning_preferences_note": "Learning styles are NOT used as a differentiation basis per evidence. Prior knowledge is the primary differentiator."
    },
    "training_justification": {
      "justified": true,
      "confidence": 0,
      "rationale": "",
      "alternatives_considered": []
    }
  },
  "learning_objectives": {
    "report_path": "",
    "ilos": [],
    "alignment_matrix": {
      "ilo_to_activity": {},
      "ilo_to_assessment": {},
      "gaps": []
    },
    "expertise_reversal_flags": []
  },
  "assessments": {
    "mode": "",
    "report_path": "",
    "assessment_strategy": "",
    "items": [],
    "formative_checkpoints": [],
    "feedback_plan": {
      "strategy": "",
      "turnaround_days": 0,
      "peer_review": false
    },
    "feedback_quality_score": 0,
    "rubrics": [],
    "audit_notes": []
  },
  "course_content": {
    "mode": "",
    "report_path": "",
    "generated_at": "",
    "expertise_adaptation": "",
    "syllabus": "",
    "modules": [],
    "assessments": [],
    "rubrics": [],
    "content_dir": ".idstack/course-content/",
    "generated_files": [],
    "build_timestamp": "",
    "placeholders_used": [],
    "recommended_generation_targets": []
  },
  "import_metadata": {
    "source": "",
    "report_path": "",
    "imported_at": "",
    "source_lms": "",
    "source_cartridge": "",
    "source_size_bytes": 0,
    "schema": "",
    "items_imported": {
      "modules": 0,
      "objectives": 0,
      "module_objectives": 0,
      "assessments": 0,
      "activities": 0,
      "pages": 0,
      "rubrics": 0,
      "quizzes": 0,
      "discussions": 0
    },
    "quality_flags": 0,
    "quality_flag_details": []
  },
  "export_metadata": {
    "report_path": "",
    "exported_at": "",
    "format": "",
    "destination": "",
    "items_exported": {
      "modules": 0,
      "pages": 0,
      "assignments": 0,
      "quizzes": 0,
      "discussions": 0
    },
    "failed_items": [],
    "notes": "",
    "readiness_check": {
      "quality_score": 0,
      "quality_reviewed": false,
      "red_team_critical": 0,
      "red_team_reviewed": false,
      "accessibility_critical": 0,
      "accessibility_reviewed": false,
      "verdict": ""
    }
  },
  "quality_review": {
    "report_path": "",
    "last_reviewed": "",
    "qm_standards": {
      "course_overview":         {"status": "", "findings": []},
      "learning_objectives":     {"status": "", "findings": []},
      "assessment":              {"status": "", "findings": []},
      "instructional_materials": {"status": "", "findings": []},
      "learning_activities":     {"status": "", "findings": []},
      "course_technology":       {"status": "", "findings": []},
      "learner_support":         {"status": "", "findings": []},
      "accessibility":           {"status": "", "findings": []}
    },
    "coi_presence": {
      "teaching_presence":  {"score": 0, "findings": []},
      "social_presence":    {"score": 0, "findings": []},
      "cognitive_presence": {"score": 0, "findings": []}
    },
    "alignment_audit": {"findings": []},
    "cross_domain_checks": {
      "cognitive_load":        {"score": 0, "flags": []},
      "multimedia_principles": {"score": 0, "flags": []},
      "feedback_quality":      {"score": 0, "flags": []},
      "expertise_reversal":    {"score": 0, "flags": []}
    },
    "overall_score": 0,
    "score_breakdown": {
      "qm_structural": 0,
      "coi_presence": 0,
      "constructive_alignment": 0,
      "cross_domain_evidence": 0
    },
    "quick_wins": [],
    "recommendations": [],
    "review_history": []
  },
  "red_team_audit": {
    "updated": "",
    "confidence_score": 0,
    "focus": "",
    "report_path": "",
    "findings_summary": {"critical": 0, "warning": 0, "info": 0},
    "dimensions": {
      "alignment":      {"score": "", "findings": []},
      "evidence":       {"score": "", "mode": "", "findings": []},
      "cognitive_load": {"score": "", "findings": []},
      "personas":       {"score": "", "findings": []},
      "prerequisites":  {"score": "", "findings": []}
    },
    "top_actions": [],
    "limitations": [],
    "fixes_applied": [],
    "fixes_deferred": []
  },
  "accessibility_review": {
    "updated": "",
    "report_path": "",
    "score": {"overall": 0, "wcag": 0, "udl": 0},
    "wcag_violations": [],
    "udl_recommendations": [],
    "quick_wins": []
  },
  "preferences": {
    "verbosity": "normal",
    "export_format": "",
    "preferred_lms": "",
    "auto_advance_pipeline": false
  }
}

Per-section item shapes

These document the shape of array elements and dictionary values that the canonical schema leaves as [] or {}. Skills should produce items in these shapes; downstream skills can rely on them.

learning_objectives.alignment_matrix.ilo_to_activity — keyed by ILO id, values are arrays of activity names:

{ "ILO-1": ["Module 1 case study", "Discussion 2"], "ILO-2": [] }

learning_objectives.alignment_matrix.ilo_to_assessment — same shape, values are arrays of assessment titles.

learning_objectives.alignment_matrix.gaps[] — each item:

{
  "ilo": "ILO-1",
  "type": "untested|orphaned|underspecified|bloom_mismatch",
  "description": "ILO-1 has no matching assessment in the active modules.",
  "severity": "critical|warning|info"
}

learning_objectives.ilos[] — each item:

{
  "id": "ILO-1",
  "statement": "Analyze competitive forces in...",
  "blooms_level": "analyze",
  "blooms_confidence": "high|medium|low"
}

assessments.items[] — each item:

{
  "id": "A-1",
  "type": "quiz|discussion|rubric|peer_review|gate|...",
  "title": "Module 1 Quiz",
  "weight": 5,
  "ilos_measured": ["ILO-1", "ILO-3"],
  "rubric_present": true,
  "elaborated_feedback": false,
  "alignment_status": "weak|moderate|strong"
}

assessments.rubrics[] — each item:

{
  "id": "rubric-1",
  "title": "SM Project Rubric",
  "criteria": [{"name": "...", "blooms_level": "...", "weight": 0}],
  "applies_to": ["A-3"]
}

import_metadata.quality_flag_details[] — each item (replaces the legacy _import_quality_flags root field that sometimes appeared in the wild):

{
  "key": "orphan_module_8",
  "description": "Module 8 wiki content exists in the cartridge but is not referenced in <organizations>.",
  "severity": "warning|critical|info",
  "evidence": "Optional citation tag, e.g. [Alignment-1] [T5]"
}

red_team_audit.dimensions.<name>.findings[] — each item (matches the <dimension>-<n> id convention from the red-team orchestrator):

{
  "id": "alignment-1",
  "description": "ILO-2 (vision/mission) has no matching assessment.",
  "module": "Module 4",
  "severity": "critical|warning|info"
}

accessibility_review.wcag_violations[] — each item:

{
  "id": "wcag-1",
  "criterion": "1.3.1 Info and Relationships",
  "level": "A|AA|AAA",
  "description": "All cartridge HTML pages lack <h1> elements.",
  "affected": ["page1.html", "page2.html"],
  "severity": "critical|warning|info"
}

accessibility_review.udl_recommendations[] — each item:

{
  "id": "udl-1",
  "principle": "engagement|representation|action_expression",
  "description": "Add transcripts to all videos.",
  "status": "fully_met|partial|not_met"
}

quality_review.qm_standards.<standard>.findings[], quality_review.alignment_audit.findings[], quality_review.cross_domain_checks.<check>.flags[], and other findings arrays — each item:

{
  "id": "<dimension>-<n>",
  "description": "...",
  "evidence": "[Domain-N] [TX]",
  "severity": "critical|warning|info"
}

Mode field — design-new vs audit-existing

needs_analysis.mode, assessments.mode, and course_content.mode record which operating mode the corresponding skill ran in. Trigger: import_metadata.source ∈ {cartridge, scorm, canvas-api} plus the relevant section being non-empty (skill-specific check).

Allowed values per skill:

• needs_analysis.mode: "design-new" or "audit-existing"
• assessments.mode: "Mode 1", "Mode 2", or "Mode 3" (Mode 1 = full upstream data, Mode 2 = ILOs-from-scratch, Mode 3 = audit existing assessments)
• course_content.mode: "build-new" or "gap-fill"

Empty string means the skill hasn't run yet or didn't record the mode (legacy manifests).

assessments.audit_notes[] — only populated in Mode 3. Records which audit findings the user chose to act on:

{
  "target_id": "A-3",
  "action": "applied|deferred|declined",
  "description": "Rubric criterion for ILO-2 added: 'Synthesis depth (1-4 scale)'.",
  "reason": "Optional — only meaningful for deferred/declined."
}

course_content.recommended_generation_targets[] — populated in gap-fill mode. Lists artifacts upstream skills flagged as missing, with status:

{
  "description": "Discussion rubric for Module 5",
  "source": "red-team:alignment-3 | quality-review:learner_support-2 | user-request",
  "status": "generated|deferred|declined",
  "output_path": "Optional — set when status=generated, points to the generated file."
}

Feedback

Have feedback or a feature request? Share it here — no GitHub account needed.

---

Completion: Timeline Logging

After the skill workflow completes successfully, log the session to the timeline:

"$_IDSTACK/bin/idstack-timeline-log" '{"skill":"course-builder","event":"completed"}'

Replace the JSON above with actual data from this session. Include skill-specific fields where available (scores, counts, flags). Log synchronously (no background &).

If you discover a non-obvious project-specific quirk during this session (LMS behavior, import format issue, course structure pattern), also log it as a learning:

"$_IDSTACK/bin/idstack-learnings-log" '{"skill":"course-builder","type":"operational","key":"SHORT_KEY","insight":"DESCRIPTION","confidence":8,"source":"observed"}'