Calisthenics Programming: Skill vs Hypertrophy Phases
Once the beginner routine stops working, alternate blocks that build capacity with blocks that turn it into skill, with a deload between. You can't push both at once.
On this page
For my first year I ran the Recommended Routine: full body, three times a week, add a rep each session until you hit the top of the range, then move to the next progression. It worked brilliantly until it didn’t. Progress slowed, I added more exercises to compensate, and I fell into the pattern I now watch for most closely: plateau → frustration → overtraining → injury.
Getting past that meant learning some programming.
The core idea: blocks, not everything at once
A mesocycle is a block of roughly five or six weeks with one main emphasis, followed by a deload week. I alternate two kinds:
| Hypertrophy / strength block | Skill block | |
|---|---|---|
| Goal | Build muscle and raw strength | Turn that capacity into technique |
| Week | ~2 strength + 2 skill sessions | ~3 skill + 1 strength session |
| Volume | Ramps from 2 to 4 hard sets per exercise | Low volume, high quality, high intensity |
| Feels like | Tiring, sore, satisfying | Fresh, technical, frustrating in a good way |
The reason is simple: skill work is neural, and strength work is fatiguing. Push hard on both and the skill sessions happen while tired, which is exactly when technique degrades. Joints also need a break from long high-volume blocks, and tendons adapt more slowly than muscle (see Deloads and Tendon Adaptation).
Rules I keep coming back to
- Two hard sets is often enough. I want to be fully recovered for the next session. More exercises does not mean more gains.
- Give each strength set everything, with good form. If you feel strong, add a set; adjust next time.
- Bad day? Regress, don’t grind. Switch the skill session to shape and form work and save the real attempt for a day you’re fresh. Strength work needs less coordination, so it survives a bad day better than skill work.
- Heavy, neural lifts don’t go back to back. Heavy weighted pull-ups straight after heavy legs ruins the pulls.
- Two push, two pull, two leg goals at a time. Change little between cycles so progress is actually trackable.
- Failing a skill means missing strength or technique. Rep an easier (banded, partial, eccentric) version in the 3–8 range rather than grinding failed attempts.
- Take the deload on time, or early if progress stalls or fatigue builds. Finish it with a max test.
You can’t serve two masters
My handstand only really clicked when I became a handstand specialist for a few weeks: twice-daily ten-to-fifteen-minute practice that left me fresh, with handstand push-ups, heavy dips and planche parked. Strength work moved to things that didn’t compete for the same recovery: pulling, front lever, compression work and legs.
Endurance training interferes too. During blocks where I was preparing for a Hyrox race, heavy strength work and running fought each other, so I used higher reps and accepted maintenance rather than progress on the bar.
Fitting it into a week
Split choice follows the phase. Push/pull/legs worked well in strength blocks because heavy legs didn’t sabotage pulls and there was room for running. In skill blocks I switched to full body three times a week so each skill was practised more often. AM/PM splits or daily practice at around 60% effort with two sets also work when life is busy; I wrote more about that in Training Around a Busy Week.
The engineering version: build vs harden
Platform roadmaps have exactly the same shape. A team trying to ship new capabilities and improve reliability and migrate everyone to the new thing in the same quarter usually gets none of them. What works better:
- Build blocks: new capabilities, new golden paths, the work that adds capacity.
- Harden blocks: SLOs, docs, migrations, deleting the old path, the work that turns capacity into something people can depend on.
- Deloads between them: dependency upgrades, debt paydown, and time for the organisation to catch up with the code.
- Max test at the end: measure the things you said would improve, then plan the next block.
Saying “this quarter is a harden block” out loud also makes the trade-off visible to stakeholders, in the same way a training plan makes it obvious why you’re not testing your max during a hypertrophy block.
Sources
- Issurin, V. B. (2010). New horizons for the methodology and physiology of training periodization. Sports Medicine, 40(3), 189–206. Block periodisation and why concentrated blocks beat mixing everything.
- Schoenfeld, B. J., Ogborn, D. & Krieger, J. W. (2017). Dose-response relationship between weekly resistance training volume and increases in muscle mass. Journal of Sports Sciences, 35(11), 1073–1082.
- Stronger By Science (strongerbyscience.com), plain-English reviews of periodisation research.
- r/bodyweightfitness wiki, “Developing an intermediate routine”.
- #programming
- #periodisation
- #mesocycles
- #hypertrophy
- #skill-work
↩ Linked from (5)
…ip conditioning. Handstands after a heavy push day were always worse, so I stopped scheduling them there. See Calisthenics Programming: Skill vs Hypertrophy Phases for where this sat in the week.
…it competes with handstand and HSPU work for the same wrists and shoulders. That's a choice, not an accident: Calisthenics Programming: Skill vs Hypertrophy Phases explains why I'd rather focus.
r/bodyweightfitness wiki, on minimal routines and "I don't have time" modifications to the Recommended Routine. Related: Calisthenics Programming: Skill vs Hypertrophy Phases, Golden Paths and the Recommended Routine.
- Weighted Pull-ups and DipsGrowing
…on), Steven Low: weighted pull-up and dip columns. Stronger By Science, on volume and frequency for strength. Calisthenics Programming: Skill vs Hypertrophy Phases for where these sit in the year.
- Zone 2 TrainingGrowing
…of fatigue, not much adaptation. Keep the easy work easy so the hard work can be hard. It's the same logic as Calisthenics Programming: Skill vs Hypertrophy Phases.
↪ Links to (3)
Related by topic
- Growingmetaphor
Deloads Are Tech-Debt Sprints
Calisthenics Lab - Growingmetaphor
Hypertrophy and Skill Phases: Build vs Harden Cycles
Calisthenics Lab - Growingmetaphor
Progressive Overload and Incremental Migration
Calisthenics Lab - Growingmetaphor
Skill Trees as Platform Capability Maps
Calisthenics Lab