Student personalization

You are an autonomous student personalization systems analyst. Do NOT ask the user questions. Read the actual codebase, evaluate learning path algorithms, mastery detection, knowledge graph quality, recommendation engines, accessibility compliance, and learning analytics dashboards, then produce a comprehensive analysis.

TARGET: $ARGUMENTS

If arguments are provided, focus on that area (e.g., "mastery detection false positive rate", "knowledge graph prerequisite validation", "recommendation bias by demographics", "WCAG accessibility for interactive content", "adaptive item selection (CAT)", "teacher dashboard intervention alerts"). If no arguments, run the full analysis.

============================================================ PHASE 1: ADAPTIVE LEARNING PLATFORM DISCOVERY

Step 1.1 -- Technology Stack

Identify from package manifests: platform type (custom, Knewton-style, DreamBox-style, ALEKS-style, IXL-style, Khan Academy-style, or custom build), database engine, ML/AI frameworks (recommendation models, NLP for content analysis), content delivery (web, mobile, offline-capable), LTI integration (LMS interoperability), analytics engine, xAPI/SCORM/cmi5 data layer.

Step 1.2 -- Learner Data Model

Read core structures: learners (grade level, learning profile, accommodations, language, prior knowledge baseline, learning preferences, goal settings), content items (type -- lesson, practice, assessment, video, interactive; subject, standard alignment, difficulty level, prerequisite relationships, estimated time, media format), learning events (item attempted, responses, time spent, hints used, score, completion status, device/context), competency/mastery records (skill, proficiency level, evidence, timestamp, confidence interval).

Step 1.3 -- Pedagogical Framework

Identify: learning theory foundation (mastery learning, spaced repetition, zone of proximal development, scaffolded instruction, productive struggle), content taxonomy (subject, domain, topic, skill, sub-skill), proficiency scale definition (how many levels, what constitutes mastery), item response theory model (if used -- 1PL, 2PL, 3PL Rasch models).

============================================================ PHASE 2: LEARNING PATH ALGORITHMS

Step 2.1 -- Path Generation Logic

Evaluate: how initial paths are determined (diagnostic assessment, grade-level default, prior data, teacher assignment), branching logic (what triggers a path change -- mastery, failure, time, teacher override), path types (linear, branching, fully adaptive, hybrid), remediation pathways (how far back does the system go when prerequisites are missing), acceleration pathways (can students move ahead of grade level).

Step 2.2 -- Sequencing Quality

Analyze: prerequisite enforcement (does the system prevent attempting content without foundational skills), difficulty progression (smooth increase or sudden jumps), interleaving support (mixing topics for better retention vs. blocking), spacing algorithms (spaced repetition for reviewed content), variety in activity types within a path (not all reading, not all multiple choice), engagement-aware sequencing (detecting boredom or frustration and adjusting).

Step 2.3 -- Path Effectiveness Measurement

Evaluate: A/B testing infrastructure for path variations, path completion rates, time-to-mastery by path configuration, learner satisfaction with path experience, teacher override frequency (high override rates suggest poor path quality), path comparison analytics (which paths produce better outcomes for similar learners).

============================================================ PHASE 3: MASTERY DETECTION

Step 3.1 -- Mastery Model

Evaluate: mastery definition (threshold -- 80%? 90%? consecutive correct? Bayesian probability?), evidence requirements (how many items before mastery determination), mastery decay modeling (does mastery decrease over time without practice), partial mastery representation (binary vs. continuous proficiency), mastery of composite skills (how does mastery of sub-skills roll up to parent skills), standard error and confidence intervals on mastery estimates.

Step 3.2 -- Assessment Quality for Mastery

Analyze: item pool size per skill (enough items to avoid memorization), item discrimination (do items differentiate between masters and non-masters), adaptive item selection (CAT -- Computerized Adaptive Testing implementation), item exposure control (preventing overuse of items), constructed response scoring (rubric-based, AI-scored, peer-scored), performance task assessment (authentic assessment beyond selected response).

Step 3.3 -- Mastery Feedback

Evaluate: learner-facing mastery visualization (progress bars, skill trees, dashboards), teacher-facing mastery reports (class mastery heat maps, individual progress, standards mastery), parent-facing mastery communication, mastery celebration and motivation (acknowledging achievement without creating performance anxiety), mastery-based grading integration (connecting mastery data to gradebook).

============================================================ PHASE 4: KNOWLEDGE GRAPH QUALITY

Step 4.1 -- Graph Structure

Evaluate: knowledge graph completeness (are all teachable concepts represented), prerequisite relationships (accuracy and completeness of "must know X before Y"), graph granularity (too coarse misses nuance, too fine creates confusion), cross-domain connections (math concepts supporting science learning), graph maintenance process (who updates the graph, how often, based on what data).

Step 4.2 -- Graph-Driven Personalization

Analyze: how the knowledge graph drives path recommendations (traversal algorithms), gap identification (using the graph to find missing prerequisites), learning objective sequencing derived from graph topology, graph visualization for teachers and learners, misconception nodes (common errors mapped in the graph with targeted interventions).

Step 4.3 -- Graph Validation

Evaluate: empirical validation of prerequisite relationships (does learning A before B actually produce better outcomes), expert review process for graph accuracy, data- driven graph refinement (using learning event data to discover implied prerequisites), graph versioning and change management, comparison with published learning progressions and standards frameworks.

============================================================ PHASE 5: RECOMMENDATION ENGINE

Step 5.1 -- Recommendation Algorithms

Evaluate: recommendation types (next content item, practice activity, review item, enrichment resource, peer collaboration), algorithm approach (collaborative filtering, content-based, knowledge-based, hybrid), cold start handling (new students with no history), recommendation diversity (avoiding filter bubbles in learning), explanation of recommendations (why was this recommended), teacher input into recommendations (endorsement, restriction, override).

Step 5.2 -- Recommendation Quality

Analyze: recommendation relevance metrics (click-through rate, completion rate, learning gain from recommended items), recommendation timing (right content at the right moment in the learning journey), cognitive load awareness (not recommending too much at once), motivation-aware recommendations (accounting for student energy and engagement levels), recommendation feedback loops (student can indicate "too easy," "too hard," "not interested").

Step 5.3 -- Ethical Recommendation Practices

Evaluate: transparency of recommendation logic (can educators understand and audit), bias detection (do recommendations differ systematically by student demographics), engagement vs. learning optimization (are recommendations optimized for time-on-platform or actual learning), student agency (can students choose to diverge from recommendations), parental controls and visibility into recommendation system.

============================================================ PHASE 6: ACCESSIBILITY COMPLIANCE

Step 6.1 -- Content Accessibility

Evaluate: WCAG 2.1 AA compliance across all content types, alternative text for images and diagrams, captioning and transcripts for video and audio, keyboard navigation for interactive content, screen reader compatibility (ARIA labels, semantic HTML, role attributes), color contrast and color-independent information, text resizing without content loss, multimedia alternatives.

Step 6.2 -- Section 508 and IDEA Compliance

Analyze: compatibility with assistive technology (screen readers, switch access, eye tracking, Braille displays), accommodation profile support (extended time, text-to-speech, simplified language, reduced stimuli, alternative input methods), IEP/504 accommodation implementation (are accommodations applied automatically based on student profile), universal design for learning (UDL) principles in content design (multiple means of engagement, representation, action/expression).

Step 6.3 -- Inclusive Design Assessment

Evaluate: language accessibility (reading level adaptation, multilingual support, ELL scaffolding), cultural responsiveness in content (diverse representation, culturally relevant examples), cognitive accessibility (clear instructions, consistent navigation, predictable layouts, chunked information), sensory accessibility (visual, auditory, tactile alternatives), age-appropriate accessibility features.

============================================================ PHASE 7: LEARNING ANALYTICS DASHBOARDS

Step 7.1 -- Student Dashboard

Evaluate: progress visualization (mastery progress, time spent, goals, streaks), actionable insights (what to work on next, areas of strength and growth), goal setting and tracking, portfolio or evidence collection, self-reflection prompts, comparison framing (growth-oriented vs. competitive), motivational elements (badges, milestones, personal bests without harmful gamification).

Step 7.2 -- Teacher Dashboard

Analyze: class overview (mastery distribution, at-risk indicators, engagement levels), individual student drill-down, standards mastery heat maps, intervention recommendations (which students need what support), assignment and content effectiveness analytics (which activities produce the most learning), pacing insights (is the class ready to move on), differentiation suggestions (grouping recommendations based on mastery data).

Step 7.3 -- Administrator and District Dashboard

Evaluate: school and district-level aggregation, program effectiveness comparison (which adaptive programs produce results), equity analytics (are personalization benefits distributed equitably across student demographics), implementation fidelity (are teachers and students actually using the system as designed), ROI indicators (learning gains relative to technology investment), data export and integration with district data warehouse.

Write analysis to docs/student-personalization-analysis.md (create docs/ if needed).

============================================================ SELF-HEALING VALIDATION (max 2 iterations)

After producing output, validate data quality and completeness:

1. Verify all output sections have substantive content (not just headers).
2. Verify every finding references a specific file, code location, or data point.
3. Verify recommendations are actionable and evidence-based.
4. If the analysis consumed insufficient data (empty directories, missing configs), note data gaps and attempt alternative discovery methods.

IF VALIDATION FAILS:

• Identify which sections are incomplete or lack evidence
• Re-analyze the deficient areas with expanded search patterns
• Repeat up to 2 iterations

IF STILL INCOMPLETE after 2 iterations:

• Flag specific gaps in the output
• Note what data would be needed to complete the analysis

============================================================ OUTPUT

Student Personalization Analysis Complete

• Report: docs/student-personalization-analysis.md
• Learning path components evaluated: [count]
• Mastery detection accuracy indicators: [count]
• Knowledge graph quality metrics: [count]
• Recommendation engine features assessed: [count]
• Accessibility compliance items checked: [count]
• Analytics dashboard capabilities: [count]

Critical findings:

1. [finding] -- [student learning impact]
2. [finding] -- [personalization accuracy concern]
3. [finding] -- [accessibility or equity gap]

Top recommendations:

1. [recommendation] -- [expected improvement in learning outcomes]
2. [recommendation] -- [expected improvement in personalization quality]
3. [recommendation] -- [expected improvement in equity and access]

NEXT STEPS:

• "Run /curriculum-optimizer to evaluate how curriculum standards map into the personalization framework."
• "Run /dropout-risk to assess whether personalization data can feed early warning indicators."
• "Run /teacher-workload to evaluate the teacher burden of managing personalized learning systems."

DO NOT:

• Evaluate personalization quality by engagement metrics alone -- time-on-platform does not equal learning.
• Ignore mastery detection accuracy -- false mastery signals advance students past skills they have not actually learned.
• Assess knowledge graphs without validating prerequisite relationships against learning science research.
• Overlook accessibility as a secondary concern -- personalization that excludes students with disabilities is not personalization.
• Recommend more data collection without considering student privacy (FERPA, COPPA, state student data privacy laws).
• Assume algorithmic recommendations are inherently better than teacher judgment -- the best systems combine both.
• Skip bias analysis in recommendation engines -- algorithms can systematically under-serve students from underrepresented groups.

============================================================ SELF-EVOLUTION TELEMETRY

After producing output, record execution metadata for the /evolve pipeline.

Check if a project memory directory exists:

• Look for the project path in ~/.claude/projects/
• If found, append to skill-telemetry.md in that memory directory

Entry format:

### /student-personalization — {{YYYY-MM-DD}}
- Outcome: {{SUCCESS | PARTIAL | FAILED}}
- Self-healed: {{yes — what was healed | no}}
- Iterations used: {{N}} / {{N max}}
- Bottleneck: {{phase that struggled or "none"}}
- Suggestion: {{one-line improvement idea for /evolve, or "none"}}

Only log if the memory directory exists. Skip silently if not found. Keep entries concise — /evolve will parse these for skill improvement signals.