Beneath Every Standard: Learning Competencies and Progressions

A standard is a destination. It tells you where a student should be able to stand at the end of a grade — "solve word problems involving addition and subtraction of fractions," "cite textual evidence to support analysis." What it does not tell you is the route: which smaller skills a student has to acquire first, in roughly what order, and where the whole thing tends to fall apart. Every experienced teacher carries that route in their head. It's most of what expertise is — and it's exactly what's missing when a generic AI tool hands you a lesson that names the standard but has no idea how students climb to it.

Claude for Teachers closes that gap by reaching past the standard to the two things beneath it: the learning competencies a standard is built from, and the progression — the order students typically learn them. Those come from the Learning Commons Knowledge Graph connector, and they are the reason a Claude-planned lesson can actually be scaffolded rather than merely labeled. This piece is about that hidden layer: what competencies and progressions are, why they matter more than the standard code, and what having them at planning time unlocks.

A standard is the top of a stack, not a single step

Read almost any standard closely and you'll notice it isn't one skill — it's a bundle. "Solve word problems involving addition and subtraction of fractions" quietly assumes a student can already find common denominators, which assumes they understand equivalent fractions, which assumes they grasp what a fraction represents at all. The standard sits at the top of that stack. Assessment happens at the top. But teaching happens all the way down.

The Learning Commons Knowledge Graph exposes the stack. Beneath each standard, it carries the smaller learning competencies that compose it — the individual, teachable pieces that add up to the standard's full demand. When Claude for Teachers plans against a standard, it isn't treating that standard as an indivisible target to be hit or missed. It can see the components, which means it can build toward the standard one competency at a time instead of throwing the whole thing at students in a single lesson and hoping.

That decomposition is quietly the difference between a lesson and a worksheet. A worksheet asks students to perform the standard. A lesson walks them up to it. You can only walk them up if you know the steps.

Progressions: the steps in order

Competencies alone aren't enough — a pile of prerequisites with no sequence is just a checklist. The second thing the graph encodes is the order: which competencies students typically learn before which others. That ordering is the learning progression, and it's what turns a set of components into a path.

Progressions are hard-won knowledge. They come from watching thousands of students learn the same material and noticing the reliable sequence — that equivalent fractions almost always has to precede common denominators, that you can't reason about theme until you can reliably summarize plot. No single teacher assembles that map from scratch; it accumulates across a profession. Encoding it into a knowledge graph and handing it to Claude at planning time means the model plans with the sequence a veteran would use, not the arbitrary order a first draft falls into.

Here's the practical shape of what the progression layer gives a lesson:

Competencies tell Claude what a standard is made of. The progression tells it the order to build in. Together they're the difference between a lesson that mentions a standard and a lesson that scaffolds students up to one.

Why progressions are what make scaffolding possible

Scaffolding is one of those words that gets nodded at and rarely defined. Concretely, to scaffold is to meet a student one rung below where the lesson aims and build a supported path up to it. You cannot do that without knowing what "one rung below" is. That's not a vibe — it's a specific prior competency, the one that sits just under the target in the progression.

This is why the progression layer is load-bearing rather than decorative. When Claude for Teachers knows the sequence, "add a scaffold" stops being a hand-wave and becomes a concrete move: insert the prerequisite competency, in the right place, before the step that depends on it. When a student is behind, "differentiate down" stops meaning "make it easier somehow" and starts meaning "drop to the specific earlier rung this student can stand on, then climb." The progression gives every one of those adjustments a real anchor.

It also makes the challenge direction principled. Extending a lesson for students who are already fluent isn't about piling on more problems — it's about reaching for the next competency up the progression. The same map that tells Claude where to scaffold down tells it where to stretch up. That's the engine underneath the differentiation skill's below/at/above tiers, and it's why those tiers keep the core content consistent instead of becoming three unrelated lessons.

Alignment stops being a retrofit

Most "standards-aligned" AI writes the lesson first and matches it to a standard afterward. That ordering is exactly backwards, and it's why so much aligned-in-name content teaches a subtly wrong grain size — right topic, wrong rung. When Claude plans from the competencies and their order, alignment isn't a check performed at the end; it's the scaffold the lesson is built on from the first line. That flip — from afterthought to construction — is important enough to have its own piece, Standards-Aligned by Construction, Not by Afterthought.

The progression is also the connective tissue for a lot of what Claude for Teachers can do beyond a single lesson. Mastery-based learning needs a sequence to move students through. Analyzing class data needs a map to place each student on. Small-group instruction needs to know which groups are stuck on which rung. All of that presumes a progression exists and is legible to the tool. The Learning Commons connector is what makes it legible.

What to do with this as a teacher

You don't have to think about competencies and progressions to benefit from them — inside Claude for Teachers they're simply present, doing their work under the hood. But knowing they're there changes how you ask. Instead of "write a lesson on adding fractions," you can lean on the layer directly: ask what competency a struggling student is probably missing, ask for the step just below the standard, ask Claude to sequence a unit along the progression rather than by textbook chapter. You're no longer prompting a text generator; you're consulting a planning partner that shares your mental model of how the subject is learned.

If you want to feel the same principle before you're verified, it's the logic behind grounded tools like the marketplace lesson-plan-studio skill: a plan is only as good as the map it's built on. The Learning Commons Knowledge Graph — reached through the connector that ships with Claude for Teachers — is that map, competencies and progression and all. It's the quiet layer beneath every standard, and it's why the lessons come out ready to scaffold.

---

Part of the Claude for Teachers series. Related: The Learning Commons Knowledge Graph Connector, Explained · Standards-Aligned by Construction, Not by Afterthought. Browse AI tutoring skills or more builder insights.