Learning Mode

Decisions

• Pending: Should lessons auto-suggest the next topic? (learning path)
• Pending: Integrate mini-lessons into daily briefings?
• Pending: Should there be a /learn-series that generates 5-10 lessons at once?

User Tasks

---

Summary

A /learn skill that generates bite-sized lessons about the Opus system, Claude Code, and software development — readable on phone via Obsidian.

Problem / Motivation

The user wants to deeply understand how Claude Code works, what’s in the Opus repo/vault, and the software development concepts behind it. Currently there’s no structured way to learn this — only scattered docs and learning-goals.md. The user wants to learn at their own pace, including on their phone via Obsidian mobile.

Proposed Solution

Build a /learn skill that generates focused, phone-friendly lessons and saves them to vault/20_knowledge/. The skill reads real files from the repo to base lessons on actual content (no hallucination). Topics range from “how do skills work?” to “what is a worktree?” to “explain the feature lifecycle”.

How it works:

1. User runs /learn <topic> (e.g., /learn skills, /learn vault structure, /learn worktrees)
2. Skill reads relevant files from the repo/vault as source material
3. Generates a concise, structured lesson (phone-screen friendly)
4. Saves to vault/20_knowledge/<subcategory>/lesson-<topic>.md
5. Updates a lesson index so user can track what they’ve covered

Lesson format:

• Title + one-line summary
• “What is it?” — plain explanation
• “How does it work in Opus?” — concrete examples from the actual repo
• “Key files” — paths to explore further
• “Try it” — a small exercise or thing to look at
• Max ~200 lines — readable in one phone session

Topic categories:

• System: How Claude Code works, skills, hooks, agents, settings, MCP, rules
• Vault: Vault structure, feature lifecycle, templates, conventions
• Dev concepts: Worktrees, git workflows, spec-driven development, scaffolding
• Code: Python modules in src/, architecture, patterns (as codebase grows)

---

Open Questions

⇒

• Should lessons auto-suggest the next topic? (like a learning path)
• Integrate mini-lessons into daily briefings later? (combine with FR-003)
• Should there be a /learn-series <topic> that generates 5-10 lessons at once?

---

Phase Overview

Phase	Description	Status
Phase 1	Basic /learn skill	—
Phase 2	Learning paths + daily integration	—

---

Phase 1: Basic /learn Skill —

Goal: Create a working /learn skill that generates lessons from real repo content.

File / Feature	Details	Owner	Status
SKILL.md	Define /learn skill with topic routing	opus	—
Topic: system	Lessons about Claude Code internals (skills, hooks, agents, rules, settings)	opus	—
Topic: vault	Lessons about vault structure, feature lifecycle, conventions	opus	—
Lesson index	Create vault/20_knowledge/lesson-index.md to track covered topics	opus	—
Link to learning-goals.md	Cross-reference with existing learning goals	opus	—

---

Phase 2: Learning Paths + Daily Integration —

Goal: Add structured learning paths and integrate lessons into daily workflow.

File / Feature	Details	Owner	Status
Learning paths	Ordered sequences of lessons per category	opus	—
Daily briefing integration	Add “Today’s Lesson” section to /briefing	opus	—
/learn-series	Generate a full series of lessons for a topic area	opus	—
Dev concepts	Add lessons about software development patterns	opus	—

---

Prerequisites / Gap Analysis

Requirements

Requirement	Description
REQ-1	/learn <topic> generates a lesson and saves it to vault
REQ-2	Lessons are based on real file contents (Read before writing)
REQ-3	Lessons are concise and phone-readable (~200 lines max)
REQ-4	Lesson index tracks what’s been covered
REQ-5	At least 5 system/vault topics work out of the box

Current State

Component	Status	Details
Learning goals	done	vault/90_inbox/learning-goals.md exists
Knowledge base	WIP	vault/20_knowledge/ has limited content
Phone access	—	FR-022 for mobile reading via Obsidian

Gap (What’s missing?)

Gap	Effort	Blocker?
/learn skill definition	Med	No
Lesson template	Low	No
Topic routing logic	Med	No

---

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-02-26	Created	Initial feature request
2026-02-27	Renumbered	From FR-003 to FR-062
2026-02-28	Rewritten	Aligned to feature-request template

---

References

• FR-022 (Phone Access) — for mobile reading via Obsidian
• vault/90_inbox/learning-goals.md — source of topic ideas
• vault/20_knowledge/ — target directory for generated lessons