Home›People›Planner

Planner · curriculum architecture + sequencing

Planner

Curriculum designer for AI Uni. Creates and overhauls courses — designing session arcs, writing exercises, producing seed data and syllabi.

Not in current cascade
  • Agent file.claude/agents/planner.md @ 30e888e9
  • Team membershipSpecialized direct-instance roster
  • ToolsRead · Write · Edit · WebSearch
  • Catalog sectionAGENT-ROLES-AND-RESPONSIBILITIES-CATALOG §3.4
  • Existence statusexists

Summary

Designs and authors complete session content — syllabi, seed data, exercises, resources. Use for course creation and overhaul.

Curriculum designer for AI Uni. Creates and overhauls courses — designing session arcs, writing exercises, producing seed data and syllabi. Works within product requirements set by the stakeholder (Jon) and enforced by the Product Owner agent. Step 1b — Platform Capability Verification: Before designing any section that uses an interactive component, verify component type exists in the platform's COMPONENT_REGISTRY · LessonView renderer supports rendering this component type · component has been tested + verified to render in current architecture. Never write discovery prompts, narration, or tutor_context that references a component until that component's rendering is verified.

Distinguishing characteristicsDifferent from Validator because: planner authors curriculum, Validator audits curriculum. Different from Researcher because: planner sequences pedagogically, Researcher provides evidence. Different from Tutor-Behavior because: planner authors content, tutor-behavior owns tutor-runtime instruction layers. Different from Administrator (NEW class): planner authors curriculum content (syllabi · seed data · exercises), administrator oversees curriculum delivery + cross-course optimization (head-of-school perspective per catalog §4.3). Distinct scopes — Planner ≠ Administrator post-Administrator-class-creation.

Research portfolio

Placeholder reasonNot in current Tier 2 cascade scope (cascade prioritized 8 classes excluding Planner). Future M-1 brief amendment may add Planner to cascade extension; expected research portfolio per pedagogical-design discipline: cognitive science of learning (sibling Researcher Cluster 1) · learning-outcomes design · Kirkpatrick 4-level evaluation · syllabus/seed-data authoring patterns · platform-component capability verification.

Significant project contributionsS75 P0-1 → Cumulative S1+

  • Cumulative S1+ · ongoing · course authoring + overhaul
    Standing curriculum-authoring responsibility — Sessions 1-N seed data · syllabi authoring · exercises · resources design. Works within product requirements set by Jon + enforced by PO agent.
  • S75 P0-1 · 2026-05-06 · Card phrasing correction (PMO turn-21 own-fire)
    Card eyebrow/desc edited to remove `education-administrator mental model` collapse phrasing — Administrator card #13 promoted inline as separate class per catalog §4.3 with distinct curriculum-delivery-oversight scope (head-of-school perspective). Planner ≠ Administrator post-promotion.

Learningsauthored + cross-cutting

Cross-cutting applied

  • Tutor 4-layer priority order (CLAUDE.md SO #9)
    tool-reminders.ts (highest) > client-specific (tutor-prompt.ts / mcp-remote-instructions.ts) > tutor-base.ts > seed data (lowest). Audit ALL layers before modifying ANY. Higher overrides lower.
  • Platform Capability Verification (Step 1b)
    Before designing any section that uses an interactive component, verify component type exists in COMPONENT_REGISTRY · LessonView renderer supports it · tested + verified.

Skills + hooksused + constraining

Skills used (always-loaded)

Primary · structured curriculum design

course-authoring

Session arc design · seed data generation · syllabus authoring. Enforces product requirements + input hierarchy.

Token reference

design-system

AI Uni visual identity · brand tokens · component patterns.

Pedagogy framework

learning-outcomes

Kirkpatrick 4-level evaluation · formative assessment design · portfolio-as-Level-3.

Hooks constraining

  • Tool-scope · agent file frontmatter
    Read · Write · Edit · WebSearch — content authoring authority for syllabi/seed data/exercises.
  • Step 1b component-rendering verification
    Never write discovery prompts, narration, or tutor_context referencing a component until that component's rendering is verified in current architecture.

Last updated · refresh details

  • Profile auto-regenerated2026-05-06T12:50:00Z
  • Refresh cadenceDaily midnight UTC · per-session-end · on-demand button (admin-tier optional)
  • agent file.claude/agents/planner.md @ 30e888e9
  • corpusnot yet authored
  • catalogdocs/agent-knowledge/AGENT-ROLES-AND-RESPONSIBILITIES-CATALOG.md @ d7d1aee8+241affb8

Refresh strategy per HANDOFF v4 §12 — profile auto-regenerates from agent-file + corpus + executions + git log.

Cross-references from the relationship graph

Edges sourced from cross-refs/matrix.json · also browsable on the org chart.

Cross-references 2 skills · 0 hooks

Skills · always-loaded

  • Course-Authoring
    Structured curriculum design — session arc · seed data · syllabus authoring.
  • Learning-Outcomes
    Kirkpatrick's 4 levels · formative assessment · portfolio-as-Level-3.