Skip to content

Skills

Scaffolded curricula, anchored to your real work. Each path reads → practices → checks → reflects, with a real artefact at every step. The path is doing its job when your work this month is better than last month.

Skills are not reading lists. They are the corpus's pedagogy — read a phase part, hold a session, write an artefact, run a check, retro on your own output, teach back to a junior. Pick a path that matches your role and level. Bring a real story from your sprint.

How a path works

Step shapePurpose
ReadCycle canon or Practice page
Worked exampleA real artefact from the corpus, annotated
Practice promptApply to your current work — bring a real story
Mini-check3–5 questions, including a negative case
Pair taskWith a more senior role; explicit handoff
Retro on own workUse the corpus's own checklists on yourself
Teach-backWrite a one-pager for a junior — the Feynman gate
Authoring contributionPR a refinement to the corpus

Each step belongs to one of these shapes. A path that doesn't reach retro on own work and teach-back by the end has not finished — these are the two steps that compound.

Levels

LevelDurationWhat it produces
Foundational6 weeks (12 for leadership)One full cycle's artefacts: brief, check, model update
Practitioner (coming)1 quarterTwo or three cycles, mentoring, cross-role craft
Advanced (coming)2+ quartersStudio-level contribution to the role's craft

Looking for your role hub?

The Teams section has each role's stance, first-30-days track, and anti-symptom catalogue. Pair it with the foundations path above.

200apps · How We Work · NWIRE