learner

name	learner
type	workflow
description	Turns real agent failures, repeated prompts, team-specific workflows, and durable project lessons into better SDD skills or memory entries. Use when the user asks to create/update/refine skills, extract reusable lessons, improve skill routing, encode team process, or save patterns for future sessions.
argument-hint	[session summary, failure mode, repeated prompt, or skill improvement request]
allowed-tools	Read, Glob, Grep, Write, Edit, Bash
user-invocable	true
effort	3
when_to_use	Use when a lesson should become durable: after repeated corrections, wrong skill routing, repeated long prompts, team-specific process discovery, or a complex session worth converting into a skill or memory entry.

Learner

Convert real SDD usage into durable operating knowledge.

Use this workflow to decide whether a lesson belongs in:

• an existing skill,
• a new skill,
• .claude/memory/annotations.md,
• another Tier 2 memory file,
• or no durable artifact.

Source Principles

This workflow adopts the Agent Skills guidance that durable skills come from real expertise, project artifacts, execution traces, and repeated refinement. Skills should capture team-specific process and failure modes, not generic best practices or deterministic glue better handled by scripts, hooks, or MCP.

Extraction Gate

Create or modify a skill only when at least one signal is present:

• Agent made a wrong choice despite a correct prompt.
• Existing skill fired but failed its mission.
• Needed skill did not fire because description was weak or absent.
• A teammate/user wrote the same long prompt, plan, or checklist a second time.
• Session repeated a costly investigation, setup, verification, or handoff loop.
• User corrected a project convention, team preference, or non-obvious edge case.
• Internal process, internal system, or proprietary data pattern must be reused.

Do not create a skill for:

• General advice the model already knows.
• One-off code snippets.
• Secrets, credentials, or environment-specific auth hacks.
• Simple deterministic checks better implemented as hooks, scripts, tests, or MCP.
• Large copied docs without a clear load condition.

Decision

Classify the lesson before editing:

Lesson type	Target
Existing workflow missed a rule, edge case, or output shape	Update that skill body
Existing skill should have fired but did not	Tighten that skill description
Repeated team-specific process forms a coherent unit	Create or update a skill
Non-obvious caveat tied to a service/library/repo area	Use annotate memory
Broad preference or project operating rule	Update the right Tier 2 memory/doc
Deterministic repeated operation	Prefer tested script/hook/MCP; skill only orchestrates when needed