| name | progress-tracking |
| description | Track learning progress, monitor milestones, identify skill gaps, analyze learning velocity, and optimize for faster skill development. Use for progress checking, gap analysis, and optimization. |
Progress Tracking Skill
Master the art of monitoring your learning journey, identifying growth patterns, and optimizing for maximum velocity toward your career goals.
Quick Start
/progress dashboard # View overall progress
/progress analysis # Identify skill gaps
/progress velocity # Understand learning pace
/progress optimize # Get optimization suggestions
Core Concepts
Progress Metrics
Learning Velocity:
Measure: Skills mastered per month
Example:
- Month 1: 2 skills (ramp up)
- Month 2-4: 4 skills/month (peak)
- Month 5+: 3 skills/month (sustaining)
Average: ~3.5 skills/month
Quality Score:
Measure: Quality of work (0-100%)
Based on:
- Project quality (code reviews)
- Test coverage (>70% ideal)
- Best practices adherence
- Documentation completeness
Consistency:
Measure: Active days per week
Goal: 5-6 days/week
Benchmark:
- Sustainable: 5-6 days
- Intensive: 7 days (limited duration)
- Struggling: <3 days (assess obstacles)
Retention Rate:
Measure: Knowledge persistence
Timeline:
- Week 1: 90% (fresh)
- Week 4: 75% (good)
- Month 3: 65% (needs review)
- Month 6: 78% (consolidating)
- Year 1: 85% (long-term memory)
Milestone Tracking
BEGINNER PHASE:
✅ HTML Fundamentals
✅ CSS Mastery
✅ JavaScript Basics
✅ Git & GitHub
├─ Checkpoint: 5 simple projects
INTERMEDIATE PHASE:
⏳ JavaScript Advanced (Current)
├─ Sub-skills:
│ ├─ Async/Await (In progress)
│ ├─ Event Loop (Not started)
│ ├─ Closures & Scope (Completed)
│ └─ Error Handling (Completed)
├─ Checkpoint: 3 medium projects
└─ Est. completion: 2 weeks
ADVANCED PHASE:
🔒 React Fundamentals (Locked - prerequisites)
├─ Unlock requirement: JavaScript 70%
├─ Current JS level: 55% (15% to unlock)
├─ Est. unlock date: 2-3 weeks
└─ Time estimate: 10-14 weeks
Progress Dashboard
OVERVIEW:
├─ Current Path: Frontend Developer
├─ Overall Progress: 45% (6 months in)
├─ Learning Pace: 12 hours/week
├─ Quality Score: 82% (Strong)
└─ Consistency: 5.2 days/week ✅
SKILL LEVELS:
HTML ████████████░░░░░░ 78% (Competent)
CSS ██████████░░░░░░░░ 70% (Competent)
JavaScript ██████░░░░░░░░░░░░ 50% (Novice)
Git ████████████░░░░░░░ 75% (Competent)
A11y ████░░░░░░░░░░░░░░░░ 35% (Aware)
Testing ██░░░░░░░░░░░░░░░░░░ 15% (Unaware)
PROJECTS COMPLETED:
✅ Portfolio Website (40 hrs)
✅ Interactive Game (35 hrs)
⏳ Todo App (35% done)
📋 Queued: Weather, E-commerce
MILESTONES:
✅ HTML Fundamentals (Completed Week 3)
✅ CSS Mastery (Completed Week 6)
✅ JavaScript Essentials (Completed Week 10)
⏳ Git Proficiency (15% to unlock Week 15)
🔒 React Basics (Locked - needs JS 70%)
VELOCITY:
Current Pace: 12 hrs/week (Sustainable)
Average Pace: 11.5 hrs/week
Trend: Consistent (slight upward)
Projection: 13 months to job-ready
Skill Gap Analysis
Gap Identification Process
STEP 1: IDENTIFY TARGET
├─ Goal: Full Stack Developer
├─ Timeline: 12 months
└─ Market: High demand
STEP 2: REQUIRED SKILLS
├─ React (must be Level 4)
├─ Node.js (must be Level 4)
├─ PostgreSQL (must be Level 3)
├─ Testing (must be Level 3)
└─ DevOps (must be Level 2)
STEP 3: CURRENT LEVELS
├─ React: Level 1 (0%) - LOCKED
├─ Node.js: Level 2 (25%) - GAP
├─ PostgreSQL: Level 1 (0%) - GAP
├─ Testing: Level 1 (0%) - CRITICAL GAP
└─ DevOps: Level 1 (0%) - LARGE GAP
STEP 4: GAP ANALYSIS
Testing: 3 levels → Critical → 12-14 weeks
DevOps: 2 levels → Large → 10-12 weeks
React: Locked → 4-6 weeks to unlock → 12 weeks after
Node.js: 2-3 levels → Medium → 8-10 weeks
PostgreSQL: 2-3 levels → Medium → 6-8 weeks
STEP 5: PRIORITIZE
Priority Order:
1. Testing (blocking multiple paths)
2. React (time-sensitive, locked)
3. Node.js (medium importance)
4. PostgreSQL (medium importance)
5. DevOps (nice-to-have initially)
STEP 6: ACTION PLAN
Timeline:
├─ Months 1-2: Close Testing gap (start)
├─ Month 2-3: Unlock React prerequisites
├─ Month 3-4: React + continued Testing
├─ Month 5-6: Node.js + Database
├─ Month 7+: Integration and Projects
└─ Month 12: Job-ready
Learning Velocity Analysis
Velocity Measurement
WEEKLY HOURS:
Week 1-2: 6 hrs/week (onboarding)
Week 3-4: 10 hrs/week (building up)
Week 5-10: 14 hrs/week (peak)
Week 11-14: 12 hrs/week (sustainable)
Average: 12 hrs/week
MONTHLY SKILLS MASTERED:
Month 1: 1.5 skills (ramping)
Month 2: 3 skills (accelerating)
Month 3: 4 skills (peak)
Month 4: 3.5 skills (sustaining)
Average: 3 skills/month
PROJECTION AT CURRENT PACE:
To Frontend Ready: 13 months
To Full Stack Ready: 18 months
To Senior Ready: 36+ months
Velocity Optimization
CURRENT BOTTLENECKS:
- Limited project experience (35%)
- Inconsistent study (2 days/week offline)
- Passive learning > active practice (60/40)
- Limited code review feedback
OPTIMIZATION OPPORTUNITIES:
1. MORE HANDS-ON PROJECTS (Highest Impact)
- Current: 1-2 projects/month
- Target: 2-3 projects/month
- Impact: +10% velocity
- Effort: Shift from passive to active
- Timeline: Immediate
2. PAIR PROGRAMMING (Medium Impact)
- Current: No pair programming
- Target: 2 sessions/week
- Impact: +8% velocity (learning + retention)
- Effort: Find peer
- Timeline: 1-2 weeks to arrange
3. TEACH OTHERS (Medium Impact)
- Current: No teaching
- Target: 1 tutoring session/week
- Impact: +12% retention
- Effort: Join mentoring community
- Timeline: Immediate
4. CODE REVIEWS (Medium Impact)
- Current: No external feedback
- Target: Weekly code review
- Impact: +15% quality score
- Effort: GitHub PR communities
- Timeline: Immediate
5. INCREASE STUDY HOURS (Low Impact)
- Current: 12 hours/week
- Potential: 15-18 hours/week
- Impact: +20% velocity (burnout risk)
- Effort: Sacrifice other activities
- Timeline: Unsustainable long-term
RECOMMENDED STRATEGY:
Focus on 1+2+3 (projects + pair + teaching)
Results in +20-30% velocity without burnout
Timeline: 13 months → 10-11 months to ready
Retention Optimization
Spaced Repetition Schedule
ACTIVE LEARNING:
├─ New skill: Review after 1 day
├─ Correct: Review after 3 days
├─ Still correct: Review after 7 days
├─ Still correct: Review after 14 days
├─ Still correct: Review after 30 days
└─ Still correct: Review after 90 days
RETENTION CURVE:
Day 1: 90% (just learned)
↓ Review
Week 1: 75% (need practice)
↓ Practice
Week 2: 70% (practicing)
↓ More practice + teaching
Week 4: 78% (consolidating)
↓ Spacing out reviews
Month 3: 82% (long-term)
Month 6: 85% (very stable)
Year 1: 88% (long-term memory)
Retention Boosters
WHAT WORKS (Ranked):
1. Teaching others (15% retention boost)
2. Building projects (12% boost)
3. Pair programming (10% boost)
4. Weekly code review (8% boost)
5. Writing about it (7% boost)
6. Spaced repetition (8% boost)
WHAT DOESN'T WORK:
❌ Passive watching (2% retention)
❌ Reading without doing (4% retention)
❌ One-time reviews (3% retention)
❌ Watching without notes (2% retention)
Consistency Tracking
Daily Tracking
Mon ✅ 3 hours (Project building)
Tue ✅ 2.5 hours (Course + coding)
Wed ✅ 2 hours (Reading + notes)
Thu ✅ 0 hours (Day off - sustainable!)
Fri ✅ 2.5 hours (Project building)
Sat ✅ 1 hour (Light review)
Sun ❌ 0 hours (Rest day)
Weekly Total: 11 hours
Streak: 5 consecutive days
Pattern: Sustainable with 2 rest days
Motivation Tracking
Consistency Level:
- Motivated: 6-7 days/week
- Sustainable: 4-5 days/week
- Struggling: 2-3 days/week
- At risk: <2 days/week
If Struggling:
□ Review goals and progress
□ Take 1-2 days real break
□ Switch to enjoyable topics
□ Reduce pace temporarily
□ Find accountability partner
□ Connect to outcome (job, freedom, etc)
At Risk Actions:
□ Take week-long break (recovery)
□ Reassess learning path fit
□ Find mentor/support
□ Switch to more engaging resources
□ Consider if goal still relevant
Optimization Recommendations
IMMEDIATE (This week):
1. Add 1-2 more projects
2. Find code review buddy
3. Join study group
SHORT-TERM (This month):
1. Increase to 14-15 hours/week
2. Start weekly code reviews
3. Begin pair programming
4. Start teaching others
MEDIUM-TERM (Next 3 months):
1. Maintain optimizations
2. Consolidate skills
3. Build portfolio projects
4. Prepare for job search
ESTIMATE IMPACT:
Current trajectory: 13 months
With optimization: 10-11 months
Savings: 2-3 months (significant!)
Next Steps
- Review your current dashboard
- Identify your velocity
- Find skill gaps
- Prioritize gap closure
- Implement velocity optimizations
- Track progress weekly
- Adjust based on results
