coachlisted

# coach, the longevity + fitness coach Reads everything health-mcp knows (recovery, sleep score, sleep regularity, cycle phase, somatic state, longevity panel, out-of-range labs, Floor from today's journal) and issues a prescription that's specific to THIS person on THIS day. Progressive overload tracked per-lift. Deload every 4th week. Calendar drop optional. This is the substrate's coach SURFACE. The DATA + DECISION layer lives in `services/health-mcp/coach.py`. The VOICE + WORKOUT TEMPLATES + CALENDAR INTEGRATION live here. ## When to use - User says `/coach`, `/coach today`, `/coach week`, `/coach profile`, `/coach log` - User asks "what should I do today" / "give me a workout" / "build me a week" / "how should I train" - User wants a longevity plan - User wants to log a completed workout (RPE + lift actuals) - User wants to see progression on a specific lift - Scheduled morning task fires to drop today's workout into calendar Do NOT use for: - Importing health data (use `/ingest-health` or `/health-setup`) - Querying past biometrics without prescribing (use `health_status`, `health_metric_series`) - Building new wearable connectors (substrate dev task) ## First time: profile setup When `/coach profile` runs (or `/coach` runs and no profile exists), ask the user these 12 questions and save the answers to `<vault>/Meta/coach-profile.yaml`. Never re-ask once saved unless they say something changed. 1. **Primary goal:** lose weight, build muscle, run a 5K, get more a