skills/lessons-learned/SKILL.md
Use when extracting learnings, saving lessons, or capturing reusable knowledge from the session. Also appropriate before presenting a plan, after notable events (bugs, wrong approaches corrected), and as final task when work is complete.
npx skillsauth add lklimek/claudius lessons-learnedInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Extract, qualify, and persist reusable knowledge from the current session.
!cat ${CLAUDE_SKILL_DIR}/../../references/source-of-truth.md
Scan the conversation for items worth remembering. Use the categories, quality gate, and examples from the Source of Truth above.
Collect as a numbered list. Search existing knowledge (memcan:recall) and drop duplicates.
Tone: factual, third-person, present tense. Pattern: "[Subject]: [what/what to do] — [why/context]"
During dedup searches, if existing memories fail the quality gate, update or delete them.
For each qualified item:
project) or project-scoped (set project to git remote origin repo name)memcan:remember skill to persist each itemLog each save: scope, type, one-line summary. Report total count.
IMPORTANT: This skill does NOT call memcan MCP tools directly. It invokes memcan:remember for saves and memcan:recall for searches. Claudius owns the classification logic; memcan is the execution layer.
testing
Coordinator-only LLM validation pass. Adds ai_assessment / ai_verdict / ai_verdict_confidence and, in the rare partial-producer case, re-estimates absent risk/impact/scope on a consolidated v3 report.
testing
Use for typos or single-line fixes (≤20 lines). Same mandatory phase order (Planning→Impl→QA→LL), minimal ceremony. Auto-retry on failure.
testing
Use for bug fixes or small changes (≤200 lines). Same phase order as workflow-feature (Planning→Impl→QA→LL) with lighter ceremony. Auto-retry on failure, unattended.
development
Use for new projects, features, or major refactoring. Phases: Planning (Req→UX→Test Spec→Dev Plan) → Implementation → QA → Lessons Learned. Auto-retry on failure, unattended.