Files
our-claude-skills/official-skils-collection/notion-knowledge-capture/reference/learning-database.md
Andrew Yim 341d5f5a5b Initial commit: Claude Skills Factory with 8 refined custom skills
Custom Skills (ourdigital-custom-skills/):
- 00-ourdigital-visual-storytelling: Blog featured image prompt generator
- 01-ourdigital-research-publisher: Research-to-publication workflow
- 02-notion-organizer: Notion workspace management
- 03-research-to-presentation: Notion research to PPT/Figma
- 04-seo-gateway-strategist: SEO gateway page strategy planning
- 05-gateway-page-content-builder: Gateway page content generation
- 20-jamie-brand-editor: Jamie Clinic branded content GENERATION
- 21-jamie-brand-guardian: Jamie Clinic content REVIEW & evaluation

Refinements applied:
- All skills converted to SKILL.md format with YAML frontmatter
- Added version fields to all skills
- Flattened nested folder structures
- Removed packaging artifacts (.zip, .skill files)
- Reorganized file structures (scripts/, references/, etc.)
- Differentiated Jamie skills with clear roles

🤖 Generated with [Claude Code](https://claude.ai/code)

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
2025-12-10 17:56:04 +09:00

1.3 KiB

Learning/Post-Mortem Database

Purpose: Capture learnings from incidents, projects, or experiences.

Schema

Property Type Options Purpose
Title title - Event or project name
Date date - When it happened
Type select Incident, Project, Experiment, Retrospective Learning type
Severity select Critical, Major, Minor Impact level (for incidents)
Team people - Who was involved
Key Learnings number - Count of learnings
Action Items relation Links to tasks Follow-up actions

Content Template

Each learning page should include:

  • What Happened: Situation description
  • What Went Well: Success factors
  • What Didn't Go Well: Problems encountered
  • Root Causes: Why things happened
  • Learnings: Key takeaways
  • Action Items: Improvements to implement

Best Practices

  1. Blameless approach: Focus on systems and processes, not individuals
  2. Document quickly: Capture while memory is fresh
  3. Identify root causes: Go beyond surface-level problems
  4. Create action items: Turn learnings into improvements
  5. Follow up: Track that action items are completed
  6. Share widely: Make learnings accessible to entire team