Pending: Hook-based vs memory-based vs hybrid approach?
Pending: How prominent should the learning nudge be? (inline note vs separate section)
User Tasks
Summary
Automatically surface relevant learning topics from vault/20_knowledge/personal/learning-topics.md when the user works on something related — so they learn by doing instead of studying separately.
Problem / Motivation
The user has a list of topics to learn (agentic programming concepts). These topics are only useful when they come up naturally during work — not as a study list. Without a surfacing mechanism, they sit in a file and get forgotten. The inbox should stay clean (not hold learning items), and topics should be completable (check off and remove).
Proposed Solution
A hybrid approach:
Memory (immediate) — Claude remembers the topics and explains relevant concepts when they come up in conversation. Already active.
Hook/rule (future) — a trigger that detects when work touches a learning topic and adds a brief explanation to the output. E.g., when creating a sub-agent, explain how agent specialization works.
Open Questions
1. Surfacing mechanism
Question: How should topics be surfaced?
Option
Description
A) Memory only
Claude remembers and explains when relevant — no automation
B) Memory + hook
Memory for now, add a hook later that checks the topic list
C) Briefing integration
Daily briefing includes “today’s learning opportunity”
Recommendation: Option B — memory works today, hook adds reliability later.
2. Nudge format
Question: How prominent should learning nudges be?
Option
Description
A) Inline
Brief note within the normal response (“btw, this is related to your learning topic X — here’s what’s happening…“)
B) Separate section
A boxed “Learning Note” section at the end of responses
C) Only on request
User asks /learn to get the explanation
Recommendation: Option A — least disruptive, most natural.
Phase Overview
Phase
Description
Status
Phase 1
Memory-based surfacing (manual)
in-progress
Phase 2
Hook that cross-references topic list with current work
—
Phase 3
Auto-check-off topics after sufficient exposure
—
Phase 1: Memory-Based Surfacing in-progress
Goal: Claude knows the learning topics and explains concepts when they come up.
File / Feature
Details
Owner
Status
vault/20_knowledge/personal/learning-topics.md
Topic checklist
opus
done
Claude memory entry
Memory linking topics to triggers
opus
done
Remove vault/90_inbox/learning-goals.md
Clean inbox
opus
done
Phase 2: Hook-Based Trigger —
Goal: A hook or rule that detects relevant work and reminds Claude to teach.
File / Feature
Details
Owner
Status
Trigger rules mapping
Which actions/files map to which topics
opus
—
Hook script or rule
Automatic detection
opus
—
Test
Manual tests
Test
Expected
Actual
Last
…
…
pending
-
AI-verified tests
Scenario
Expected behavior
Verification method
…
…
…
E2E tests
Scenario
Assertion
…
…
Integration tests
Component
Coverage
…
…
Unit tests
Component
Tests
Coverage
…
…
…
History
Date
Event
Details
2026-03-12
Created
Split from learning-goals.md, which moved to knowledge
References
FR-064 (Personal Learning Feed) — delivers learning content via messaging; this FR surfaces topics during work sessions