// Use when the user wants to find what to learn next, explore learning topics, get project ideas for a skill gap, or add a learning idea to their backlog. Triggers on: "what should I learn", "suggest learning projects", "I want to learn X", "add to my learning backlog", or "find me resources on X".
Use when the user is done learning for the day, wants to save progress, or wants to wrap up a lesson. Also triggered by /learn when postponing or abandoning. Updates the learning intelligence layer (insights.md) after each session. Triggers on: "end session", "done learning", "save progress", "wrap up", "end-learn", "I'm done for today".
Use when the user wants to sit down and learn, continue a lesson, practice a skill, or work through a learning project. Triggers on: "let's learn", "continue my lesson", "start learning", "practice", "I have time to learn", or "pick up where I left off".
Internal-only skill — never called directly by users. Provides the Learning Intelligence Layer. Two modes: "build context" (called by /learn at session start) reads learning history and produces a learner context; "update insights" (called by /end-learn after session close) updates the persistent insights.md summary.
Use when the user wants to review what they've learned, see progress on their gaps, get a summary of recent learning sessions, or wants article ideas based on learnings. Triggers on: "learning report", "what have I learned", "progress report", "summarize my learning", or "learning summary for the last month".
Use when the user wants a fast status check on their learning without a full report. Triggers on: "learning status", "where am I", "what's my learning state", "how's my learning going", or "check my progress".
Use at the end of a Claude Code session to capture project-specific friction as proposed CLAUDE.md edits. Triggered by /debrief (no args) to scan the full session, or /debrief <hint> to focus on a specific area (e.g., /debrief the API naming convention thing). Returning "session looks clean" with no proposals is a first-class outcome, not a fallback. Triggers on: "/debrief", "debrief the session", "wrap up this session", "what did we learn", "any rules to capture", "should we update CLAUDE.md".
| name | new-learning |
| description | Use when the user wants to find what to learn next, explore learning topics, get project ideas for a skill gap, or add a learning idea to their backlog. Triggers on: "what should I learn", "suggest learning projects", "I want to learn X", "add to my learning backlog", or "find me resources on X". |
| license | MIT |
| version | 0.1.0 |
| metadata | {"author":"david","tags":"learning, backlog, ideas, projects, resources, gaps, suggestions"} |
Generate learning ideas based on the learner's profile and add selected ones to
~/.claude/learning/backlog.md. Ideas can be hands-on projects (structured by
milestones) or reading/article recommendations.
Profile must exist at ~/.claude/learning/profile.md. If not, tell the user:
"No learning profile found. Run /init-learning first to set up your profile."
Read context:
~/.claude/learning/profile.md — gaps, goals, session_length~/.claude/learning/lessons/archive/ — scan "Still Fuzzy On" sections and abandoned lesson topics~/.claude/learning/backlog.md — avoid duplicating existing items~/.claude/learning/insights.md — if it exists, read recurring struggles and confirmed strengths to inform suggestionsDetermine source of ideas:
/new-learning "WebSockets"): focus on that topicSearch for current resources:
Propose 3-5 ideas using this format for each:
### 1. [Title]
**Gap:** [which gap from profile] | **Effort:** [N] sessions | **Style:** hands-on / reading
[1-2 sentence description of what you'll build or learn]
**Milestones** (if hands-on):
1. [First milestone — simplest, get something working]
2. [Build on it]
3. [Polish or advanced feature]
Example:
### 1. Build a REST API with Express + PostgreSQL
**Gap:** backend | **Effort:** 3 sessions | **Style:** hands-on
Build a task management API from scratch — routes, validation, database, and tests.
**Milestones:**
1. Scaffold Express app, define routes, return mock data
2. Connect PostgreSQL, implement CRUD operations
3. Add input validation, error handling, and integration tests
User picks — present as a numbered list. Ask: "Which ones should I add to your backlog? (e.g., 1, 3)"
Write to backlog.md:
## Backlog header)- [ ] <title> — **gap:** <gap> — **effort:** <N sessions> — **style:** <hands-on | reading>status: abandoned)session_length from profile/learn as resumable