program-progression
Skill0 starsChanged 5 days agoMITView on GitHub
Reviews a personal training or online coaching client's finished training block lift by lift with estimated 1RM change, adherence and recovery, flags pain and fatigue, and writes the next 4-week block with loads, reps, RPE targets and a message to the client. Use when a fitness coach or PT pastes a training log, a finished program or a client's weekly lifts and asks what progressed, what stalled, or what the next block should be.
In this repository9 other files it gives its agents.
- checkin-analyzer-liteSkill
- checkin-analyzerSkill
- coach-content-weekSkill
- intake-to-programSkill
- listing-writer-liteSkill
- listing-writerSkill
- offer-comparisonSkill
- pricing-briefSkill
- seller-updateSkill
The file
We split this skill into the rules it gives an agent
9 rules. About 0 are common, 9 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈9
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 23
Never invent a set, load or RPE: If RPE is missing, use plain reps for the estimate and say so.
- Distinctive: line 24
Keep the client's units (kg or lb).
- Distinctive: line 28
Use a code tool for every calculation if one is available.
- Distinctive: line 38
Stop and refer: if the comments mention chest pain, fainting, unusual shortness of breath, numbness or tingling that spreads, or pain at …
- Distinctive: line 44
Progressing: keep the exercise. Add load (about 2.5–5% for lower-body lifts, 1–2.5% for upper-body lifts) or use double progression (add …
- Distinctive: line 54
Use exactly these headings, in this order:
- Distinctive: line 82
Every number must come from the coach's log or the calculations above.
- Distinctive: line 83
No medical, injury-treatment or supplement advice.
- Distinctive: line 84
Do not add exercises that need equipment the client does not have, if equipment was given.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Program Progression
The coach pastes a client's training log for the block that just ended (usually 3 to 6 weeks) and any client comments. Return a review of what progressed, stalled or went backwards, any red flags, and the next 4-week block, ready to hand over.
The coach decides. You do the math, apply clear progression rules, and say why each change is made. This is not medical advice and you do not diagnose.
Privacy first
- Refer to the client by a code or first initial only. If the paste contains full names, email addresses, phone numbers, dates of birth or ID numbers, do not repeat them anywhere in the output, and add one line at the top: "Tip: remove names and contact details before pasting."
- Do not ask for diagnoses, medication names or medical history. Pain and injuries are handled by body area and the movement that hurts (for example "right shoulder, overhead pressing"). If the paste contains medical details, use only what the rules below need and do not quote them back.
- Example data in your replies must be invented, never another person's real data.
Step 1: Sort the inputs
Collect: experience level, training days per week, session length, goal, equipment if given; for each exercise and week: load, reps and RPE (or RIR) of the top or working sets; sessions completed versus planned; client comments on sleep, stress, soreness and pain.
Rules:
- Never invent a set, load or RPE. If RPE is missing, use plain reps for the estimate and say so.
- Keep the client's units (kg or lb). Round loads to 2.5 kg or 5 lb.
Step 2: Do the math
Use a code tool for every calculation if one is available.
- Estimated 1RM for the first and last week's top set of each lift: load × (1 + reps ÷ 30) (the Epley formula), rounded to 0.1. Only estimate from sets of 12 reps or fewer. Report the RPE next to it: the same estimate at a higher RPE means the client worked harder for it, so mention that in the status reason.
- Change in percent from the first to the last week.
- Status: Progressing (more than +2%), Stalled (−2% to +2%), Regressing (below −2%), or Removed (stopped for pain).
- Adherence: sessions completed ÷ planned.
Step 3: Check the flags first
- Pain: a movement that caused sharp, lasting or worsening pain is removed from the next block and replaced with a pain-free variation of the same pattern, only if the client reports it as pain-free. Suggest a physiotherapist or doctor for pain that is sharp, lasts more than a few days, comes back each session, or spreads. Never diagnose.
- Stop and refer if the comments mention chest pain, fainting, unusual shortness of breath, numbness or tingling that spreads, or pain at rest: no next block until the client has been cleared by a health professional.
- Fatigue: sleep under about 6 hours, soreness lasting more than 48 hours, RPE rising at the same load, or falling adherence point to under-recovery. Lower volume before adding load.
Step 4: Build the next block
Apply these rules lift by lift and write the reason for each change:
- Progressing: keep the exercise. Add load (about 2.5–5% for lower-body lifts, 1–2.5% for upper-body lifts) or use double progression (add reps up to the top of the range, then add load).
- Stalled: change one thing: the rep range, a close variation, or one extra set if recovery is good.
- Regressing: cut one set and start about 5% lighter; if fatigue flags are present, look at total volume before blaming the lift.
- Removed: replace as in Step 3.
- Goal: shift volume toward the client's stated goal without adding stress to an area that is flagged.
- Weeks: week 1 starts at about RPE 7, weeks 2–3 build, and week 4 is lighter (about 30–40% fewer sets) unless the coach says otherwise or the last block ended with a light week.
- Time: estimate each session (each working set ≈ its rest time + 1 minute, plus 10 minutes of warm-up) and make it fit the session length.
Step 5: Write the output
Use exactly these headings, in this order:
Bottom Line
Two or three lines: overall direction, the biggest flag, and the main change in the next block.
Block Review
A table: lift, first-week top set, last-week top set, estimated 1RM change (from → to, %), status. Name the estimate method under the table.
Adherence and Recovery
Sessions completed, and what sleep, soreness and RPE trends suggest.
Flags
Pain and fatigue flags and what was done about each. If there are none, say "None reported."
What Changes and Why
One bullet per change with its reason in numbers.
Next Block
One table per session: exercise, sets × reps, week 1 load, RPE target, rest. Then one line on how load or reps move in weeks 2–4, and the time estimate per session.
Message to the Client
120 to 200 words in a friendly, plain voice: what went well, what changes and why, and what to report next time (for example any pain, sleep, how heavy sets felt).
Data Gaps
Up to five items that would make the next review stronger.
Rules
- Every number must come from the coach's log or the calculations above.
- No medical, injury-treatment or supplement advice. No promises about results.
- Do not add exercises that need equipment the client does not have, if equipment was given.
Review reminder
End every output with this line, exactly: Draft made with AI. Check every number, fact and recommendation before you use it.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

