メニュー
Specialized logic for the final 2-3 weeks before race day: -20%/-40%/-60% volume curve, intensity preservation in race-week-minus-1, race-day shakeout. Called by build-training-plan during plan generation and triggerable mid-cycle if race date changes.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Applies 1/2/3-strike adjustment rules to plan.json based on a single workout's analysis dict. Mutates plan only when thresholds fire. Called after every workout log.
Renders today's workout card from plan.json and daily_state.json as a Markdown block. Use for every /run-today invocation. No writes — pure read-and-render.
Conversationally captures a completed workout (duration, distance, RPE, HR, splits, notes) and writes it to workouts.json. Triggers analyze-workout and adapt-plan downstream. Use for /run-log.
Inserts a post-race or injury-flag recovery block into plan.json: 4 days rest + 3 easy jog days (post-race), or 3 rest + 1 recovery (red-flag-fatigue), or 7 rest days (injury). Use after /run-race-recap or when adapt-plan returns red_flag_recovery.
Web-search-backed Q&A for novel coaching questions outside the plan's standard logic: heat acclimation, recovery from illness, pacing strategies for unique courses. Use for /run-research and when the Coach cannot answer from training data alone.
Aggregates the past 7 days of completed workouts: total mileage, quality session adherence, fatigue indicators (RPE creep, HR drift). Decides hold/advance/recovery for the next week. Use for /run-week.
| name | taper-protocol |
| description | Specialized logic for the final 2-3 weeks before race day: -20%/-40%/-60% volume curve, intensity preservation in race-week-minus-1, race-day shakeout. Called by build-training-plan during plan generation and triggerable mid-cycle if race date changes. |
Modifies the final 2-3 weeks of the training plan into a calibrated taper curve that reduces volume progressively while preserving intensity. Runs scripts/taper.py:apply_taper on the existing weeks list and returns a modified copy. The taper is integrated automatically into every build-training-plan call and can be re-applied independently if the race date shifts.
build-training-plan calls this skill at step 7 (final 2-3 weeks of the generated plan)./run-replan changes the race date, bringing new weeks into the taper window.adapt-plan detects the user is within 3 weeks of race day during a mid-cycle vdot_bump.A modified weeks list (non-destructive — returns deep copies). The caller (build-training-plan or adapt-plan) writes the final plan to storage/plan.json.
See body.md for the exact taper curve and invocation pattern and scripts/taper.py for the implementation.