growth-log
Write growth log entries that extract reusable patterns from completed work — root cause, transferable rule, and a recognizable signal — instead of diary-style event narration, with a 4-8 sentence template and merge-duplicates discipline.
- Kind
- Skill
- Works with
- Claude Code, Codex
- Source
- affaan-m/ECC @ d3b8a3e90890
- Path
- skills/growth-log/SKILL.md
- License
- MIT
- Jobs
- Debugging, Review, Git workflow
InstallCopy it from the source repository, or sign in and let the assistant adapt it for your project.
# Growth Log Skill > **The problem:** Most people write "fixed a bug in X" as a learning log. That's a diary entry, not a learning artifact. A real growth log extracts the *pattern* so you recognize it next time. > > **This skill teaches:** How to write learning entries that compound across sessions. Works with any note-taking system — Markdown files, Notion, Obsidian, plain text. Templates are generic; adapt to your setup. ## When to Activate - After completing a complex task (multi-file, new feature, architecture change) - After a failure, mistake, or "that was harder than expected" moment - When you want to review what you've learned over a period **When NOT to activate:** Trivial changes (typo fixes, single-line tweaks, config value changes with no debugging). The threshold: *did this task involve debugging, redoing, rollback, or a non-obvious decision?* If yes → write an entry. If no → skip. ## The Three Rules ### Rule 1: Failures > Achievements A failure is nutritionally denser than a success. One bug that took 2 hours to find teaches more than 3 features that worked first try. **Bad:** "Successfully implemented the login flow." …