plan-module

Plan Module

Plan a complete Canvas module: the Module Outcomes page, the lessons inside it, the summative assessment at the end, and the Canvas Module container that holds them all. All drafts. Teacher publishes manually.

This skill never publishes anything. Every page lands in Canvas as a draft. The Canvas Module itself is created in Canvas's default unpublished state. The teacher reviews everything in Canvas and clicks Publish themselves when ready.

When to use

A teacher describes a multi-lesson stretch of curriculum they want to scaffold in Canvas. Common phrasings:

• "Plan a module on vibe coding — Weeks 24–36, course DSGN 9"

• "Design Module 4 for FSV 117 — pitch development, 4 weeks"

• "Draft a watershed unit, 6 lessons + a test"

• "I need to set up the next module — AI tools for designers, 8 weeks"

When NOT to use

• Single lesson — that's plan-lesson (UbD planning) or post-lesson-page (just posting an already-planned lesson).

• Single assessment — that's plan-assessment.

• Adding to an existing module — call list_modules, then add_module_item directly (or use plan-lesson → post-lesson-page / plan-assessment and then add the resulting page).

Prerequisites

• canvas-mcp v0.3.16 or later (needs create_module from v0.3.12 + title_format on list_page_templates from v0.3.16).

• A school config with lesson, assessment, and module_outcomes page templates (Franklin: bundled by default).

Workflow

1. Capture the module metadata

These pieces are required to build the module. Get them from the teacher's initial request; ask only for what's missing:

• Canvas course (code or numeric id — confirm via list_courses if there's any ambiguity)

• Module number (integer; e.g., 4)

• Module short title (the marketing name; e.g., "Vibe Coding")

• Module subtitle (the elaboration; e.g., "Transforming Text into Functional Software with AI")

• Week range (start–end integers, e.g., 24–36)