diff --git a/org-cyf-guides/content/contributing/minutes/index.md b/org-cyf-guides/content/contributing/minutes/index.md
index 237121e52..703f78e1c 100644
--- a/org-cyf-guides/content/contributing/minutes/index.md
+++ b/org-cyf-guides/content/contributing/minutes/index.md
@@ -17,6 +17,46 @@ Attendees:
 
 ---
 
+## 2026-01-13
+
+Attendees: Ali Smith, Anna Aitchison, CJ Yuan, Daniel Wagner-Hall
+
+### ❗Actions from last time
+
+- [ ] Daniel (Carry-over): Look at tic-tac-toe workshop explaining the breaking down of the problem
+- [ ] CJ (Carry-over): Update testing content in ITP
+- [x] Colin (Carry-over): Add PR formatting to ITP onboarding
+- [ ] CJ: Clean up (and split up) the "How ITD works" section.
+- [x] Daniel: Add "respond to a bot comment" to the developer specs workshop
+
+### 📝 Agenda points
+
+#### Testing content in ITP
+
+**Why are we introducing `console.assert`?** Avoiding having to pull in dependencies, and all of imports/packages/projects/...
+
+**Should we be focusing on what values to test or how to test or both?** A lot of the testing content is "copy and paste examples with more values". Long-term we want trainees to do both, but we don't necessarily have to do both at the same time.
+
+**Some tests talk about TDD but don't really do it?** We should probably remove the term TDD, but try to get people thinking about test cases before writing code (even if not actually writing them). If we want to introduce TDD, we should probably do so explicitly (and better)!
+
+#### Required demo-giving for people without laptops
+
+We now require giving a demo for each Step in ITP. But we won't lend people laptops until they've submitted Step 1. How should we handle bootstrapping this?
+
+Change the requirement to _attend_ a demo session for Step 1, and _presenting_ a demo session for the subsequent steps. But keep recommending presenting demos as early as possible.
+
+#### Moving Tuesday meetings to 7pm to avoid conflict with demo session
+
+Let's do it. Also, let's only do Tuesdays, they work better for everyone and it will be more predictable.
+
+### ❗Actions
+
+- [ ] Daniel (Carry-over): Look at tic-tac-toe workshop explaining the breaking down of the problem
+- [ ] CJ (Carry-over): Update testing content in ITP
+- [ ] CJ (Carry-over): Clean up (and split up) the "How ITD works" section.
+
+---
+
 ## 2025-12-16
 
 Attendees: CJ Yuan, Colin Farquhar, Daniel Wagner-Hall, Karen Klein, Léon McGregor