Stats
Actions
Tags
From brag-doc
Writes or updates the "Failures / Lessons Learned" section of a brag doc entry. Invoke when you have evidence of things that went wrong, root causes, and what changed as a result.
How this skill is triggered — by the user, by Claude, or both
Slash command
/brag-doc:write-failures-lessons-learnedThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
This section is optional — omit entirely if no evidence exists.
This section is optional — omit entirely if no evidence exists.
A curated set of well-formed failure/lesson entries. Each should cover:
Frame as ownership + improvement, not blame or excuse.
Bullet list, ≤6 items. Each bullet: 2–3 sentences covering what happened → why → what improved. These should be interview-ready: concise enough to tell in 60 seconds.
Return only:
## Failures / Lessons Learned
- <bullet>
npx claudepluginhub lou-k/claude-plugins --plugin brag-docCaptures structured lessons learned entries for organizational memory after incidents, completed projects, or significant learnings to preserve knowledge for future teams.
Captures structured postmortems from dev sessions into project-scoped lessons files that future planning runs can read to avoid repeating mistakes.
Transforms accomplishment descriptions into structured brag document entries with categorization, achievement bullets, quantified impacts, and skills demonstrated. Useful for promotion prep and performance reviews.