learning-hours/learning-hour-maker
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Update skill and README with real timetable data from 124 learning hours

Browse Source 
- Skill now reflects actual patterns: single 35-min practice (65%),
  two rounds (23%), with demo (28%)
- Average times per block type from library analysis
- Output format matches Samman Markdown convention
- README updated with statistics
This commit is contained in:
mostalive
2026-09-02 15:28:38 +01:00
parent d92c8a79d3
commit d8eaf03a68
2 changed files with 104 additions and 47 deletions
Download Patch File Download Diff File Expand all files Collapse all files
.pi/skills/learning-hour-design/SKILL.md
+89 -39
View File
@@ -39,22 +39,54 @@ Start by helping Willem identify 1–3 clear learning goals. For each goal:
### Phase 2: Timetable
Between the learning goals and the 4 C's, design a timing plan. The default structure is two rounds of 15-minute pair practice, preceded by Connect and Concepts (sometimes split, sometimes all Concepts after the first practice).
Between the learning goals and the 4 C's, design a timing plan. Analyze of 124 Samman learning hours shows these patterns.
#### Average times per block type (from the library)
| Block | Average | Range |
|-------|---------|-------|
| Connect | **6.6 min** | 2–15 min |
| Concept | **9.2 min** | 2–25 min |
| Concrete/Do | **25.3 min** | 5–45 min (per block) |
| Conclusion/Reflect | **6.2 min** | 2–15 min |
| Demo (optional) | **10.6 min** | 2–45 min |
#### Most common structure: 4 blocks (65% of hours)
| Block | Time | Description |
|-------|------|-------------|
| Connect | 5-10 min | Hook attention, connect to prior knowledge |
| Concepts (Round 1) | 5-10 min | Introduce key ideas before first practice |
| Concrete Practice 1 | 15 min | Participants practice in pairs |
| Concepts (Round 2) | 5 min | Additional concepts or deepening after practice |
| Concrete Practice 2 | 15 min | Second pair practice round |
| Conclusions | 5-10 min | Wrap-up, key takeaways |
| Concept | 10-15 min | Introduce key ideas |
| Concrete Practice | 30-35 min | Single extended practice block |
| Conclusion | 5-10 min | Wrap-up, key takeaways |
#### Two-practice-round structure (23% of hours)
| Block | Time | Description |
|-------|------|-------------|
| Connect | 5-10 min | Hook attention, connect to prior knowledge |
| Concept | 5-10 min | Introduce key ideas before first practice |
| Concrete Practice 1 | 15-20 min | First practice round |
| Concept (deepening) | 5-10 min | Additional concepts after practice |
| Concrete Practice 2 | 15-20 min | Second practice round |
| Conclusion | 5-10 min | Wrap-up, key takeaways |
#### With a demo block (28% of hours)
| Block | Time | Description |
|-------|------|-------------|
| Connect | 5-10 min | Hook attention, connect to prior knowledge |
| Concept | 5-10 min | Introduce key ideas |
| Demo | 10-15 min | Demonstrate the technique |
| Concrete Practice | 25-30 min | Participants practice |
| Conclusion | 5-10 min | Wrap-up, key takeaways |
**Rules for the timetable:**
- Total must fit in 60 minutes — be strict about this.
- Two 15-minute pair practice rounds are the default. Adjust only with justification.
- Connect always comes first. Concepts can be split before/after practice, or front-loaded entirely before Practice 1.
- Always leave room for Conclusions at the end.
- Total is usually 50-55 min of explicit blocks, leaving 5-10 min buffer for transitions.
- **Single 35-min practice is more common** than two 15-min rounds — ask Willem which fits.
- Connect is almost always first (99%). Conclusion is always last (99%).
- Concept can come after practice (21% of hours) — used for deepening or explaining what they just experienced.
- Demo is a distinct block from concept when present.
- If Willem has more concepts than fit, help cut scope — 60 minutes is tight.
Present the timetable and ask Willem if it feels right before moving on.
@@ -76,10 +108,11 @@ Work through each C. For each one, ask questions and co-create content.
What are the key ideas, frameworks, or principles?
- List 2–4 concepts maximum. More than that won't fit.
- List 2–4 concepts maximum. More than that won't fit in ~9 min average.
- For each concept: what's the simplest way to explain it?
- What visual, diagram, or example makes it click?
- Which concepts go before Practice 1 vs Practice 2?
- Consider: do some concepts go before practice and some after? (21% of hours interleave concept after practice)
- Reference the Samman Concept page for activity ideas: https://sammancoaching.org/activities/concept.html
#### C3: Concrete Practice
@@ -88,7 +121,7 @@ This is where participants actively apply the new concept. Usually a coding exer
- Willem often has a practice idea that's too big. **Actively help descope:**
- "What's the minimum viable version of this exercise?"
- "What can you cut and still hit the learning goal?"
- "Can this be done in pairs in 15 minutes?"
- "Can this be done in pairs in 15-35 minutes?"
- "What tools do they need? Keep it simple — a screenshot on paper works, don't need editors."
- Structure each practice round:
- Clear instructions (what to do, with whom, for how long)
@@ -111,50 +144,67 @@ How do participants consolidate what they learned? Conclusions help learners sum
Once all phases are done:
1. Present the complete learning hour as an org-mode outline.
1. Present the complete learning hour as a Markdown file matching the Samman format.
2. Verify: does every C map back to a learning goal?
3. Check the math: does the timetable add to 60 minutes?
3. Check the math: does the timetable add to ~55 min (leaving buffer)?
4. Flag any gaps or scope creep.
## Output Format
When producing the final learning hour, use this org-mode structure:
When producing the final learning hour, use this Markdown structure matching the Samman convention:
```org
#+title: [Learning Hour Title]
```markdown
---
theme: [topic]
title: [Learning Hour Title]
name: [slug-name]
kata: [kata-name if applicable]
difficulty: [1-5]
author: [author]
affiliation: [affiliation]
tags: [tag1 tag2]
---
* Learning Goals
- [Goal 1 – observable outcome]
- [Goal 2 – if applicable]
# [Learning Hour Title]
* Timetable
| Block | Time | Notes |
|-------+------+-------|
| ... | ... | ... |
[Opening paragraph: why this matters, what problem it solves]
* Connect
[Content]
## Learning Goals
* Concepts
** Concept 1
[Content]
** Concept 2
[Content]
* [Goal 1 – observable outcome]
* [Goal 2 – if applicable]
* Concrete Practice
** Round 1 (15 min)
[Instructions, task, debrief]
** Round 2 (15 min)
[Instructions, task, debrief]
## Session Outline
* [X] min connect: [brief description]
* [X] min concept: [brief description]
* [X] min concrete: [brief description]
* [X] min conclusion: [brief description]
## Connect - [Connect Activity Name]
[Content, instructions, examples]
## Concept - [Concept Name]
[Content, explanations, examples]
## Concrete Practice - [Practice Name]
[Instructions, task, tools, debrief]
## Conclusions - [Conclusion Activity Name]
* Conclusions
[Wrap-up, takeaways, next steps]
```
## Tips
- Always push back on scope creep — 60 minutes is tight.
- Always push back on scope creep — 60 minutes is tight; explicit blocks usually total 50-55 min.
- If Willem has multiple learning goals, suggest splitting into separate hours.
- Pair practice is the default format; suggest alternatives only if justified.
- A single 35-min practice block is the most common pattern — two rounds is less common but valid.
- Demo is a distinct block from concept; suggest it when the technique benefits from seeing it first.
- When in doubt, reference the Samman example: https://sammancoaching.org/learning_hours/testable_design/naming.html
- Browse the full library for inspiration: https://sammancoaching.org/learning_hours/
- Check `website/_learning_hours/` in this repo for local copies of all learning hours.