Fitness Program — Full Design Pipeline

Workflow

Phase 1: Preparation (Orchestrator handles directly)

1. Extract from user input:
   • Goal: hypertrophy / strength / fat loss / fitness improvement / rehabilitation
   • Fitness level: beginner / intermediate / advanced, training history
   • Available resources: X sessions/week, X minutes/session, equipment (gym / home / bodyweight)
   • Physical info (optional): sex, age, height, weight
   • Injury history (optional): area, current condition
   • Existing program (optional): currently running program
2. Create a _workspace/ directory at the project root
3. Organize inputs and save to _workspace/00_input.md
4. Determine execution mode based on request scope

Phase 2: Team Assembly and Execution

Tasks 2a (exercise guide) and 2b (nutrition pairing) run in parallel.

Inter-agent communication flow:

• architect completes → sends exercise list and precautions to guide, sends intensity/volume/goal to linker, sends periodization schedule to builder
• guide completes → sends high-intensity exercise list to linker, sends logging items to builder
• linker completes → sends nutrition tracking items to builder
• builder integrates all information to create the template; if missing items are found, requests clarification from the relevant agent

Phase 3: Integration and Final Deliverables

1. Review all files in _workspace/
2. Verify consistency across program–schedule–guide–nutrition–template
3. Report final summary to the user:
   • Program design doc — 01_program_design.md
   • Weekly schedule — 02_weekly_schedule.md
   • Exercise guide — 03_exercise_guide.md
   • Nutrition pairing chart — 04_nutrition_plan.md
   • Tracking template — 05_tracking_template.md

Mode by Request Scope

Using existing files: If the user provides an existing program, copy it to _workspace/01_program_design.md and skip the architect.

Data Transfer Protocol

File naming convention: {order}_{agent}_{deliverable}.{extension}

Error Handling

Test Scenarios

Normal Flow

Prompt: "I'm a beginner at the gym and want a hypertrophy-focused program, 4 days a week. 178cm, 75kg, 28-year-old male." Expected output:

• Program: upper/lower 4-day split, 12-week periodization (adaptation → accumulation → intensification → deload)
• Schedule: 4 sessions/week × 60 min, sets/reps/RPE specified per exercise
• Guide: form descriptions + substitutions for all exercises in the program (15–20 exercises)
• Nutrition: bulk-up calories (TDEE+300), macros, pre/post-workout timing
• Template: daily log, weekly summary, 4-week evaluation form, body composition tracker

Existing File Flow

Prompt: "Here's my current PPL routine — can you pair it with a diet?" + program file attached Expected output:

• Copy existing program to _workspace/01_program_design.md
• Nutrition mode: deploy linker, analyze existing program intensity, generate nutrition pairing chart

Error Flow

Prompt: "I have a herniated disc — create a workout program for me." Expected output:

• Injury history applied: exclude high-lumbar-load exercises (deadlifts, barbell squats)
• Include core stabilization exercises, suggest substitutes (leg press, machine-based)
• All exercises marked with "lumbar caution" ⚠️ + "consult orthopedics/rehabilitation medicine"
• Progressive overload set more conservatively

Per-Agent Extended Skills