learnlisted

# learn — Phase 3.6 Mine the current session for a reusable pattern and save it as a Speculation- grade skill under `~/.claude/skills/learned-<name>-unverified/SKILL.md`. User confirmation is mandatory before the write — never silently persist. ## Trigger conditions Run `/learn` after solving a non-trivial problem where the approach is generalizable (not a one-off typo or outage-specific fix). ## What to extract | Kind | Example | |------|---------| | **Error resolution** | Root cause + fix that applies to similar errors | | **Debugging technique** | Non-obvious steps, effective tool combos | | **Workaround** | Library quirk / API limitation / version-specific fix | | **Project-specific pattern** | Codebase convention / integration pattern discovered this session | ## Workflow ### Step 1 — Review session Scan recent messages / tool outputs for extractable patterns. Prefer patterns that saved meaningful time or would have, had they been known upfront. ### Step 2 — Identify the highest-value candidate Multiple candidates? Pick one. Keep skills focused — **one pattern per file**. ### Step 3 — Draft skill body Use the **learned-skill template** below. Mark confidence as `Speculation` and append `-unverified` to the skill directory name. ### Step 4 — User confirmation Present a concise summary (pattern name, one-sentence description, trigger, proposed filename) to the user and ask to approve the save. Options: - A: "Save it" → Step 5 - B: "Edit first" → accept user r