gtapps/weekly-coaching-patterns

Weekly Coaching Patterns

Scheduled-check skill: reads the last 4 compiled/activity-*.md artifacts for steady sessions and detects whether cardiac drift is trending upward over time. Returns a fixed findings block for reflect --scheduled-checks to classify and route.

Contract: idempotent, read-only, no self-scheduling, short-running. Returns findings or silence — never creates proposals itself.

Steps

1. Run the trend check. Issue a single Bash call:

   bun ${CLAUDE_PLUGIN_ROOT}/scripts/fitness-lab.ts weekly-patterns
   

   The script does the whole deterministic pass — filesystem only, no Strava token: globs .claude-code-hermit/compiled/activity-*.md, keeps entries whose frontmatter has type: activity-note AND session_kind: steady, takes the 4 most recent by created, reads each note's signed drift from the cardiac_drift_bpm frontmatter field, falling back to the body's Cardiac drift: line for notes written before that field existed (neither present → excluded; a negative value compares as smaller than any positive — the sign is never stripped), and evaluates a strict oldest-to-newest monotonic rise across all 3 adjacent pairs. It emits:

   {"steady_sessions_found": <int>, "series": [{"file": "…", "date": "…", "drift": <signed int>}], "trend": "upward" | "none" | "insufficient-data"}
   

   series is ordered oldest-to-newest. trend: "upward" means the 4-value bpm series is strictly increasing (the deliberately strict v1 bar — avoids false positives from noisy week-to-week variation). "none" = 4 values but not monotonic; "insufficient-data" = fewer than 4 drift values (expected on interval/strength-heavy weeks — not an error).

   Anti-duplication guard: emit a finding ONLY on trend: "upward" (the quantitative numeric rise). Do NOT emit on label recurrence alone.

2. Output the findings block. Always output a plain-text findings block to stdout, regardless of outcome. reflect --scheduled-checks classifies the result from this block.

   trend: "upward":

   weekly-coaching-patterns findings — <YYYY-MM-DD>
   Coaching patterns: 1
   - Coaching pattern detected [cardiac-drift-high]: cardiac drift rising across 4 consecutive steady sessions (<V1>→<V2>→<V3>→<V4> bpm) — check pacing strategy and hydration; consider an easy recovery run next session
   

   Replace <V1>…<V4> with the four series[].drift values in order (oldest-to-newest, each rendered with its sign, e.g. +6), and <YYYY-MM-DD> with today's date.

   trend: "none" or "insufficient-data":

   weekly-coaching-patterns findings — <YYYY-MM-DD>
   No actionable findings.
   

   The [cardiac-drift-high] label reuses the seed vocabulary from activity-deep-dive step 7b — no new label is introduced.

Example

Four steady sessions, oldest-to-newest, with drift lines +4, +7, +9, +13:

weekly-coaching-patterns findings — 2026-05-31
Coaching patterns: 1
- Coaching pattern detected [cardiac-drift-high]: cardiac drift rising across 4 consecutive steady sessions (+4→+7→+9→+13 bpm) — check pacing strategy and hydration; consider an easy recovery run next session

The same four sessions with values +4, +7, +6, +13 do not hold (the +7→+6 pair falls), so the output is the No actionable findings. block. A series of -3, +1, +5, +9 does hold (every pair rises; the leading negative compares as smallest).

Extend-if-useful (not in v1)

The following metrics follow the same steady-session pattern and would add items to the Coaching patterns list. NOT implemented in v1 — cardiac drift alone proves the mechanism end-to-end.

• Z2 pace/HR efficiency slope — extract Pace/HR efficiency: X.XX min·km⁻¹·bpm⁻¹ from each artifact; detect a strictly declining trend across the 4 steady sessions. Label: efficiency-regression.
• Recovery-score trend — extract Recovery: N/5 from each artifact (applies to both steady and interval sessions); detect a strictly hardening trend across the 4 sessions. Label: recovery-insufficient.

Notes

• This skill writes no artifact. All output goes to stdout for reflect --scheduled-checks to classify and route. Runtime state (last_run, consecutive_empty, etc.) is written by reflect --scheduled-checks to state/reflection-state.json → scheduled_checks.weekly-coaching-patterns — not by this skill.
• Registered by /claude-code-fitness-hermit:hatch step 8c via a scheduled_checks config entry (interval_days: 7). The core daily scheduled-checks routine fires reflect --scheduled-checks, which picks it up once 7+ days have elapsed since last_run.
• The [cardiac-drift-high] label has two upstream producers. activity-deep-dive step 7b writes single-session observations (graduated to proposals via reflect's current-session path); this skill emits on a multi-session trend. Both flow into proposal-triage, which dedups — so a triage DUPLICATE verdict here is expected behavior, not a bug.