name: review-learning description: Use when user requests learning progress review, assessment, or evaluation of any learning item in MasterAnything framework. Triggers: "review progress", "how am I doing", "assess my learning", "check my progress", "am I on track".
Review Learning Progress
Overview
Systematically evaluate learning progress against defined goals and milestones, providing actionable insights and updating progress records.
Core principle: A review must compare actual progress against planned goals, not just summarize what was done.
When to Use
digraph review_trigger {
"User asks about learning progress?" [shape=diamond];
"Specific learning item mentioned?" [shape=diamond];
"Use this skill" [shape=box];
"Use different approach" [shape=box];
"User asks about learning progress?" -> "Specific learning item mentioned?" [label="yes"];
"Specific learning item mentioned?" -> "Use this skill" [label="yes"];
"User asks about learning progress?" -> "Use different approach" [label="no"];
"Specific learning item mentioned?" -> "Use different approach" [label="no"];
}
Triggers:
- "Review my progress"
- "How am I doing with [topic]?"
- "Assess my learning"
- "Check my progress"
- "Am I on track?"
- "Review [learning item name]"
When NOT to use:
- Starting a new learning session (use
/study) - Creating a new learning item (use
/new-learning)
Core Pattern
Before (Baseline - Missing Elements)
## Current Status
- Stage: Novice
- Time: 0.5 hours
- Progress: 5%
[Summarizes what was done, no evaluation]
After (With Skill - Complete Review)
## Timeline Assessment
- Expected: Novice stage complete by 2025-02-09 (1 week)
- Current: 5% complete, 0.5 hours invested
- Status: Behind schedule (need 2+ hours/day to catch up)
## Milestone Evaluation
- Completed: 3/10 Novice milestones
- Missing: Character classes, anchors, email matching
- Next priority: Complete character classes (blocks all next steps)
## Learning Patterns
- Frequency: One 30-minute session (needs daily practice)
- Focus: Theory over practice (no code examples yet)
- Trend: Good documentation, insufficient application
## Action Plan
1. Complete character classes today (blocks progress)
2. Add 15-minute daily practice sessions
3. Create one regex example per concept learned
Quick Reference
| Review Component | What to Check | Where to Find It |
|---|---|---|
| Timeline | Planned vs actual dates | README.md roadmap, progress.md dates |
| Milestones | Completed vs required | README.md checklist, progress.md logs |
| Time Investment | Hours vs expectations | progress.md time tracking |
| Learning Patterns | Frequency, focus, gaps | progress.md log entries |
| Resource Usage | Tools referenced vs used | resources.md, notes content |
| Flashcards | Cards created, mastery level | flashcards/*.md |
| Spaced Repetition | Review completion rate, overdue items | reviews/spaced-repetition.md |
| Blockers | Missing prerequisites | README.md dependencies in milestones |
Implementation
Step 1: Read Core Files (Always)
# Use Read tool for these files first
[learning-item]/README.md # Goals, milestones, roadmap
[learning-item]/progress.md # Time tracking, completion status
[learning-item]/notes/*.md # Learning evidence, patterns
[learning-item]/reviews/spaced-repetition.md # Spaced repetition status
[learning-item]/flashcards/*.md # Flashcard mastery data
Step 2: Timeline Assessment
Calculate:
- Expected completion date for current stage (from README.md)
- Days elapsed since start date
- Expected hours per week vs actual
- Pace: "On track", "Ahead", or "Behind"
Example calculation:
Novice stage: 1 week expected
Started: 2025-02-02
Today: 2025-02-09
Expected: 5-7 hours total (1 hr/day)
Actual: 0.5 hours
Status: Behind (need 6.5 hours in remaining days)
Step 3: Milestone Evaluation
Check each milestone in current stage:
- Mark for completed checklist items in README.md
- Mark for incomplete items
- Identify blocking items (prerequisites for next steps)
Example:
### Novice Milestones
- Explain basic concepts
- List 10+ metacharacters
- Complete environment configuration (NOT DONE)
- Run first example (BLOCKED by env config)
Step 4: Pattern Recognition
Analyze progress.md log for patterns:
| Pattern | What to Look For | Indicator |
|---|---|---|
| Frequency | Days between sessions | Consistent? Gaps? |
| Duration | Minutes per session | Too short? Too long? |
| Focus | Theory vs practice | Any code/projects? |
| Blockers | Repeated problems | Same issue multiple times? |
| Momentum | Progress over time | Accelerating? Stalling? |
Example finding:
Pattern: Single 30-minute session, then 7-day gap
Issue: Insufficient frequency for retention
Recommendation: Daily 20-minute sessions better than weekly 2-hour sessions
Step 5: Generate Recommendations
Prioritize by impact:
- ** Critical** - Blocks all progress (e.g., environment not set up)
- ** Important** - Slows progress significantly (e.g., missing foundation)
- ** Suggestion** - Optimizes learning (e.g., add practice)
Format:
## Action Plan (Priority Order)
### Critical (Complete Today)
1. Set up environment (blocks all next steps)
- Run: [specific command]
- Verify: [how to confirm it works]
### Important (This Week)
2. Complete character class module
- Time needed: 1 hour
- Resources: [link to section]
### Suggestions (Ongoing)
3. Add daily practice sessions
- Current: 30 min once/week
- Recommended: 20 min daily
- Reason: Spaced retention better
Step 6: Update progress.md
Append review findings:
## Learning Reviews
### 2025-02-09 - Weekly Review
**Reviewer**: Claude (review-learning skill)
**Timeline**: Behind schedule (0.5h / 7h expected)
**Milestones**: 3/10 Novice tasks complete
**Key Finding**: Environment setup not complete, blocking progress
**Action**: Set up environment today, then complete character classes
**Next Review**: 2025-02-16
Common Mistakes
| Mistake | Why It's Wrong | Fix |
|---|---|---|
| Only summarizing, not evaluating | Doesn't help user improve | Compare against goals explicitly |
| Ignoring timeline | User can't adjust effort | Show expected vs actual pace |
| Not checking README.md milestones | Misses completion criteria | Always evaluate checklist items |
| Skipping pattern analysis | Misses systemic issues | Analyze frequency, duration, focus |
| No progress.md update | Review insights lost | Append review to progress.md |
| Generic advice | Doesn't address specific gaps | Tie recommendations to missing milestones |
Real-World Impact
Before this skill: Reviews were summaries ("You learned metacharacters, good start!") with no assessment of whether the user was on track to meet their goals.
After this skill: Reviews provide concrete timeline assessments ("Behind schedule - need 2 hours/day to catch up"), identify blocking issues ("Environment setup blocks all progress"), and document findings in progress.md for future reference.
Skill version: 1.0 Last updated: 2025-02-02