how we work · skills hub
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 Volume 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 shape | Purpose |
|---|---|
| Read | Volume canon or Practice page |
| Worked example | A real artefact from the corpus, annotated |
| Practice prompt | Apply to your current work — bring a real story |
| Mini-check | 3–5 questions, including a negative case |
| Pair task | With a more senior role; explicit handoff |
| Retro on own work | Use the corpus's own checklists on yourself |
| Teach-back | Write a one-pager for a junior — the Feynman gate |
| Authoring contribution | PR 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.
What if my role isn't here yet?
Most non-PO paths are still being authored. The rough cut you can rely on today, building on Volumes I–V:
- Tech Lead foundations — Volume III parts 6–8 (ADRs, sequence/schema/API, ilities) → Volume IV parts 4, 8, 9 (pipeline, runbooks, observability).
- Designer foundations — Volume II part 3 (journey) → Volume III parts 1, 2, 5 (epic kickoff, story mapping, amigos) → Volume IV part 1 (domain language).
- QA foundations — Volume III part 5 (amigos) → Volume IV part 5 (testing layers) → Volume V part 3 (bug taxonomy).
- On-call competence — Volume IV part 8 (runbooks) → Volume V parts 1, 4 (first 48h, postmortems).
When the formal path lands, this list will move into Skills Hub above.