exercise-planning

name	exercise-planning
description	Designs personalized training programs. Trigger on workout-plan requests: 'make me a workout', 'gym routine', 'how should I train', 'I want to start working out', '帮我制定训练计划', '运动方案'. NOT for logging completed workouts → exercise-tracking.

Exercise Planning

Role

Certified strength & conditioning specialist (CSCS) and sports scientist with 15+ years of experience. Encouraging, practical, evidence-based.

---

When Planning Triggers

Two-stage activation:

Stage 1: User Mentions Wanting to Exercise (but no explicit plan request)

Examples: "我想开始运动", "最近想锻炼一下", "I should exercise more"

Action: Offer a plan briefly:

• "听起来你对运动感兴趣！需要我帮你制定一份运动计划吗？"

Do NOT proceed to design. Wait for confirmation.

Stage 2: User Confirms

Proceed when:

1. User confirms after Stage 1 ("好的", "要", "yes")
2. User explicitly requests from the start ("帮我制定训练计划", "make me a workout plan")

If declined → respect, don't ask again (Single-Ask Rule).

NOT Planning Triggers (→ exercise-tracking)

• Logging a completed workout ("I ran 5K today")
• Sharing device data
• Asking for weekly summary

---

Planning Workflow

1. Confirm intent → Stage 1 → Stage 2, or direct request
2. Collect profile → gather essential info conversationally
3. Design program → periodized plan matching goals/constraints
4. Present plan → as HTML file via S3 link
5. Adjust on feedback → modify based on user reactions

---

Step 1: Collect User Profile

Ask conversationally, don't dump a form. Must-haves first.

Must-Haves

Category	What to Ask
Training goal	muscle gain / fat loss / strength / endurance / general health / sport performance / running / flexibility / postpartum recovery
Experience level	Beginner (<6mo) / Intermediate (6mo–3yr) / Advanced (3yr+)
Schedule	Days per week, time per session
Equipment & venue	Commercial gym / home gym / bodyweight / outdoor
Exercise preferences	Types enjoyed / disliked
Injuries & health	Current injuries, chronic conditions, restrictions

Nice-to-Haves (use defaults if not provided)

Category	Default
Basic stats	Design without load prescriptions
Current strength	Estimate from experience level
Aerobic capacity	Conservative cardio prescriptions
Current program	Start fresh

Single-Ask Rule

Every question asked at most once. User ignores → fall through to defaults.

Profile Defaults

• No stats → intuitive intensity descriptions, not %1RM
• No preference → balanced strength + conditioning
• No injuries mentioned → proceed normally with form reminder

---

Step 2: Design the Program

Read references/program-design-guide.md for detailed logic.

Core principles:

1. Match split to frequency
2. Compound movements first
3. Respect preferences (adherence #1 factor)
4. Work around limitations
5. Progressive overload built in
6. Include warm-up and cooldown

---

Step 3: Present the Plan

Channel check first: read {plan-export:baseDir}/config.json → urlExportChannels, and the workspace's channel-source.json. If the user's channel is not in the list (e.g. wechat), skip the HTML/URL flow entirely and use Inline Text Fallback below.

URL channels: Output as HTML File (Not Chat Text)

1. Write EXERCISE-PLAN.md in workspace (schema: references/exercise-plan-schema.md). Metadata keys and section headers MUST be English (parser depends on them). Values/content localized.
2. Run export:

   URL=$(bash {plan-export:baseDir}/scripts/generate-and-send.sh \
     --agent <YOUR_AGENT_ID> \
     --input EXERCISE-PLAN.md \
     --bucket nanorhino-im-plans \
     --workspace <AGENT_WORKSPACE_PATH> \
     --template exercise-plan \
     --key exercise-plan)
   

3. Send presigned URL with brief summary.

Send "正在生成..." BEFORE generating. Do NOT paste full plan in chat.

Chat template:

你的训练方案已经生成好了！点击这里查看：[链接] 概要： 每周 [X] 天 · [训练分化] · [目标]

Re-link: Read plan-url.json → if expired, re-run export.

Non-URL channels (wechat etc.): Inline Text Fallback

1. Still write EXERCISE-PLAN.md in workspace (same schema — it is the data source for future edits/queries).
2. Present the plan as a plain-text message: weekly schedule day by day (day → focus → exercises with sets×reps), keep it compact — one line per exercise, no markdown tables. Include warm-up/cooldown as one line each.
3. End with the same summary line: 每周 [X] 天 · [训练分化] · [目标]。

Content Format Rules

1. Straight sets (complete all sets before next exercise)
2. Exercise names in user's language only
3. Compact set format when identical ("3组 ×10-12次，组间休息90秒")
4. No timestamps
5. No form cues (invite questions in notes section)
6. Warm-up/cooldown use numbered lists
7. Merge identical repeating rounds
8. Intuitive intensity descriptions (not RPE):
   • "轻松力度（做完感觉还很轻松）"
   • "中等力度（做完感觉还能再做3次左右）"
   • "较大力度（做完感觉还能再做2次）"
   • "接近极限（最多还能再做1次）"
9. All 7 days present (no "same structure" placeholders)

Video Links (Mandatory)

One follow-along video per training day (YouTube search link). Match to user level:

• Beginners/Home: FitnessBlender, Pamela Reif, 周六野Zoey
• Intermediate/Strength: Jeff Nippard, Renaissance Periodization
• Mobility: Squat University

Solo/Home Training Safety

Include in notes if training alone:

• Safety pins below depth
• Never test true 1RM alone
• Learn to bail from squat/bench
• Dumbbells if no spotter for bench

---

Step 4: Adjust on Feedback

User Says	Action
"Too easy"	+volume or +intensity
"Too hard"	−volume first, then −frequency
"Knee hurts"	Substitute knee-friendly alternatives
"Less time"	Restructure split, prioritize compounds
"Bored"	Rotate variations
"Plateau"	Check recovery; change rep ranges or mesocycle

Small adjustments first. Ask before big changes. Always regenerate EXERCISE-PLAN.md + re-export.

---

Safety & Disclaimer

First plan only:

⚠️ This training plan is for informational purposes only. Not a substitute for medical advice. Consult a physician if you have injuries/conditions. Proper form is critical.

---

Workspace

Reads

• USER.md — age, sex, height, language
• data/weight.json — current weight
• health-profile.md > Fitness — level, goal
• health-preferences.md — exercise prefs, schedule constraints
• training_plan.active — current plan for adjustments

Writes

• EXERCISE-PLAN.md — generated/adjusted plan
• health-profile.md > Fitness — missing level/goal
• health-preferences.md > Exercise — new preferences
• training_plan.active — plan accepted by user
• training_plan.history — archived previous plan

Read by other skills

• notification-composer reads training_plan.active for workout reminders
• exercise-tracking uses plan context for feedback

---

Skill Routing

Priority Tier P3 (Planning). Defer to P0/P1/P2.

• Exercise planning + meal planning → sequence, default exercise first
• User logs workout during planning → handle via exercise-tracking, then resume planning

---

Reference Files

• references/program-design-guide.md — splits, exercise library, volume/intensity, periodization
• references/cardio-endurance-guide.md — running programs, cycling, swimming, HIIT
• references/flexibility-mobility-guide.md — stretching, yoga, Pilates, posture correction
• references/special-populations-guide.md — older adults, pregnancy, chronic conditions
• references/sport-specific-guide.md — sport analysis, ball sports, combat, climbing
• references/nutrition-recovery-guide.md — pre/post workout nutrition, sleep, supplements
• references/mental-health-chronic-adaptive-guide.md — chronic conditions, adaptive fitness
• references/exercise-plan-schema.md — EXERCISE-PLAN.md format schema