Skip to content

/vt-c-learning-metrics

View ROI metrics for the learning system

Plugin: core-standards
Usage: /vt-c-learning-metrics [--since 7d]

/vt-c-learning-metrics

Display metrics dashboard showing learning system effectiveness and ROI.

Usage

/vt-c-learning-metrics              # Full dashboard (default)
/vt-c-learning-metrics --since 7d   # Only last 7 days (future enhancement)

What It Shows

  • Total solutions documented and reused - How many documented solutions have been referenced
  • Time saved from solution reuse - Cumulative time saved by not re-researching problems
  • Bugs prevented by pattern detection - Issues caught before they occurred
  • Verification loop effectiveness - How often Ralph Wiggum loops prevent false completions
  • Pattern promotion statistics - Automatic vs manual promotions to Required Reading
  • Compounding impact over time - Visual representation of knowledge growth

How It Works

  1. Reads 4 metrics JSON files:
  2. metrics/solution-reuse.json - Logged when learnings-researcher finds reusable solutions
  3. metrics/pattern-usage.json - Logged when critical patterns prevent bugs during planning
  4. metrics/verification-loops.json - Logged by ralph-wiggum-loop skill

  5. metrics/pattern-promotions.json - Logged when patterns auto-promote at 3+ occurrences

  6. Calculates ROI metrics:

  7. Time saved = Sum of estimated time savings from all reuses and pattern prevention
  8. Bugs prevented = Count of issues caught by pattern detection

  9. Verification effectiveness = Average loop count and false claims prevented

  10. Generates markdown dashboard with:

  11. Summary statistics
  12. Top reused solutions
  13. Pattern prevention breakdown
  14. Compounding impact visualization

Routes To

learning-metrics skill

Example Output

# Learning System Metrics

Generated: 2026-01-27 23:30:00

## 📊 Summary

| Metric | Value |
|--------|-------|
| Solutions Documented | 47 |
| Solutions Reused | 23 |
| **Total Time Saved** | **625 min (10.4 hrs)** |
| Bugs Prevented | 8 |
| Avg Verification Loops | 1.8 |

## 🔄 Top Reused Solutions

| Solution | Reuses | Time Saved |
|----------|--------|------------|
| N+1 Query Prevention | 5 | 125 min |
| Missing Eager Loading | 4 | 100 min |
| Email Threading Patterns | 3 | 75 min |

## 🛡️ Pattern Prevention

| Pattern | Uses | Bugs Prevented |
|---------|------|----------------|
| Input Validation | 4 | 3 |
| Async Timing Issues | 2 | 2 |

## ✅ Verification Effectiveness

- **Total Verification Runs**: 23
- **Average Loop Count**: 1.8
- **False Claims Prevented**: 12
- **Success Rate**: 95.7%

## 🎯 Pattern Promotions

- **Auto-Promoted**: 3
- **Manual Promotions**: 1
- **Avg Occurrences Before Promotion**: 3.2

## 💡 Compounding Impact

**This is investment #47 in your knowledge base.**

Each solution makes the next one faster. The system is getting smarter with every documented problem.

**Time Savings Trend**:
- First-time problem solving: ~30-60 minutes (research + trial/error)
- With documented solutions: ~2-15 minutes (lookup + implementation)
- **Net savings per reuse**: ~25-45 minutes

**Projected ROI**:
- At 23 reuses: Already saved 625 minutes (10.4 hours)
- If current solutions are each reused 3 more times: Potential 1,500+ minutes savings

When Metrics Are Generated

Metrics are automatically logged during normal workflow execution:

  1. Solution Reuse - When /vt-c-wf-plan runs learnings-researcher agent and finds relevant solutions
  2. Pattern Prevention - When critical patterns from cora-critical-patterns.md are detected during planning
  3. Verification Loops - When /vt-c-wf-work --autonomous uses Ralph Wiggum verification
  4. Pattern Promotions - When /vt-c-compound detects 3+ occurrences of same root cause + component

To generate metrics: Simply use the normal workflows (/vt-c-wf-plan, /vt-c-wf-work, /vt-c-compound). The system tracks everything automatically.

Notes

  • First run: Will show empty metrics with helpful "getting started" message
  • Performance: Executes in < 100ms by reading JSON files only
  • No external dependencies: Uses only local metrics files
  • Privacy: All metrics stored locally, nothing sent externally