Also check the open GitHub issues. This file holds the long-lived feature backlog. Work that came out of a specific code review or PR triage is tracked as an issue instead, so it stays next to the evidence that produced it:
#60 — an interruptedSHIPPED (v3.5.0.0)idstack-learnings-deletecan destroy the whole log (truncate-in-place)#61 — decide whetherSHIPPED (v3.5.0.0)--cross-projectlets global learnings outrank local ones; the code and the comment above it disagree#62 — remaining test-coverage gaps, one of which is a silent regression todaySHIPPED (v3.5.0.0)The issue is authoritative for its own detail; don't copy it here.
Shipped in v3.5.0.0. Native Chrome Side Panel extension officially published on the Chrome Web Store for in-browser audits in Canvas LMS and Google Docs, automated background Canvas course crawler for multi-page hierarchies, Course Dossier compiler and Markdown exporter, and bin/package-extension.sh packaging tool. Closed issues #60 (atomic learnings deletion with permission preservation), #61 (cross-project local-over-global search precedence), and #62 (slugify stdin/emoji and migrate fallback tests).
v3.4: Single-Host Claude Code Architecture & Automated Doc Verification SHIPPED (v3.4.0.0, v3.4.0.1)
Shipped in v3.4.0.0 and v3.4.0.1. Reconciled architecture to single-host Claude Code plugin. Removed retired Codex CLI target, deleted dist/ and AGENTS.md artifacts. Added test/check-doc-accuracy.py validator script to enforce version parity (v3.4.0.1 / schema 1.4), binary executable permissions, flag accuracy, and relative link integrity across all documentation surfaces. Added test/check-evidence-cards.py to prevent evidence card tier overstatements.
Shipped in v2.4.0.0 with Markdown reports under .idstack/reports/ (historical —
later releases replaced that path with self-contained HTML reports under
.idstack/exports/<course-slug>/, which is the current contract). Every
finding-producing skill writes both .idstack/project.json (system state) and a
human-view report following the canonical observation → evidence → why-it-matters
→ suggestion structure in templates/report-format.md. /idstack:pipeline
produces the cross-cutting aggregate (now index.html in the export folder)
with top recurring issues, evidence themes, and where to start. Plus
install-hygiene fix: setup actively removes pre-v2.0.1.0 dispatcher clones,
smoke-test catches the regression, new bin/idstack-doctor for diagnostics.
Shipped in v1.2.0. bin/idstack-migrate handles schema migrations.
Every skill preamble calls it automatically (7 skills at the time; 11 now).
Shipped in v1.2.0. Four checks added to /course-quality-review: cognitive load, multimedia principles, feedback quality, expertise reversal. Plus: fix-link integration, quick-win prioritization, score trending, shareable quality report, and per-category scoring breakdown.
Shipped in v1.5.0. bin/idstack-gen-skills generates SKILL.md from .tmpl templates.
Shared preamble (update check, manifest check, context recovery) maintained in
templates/preamble.md. Contributors edit .tmpl files, run gen-skills to regenerate.
The remaining skill suite from the evidence synthesis includes 4 more skills:
- id-model-selector (Domain 1) — context-driven model/framework recommendation
- content-sequencing (Domain 4) — cognitive load-aware sequencing and chunking
- media-selection (Domain 6) — multimedia principle application and violation flagging
- evaluation-design (Domain 8) — Kirkpatrick+ evaluation planning Why: Extends coverage for specialized ID workflows. Each backed by evidence synthesis. Depends on: User feedback on which capabilities are most requested. Note: assessment-design, course-builder, and course-export are now shipped (v1.1). learner-analysis is partially covered by /needs-analysis (Level 3) and /course-import. prototype-iteration overlaps with the build/export pipeline.
Add Blackboard (xAPI), Moodle (web services), and D2L (Valence API) as import sources alongside Canvas. The IMS Common Cartridge format covers these generically, but LMS-specific APIs unlock richer data (rubrics, analytics, student engagement). Why: Each LMS has unique data that cartridge export doesn't capture. Depends on: /course-import Canvas API path stable and tested. User demand. Priority: P3
Shipped in v1.4.0. SCORM 1.2/2004 import added as Path E in /course-import. SCORM 1.2 export added as Path C in /course-export. PDF import also added (Path D).
Shipped in v1.5.0. Pipeline progression guidance now generates dynamic next-step recommendations based on timeline data. The shared preamble handles this consistently across all skills.
Shipped across v2.0 and v2.2. /accessibility-review runs WCAG and UDL as parallel sub-agents; /course-quality-review parallelizes its QM/CoI/alignment dimensions; v2.2 moved /red-team into a clean-context sub-agent that returns to the parent for a triage-and-fix loop (Critical / Critical+High / All / Skip).
Add bin/idstack-config for persistent user preferences (auto-update on/off, default
export format, context recovery verbosity). Plain YAML at .idstack/config.yaml.
Why: As course memory adds configurable behaviors, users need a way to set preferences.
Depends on: Course memory system (v1.5.0) proving useful. User feedback on what
to make configurable.
Priority: P3
Enable learnings and patterns to transfer across courses (e.g., PSY101 to PSY201).
Requires a global storage location (~/.idstack/global/learnings.jsonl) alongside
the project-local .idstack/ files. Institutional knowledge compounds across semesters.
Why: IDs who teach multiple courses discover the same quirks repeatedly.
Depends on: Course memory system (v1.5.0) in use. Needs design for how global
vs project-local learnings interact.
Priority: P2
Give idstack.org a pre-install demo. The redesign removed the old "See it work" transcript section, so today a visitor sees the evidence cards, the pipeline diagram, and a sample report excerpt, but never watches a skill run. Options: animated terminal replay (CSS-only, building on the existing typing animation), a clickable pipeline explorer showing what each of the 11 skills does, or expanded sample output with evidence citations. The goal is to let prospective users experience the value before installing. Why: CEO review killed a post-install /demo command because IDs always have a course. The real TTHW problem is pre-install: visitors on idstack.org need to understand the value before committing to install. The landing page demo is where that conversion happens. Depends on: Design review of the current landing page to identify what's working and what's not. User feedback on whether the current "See it work" section clearly demonstrates the workflow. Priority: P2
Push changes back to Canvas (and eventually other LMS) via API. After /course-quality-review identifies issues and /learning-objectives generates better ILOs, push the improvements back to the LMS. The output IS the course. Why: The 10x vision. Eliminates the translation step from design doc to LMS. Depends on: /course-import stable, Canvas API write operations investigated, conflict handling designed, institutional partnerships.