Instructional Design Models & Frameworks
ADDIE, ARCS, ASSURE, and UDL each fit different contexts. Reviews across the literature find no universal best; using two or three frameworks together tends to outperform strict adherence to one.
108 peer-reviewed studies across 11 research domains. Every recommendation tagged with its evidence tier — T1 meta-analyses and RCTs through T5 expert opinion. Runs in Claude Code, OpenAI Codex CLI, and (soon) Gemini.
git clone https://github.com/savvides/idstack.git && cd idstack && ./setup
Evidence
Stronger evidence wins when tiers conflict. All 108 references are auditable in evidence/references.md — open source, no proprietary studies, no cherry-picking.
ADDIE, ARCS, ASSURE, and UDL each fit different contexts. Reviews across the literature find no universal best; using two or three frameworks together tends to outperform strict adherence to one.
Objectives, activities, and assessments need to line up; gaps in that sequence predict learning-outcome failures. The revised Bloom's taxonomy supplies the verb vocabulary so each level can be assessed against the level it claims to teach.
Three layers — organizational, task, learner — analyzed before any content gets written. When this step is skipped, courses tend to teach what the designer found interesting rather than what the audience came for.
Working memory limits how much new information learners can hold and manipulate at once. Element interactivity, intrinsic vs extraneous load, and the expertise-reversal effect explain why scaffolding that helps a novice can slow an expert down.
Feedback that explains what to do next produces larger learning gains than feedback that only marks right and wrong. Nicol's seven principles describe what "next" should look like in writing, peer review, and rubric design.
Mayer's principles (coherence, signaling, segmenting, modality, redundancy) predict when combinations of words and visuals help learning and when they interfere with it. Violations produce measurable working-memory load.
Expertise level changes which instructional moves help and which backfire. Scaffolding that supports a novice can interfere with an expert who has already automated the underlying skill.
Evaluation only measures what it was designed to measure, so the design has to happen alongside the course. Kirkpatrick's four levels (reaction, learning, behavior, results) map what's possible; most courses report only the first.
Short iteration cycles with real learners tend to produce better courses than long planning phases, particularly under time pressure. Design-based research formalizes that iteration so it stays methodologically defensible.
Quality Matters' eight standards and the Community of Inquiry framework (teaching, social, cognitive presence) are the two rubrics with the most published validation studies behind them. idstack's quality audit runs against both.
WCAG 2.1 AA is what most jurisdictions require by law. UDL 3.0 (multiple means of representation, action, engagement) sets out how to design for the learner variation real cohorts already contain, rather than retrofitting it later.
Recommendations carry a domain code and tier — [Alignment-14] [T1] — so you can trace any claim back to the source paper. The references file is just Markdown: grep it, fork it, audit it.
Pipeline
Eight of them run end-to-end as the standard sequence; two utilities (course-import and learn) sit outside it. Use one command for the full pipeline, or invoke any skill on its own — none of them require an existing manifest.
Sequence — runs left to right under /idstack:pipeline
Run the full sequence with /idstack:pipeline in Claude Code or $pipeline in Codex CLI. The orchestrator auto-skips completed steps and resumes where you left off.
Output
Every finding-producing skill writes both: a branded HTML report you open in a browser, and a JSON manifest the next skill in the pipeline reads. All per-course artifacts land under one self-describing folder, .idstack/exports/<course-slug>/.
What we saw. Of 8 stated objectives, 3 have no matching assessment item.
What the evidence says. Constructive alignment requires every objective to map to an activity and an assessment; orphaned objectives predict learning-outcome gaps. [Alignment-14] T1
Consider. Run /idstack:assessment-design to close the gap, or remove the orphaned objectives.
{
"learning_objectives": {
"findings": [
{
"id": "obj-3",
"severity": "warning",
"tier": "T1",
"domain": "Alignment-14",
"observation": "3 of 8 ILOs lack assessment",
"consider": "/idstack:assessment-design"
}
],
"report_path": ".idstack/exports/<course-slug>/learning-objectives.html",
"updated": "2026-05-13T14:32:18Z"
}
}
The HTML report is what an instructional designer reads (or hands to a stakeholder — the folder is self-contained, CSS bundled, zip-friendly); the JSON is what /idstack:assessment-design reads next. Both files always reflect the most recent run; the timeline at .idstack/timeline.jsonl carries the run history. /idstack:pipeline additionally writes an index.html course dashboard at the folder root, linking to every per-skill report.
Install
git clone https://github.com/savvides/idstack.git && cd idstack && ./setup
./setup auto-detects which CLIs are on your PATH and installs to whichever you have. Force one with --codex or --no-codex.
New to AI coding tools? Install one first — Claude Code (free download) or Codex CLI (npm install -g @openai/codex). Then paste the command above. When your CLI starts, run /idstack:pipeline (Claude) or $pipeline (Codex).
What's new
./setup now registers idstack as a Claude Code plugin marketplace and installs it from there. Recent Claude Code versions stopped discovering plugins from the bare symlink the old setup created, so /idstack:<skill> commands silently never appeared in the slash picker. If that happened to you, pull the latest and re-run ./setup.
A fresh install is one line: git clone https://github.com/savvides/idstack.git && cd idstack && ./setup. Setup is idempotent, auto-detects Claude Code and Codex CLI on your PATH, and clears out installs from older versions. Restart Claude Code afterward — plugins load at session start.
Next: Gemini CLI, additional specialist skills (content sequencing, media selection, Kirkpatrick evaluation), and push-to-LMS so improvements land back in Canvas without copy-paste. See the roadmap.