Practice Review

Step 2: Generate Feedback

Create:

• Summary: 1-2 sentences capturing the session's overall quality
• Highlights: 2-3 specific positives (PRs, consistency, breakthroughs)
• Suggestions: 2-3 actionable next-session recommendations
• Next Focus: One sentence describing the priority for the next session

Plateau Detection

If an exercise's velocity has been near-zero for 2+ weeks (check improvementVelocity):

• Flag it in suggestions
• Recommend: different approach, lower BPM with cleanliness focus, or complementary exercise
• Frame as strategy, not failure: "Plateaus mean your body is consolidating"

Difficulty Adjustment Signals

• 3+ clean sessions at same BPM → suggest +5 BPM
• Rating consistently <= 2 → suggest -10 BPM, switch to fundamentals
• Exercise skipped 3+ times recently → suggest rotating it out

Step 3: Write Output

Write the review to 05_App_Data/practice-tracker/review.json using this exact schema:

{
  "generated": "ISO timestamp",
  "sessionId": "session-id-from-input",
  "summary": "Concise session summary (1-2 sentences)",
  "highlights": [
    "Specific highlight with numbers",
    "Another highlight"
  ],
  "suggestions": [
    "Actionable suggestion for next session",
    "Another suggestion"
  ],
  "nextFocus": "One-sentence priority for next time"
}

Step 4: Write the file

Use the write_file tool to write the review to 05_App_Data/practice-tracker/review.json.

Tone

Direct, respectful, zero cheerleader energy. Like a serious guitar teacher who respects that you're an advanced player. Specific technical observations over generic encouragement.

Good: "Sweep arpeggio PR at 125 — clean enough to push to 130 next time. Legato floor was lower than expected; spend more warm-up time on hammer-ons." Bad: "Great job! You're doing amazing! Keep it up!"