skills.rest
MilanKra13
MilanKra13COMMUNITY
Explore all skills by this author →
GitHub

meta-problem-analyzer_lc_v1

Analyze developer notes to identify root causes and map them to Claude Code features.

Updated Aug 23, 2026
Search Tags:#mindset#notes#claude-code#analyze#root-cause#problem-analysis
One-click install
npx skills add https://github.com/MilanKra13/python-enterprise-template --skill meta-problem-analyzer-lc-v1
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: meta-problem-analyzer_lc_v1
Source: https://github.com/MilanKra13/python-enterprise-template/tree/main/%7B%7Bcookiecutter.project_slug%7D%7D/.claude/skills/meta-problem-analyzer_lc_v1
Command: npx skills add https://github.com/MilanKra13/python-enterprise-template --skill meta-problem-analyzer-lc-v1

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Analyzes developer notes to identify root causes and map them to Claude Code features for automated resolutions and improved workflows.

Core Features & Use Cases

  • 5-Phase Problem Analysis pipeline: parse notes, extract symptoms and emotions, map to root causes, assign Claude Code features, and log results.
  • Emotion and pattern detection to surface recurring issues and blockers in developer notes.
  • Two-level analysis (executive and meta) to reveal underlying systemic problems across teams.
  • Generates actionable Claude Code features and integration hooks to expedite remediation.
  • Produces structured artifacts including the meta-problem, groups, mindset profiling, and recommendations.

Quick Start

Run analyze_problem.py with your notes file to generate a meta-problem report.

Frequently Asked Questions about meta-problem-analyzer_lc_v1

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I analyze developer notes to find root causes in my workflow?▼

To analyze developer notes for root causes, process your files through a 5-phase pipeline that parses notes, extracts symptoms and emotions, maps them to root causes, and assigns Claude Code features for remediation.

What is meta-problem analysis and how does it work with Claude Code?▼

Meta-problem analysis processes developer notes to detect recurring frustrations and patterns, mapping them to Claude Code features and generating structured artifacts like mindset profiles and recommended hooks.

Can I use developer notes from team retrospectives to detect systemic workflow blockers?▼

Yes, you can use notes from team retrospectives and post-mortems. The analysis performs two-level executive and meta evaluations to reveal underlying systemic problems across teams.

How do I extract recurring frustrations from post-mortem notes automatically?▼

You can extract recurring frustrations by running the analysis script with your notes file, which detects emotions and patterns to surface blockers and generates a meta-problem report.

What's the best way to map identified root causes to actionable development features?▼

The best way to map root causes to actionable features is using a 25 mindset criteria evaluation, which outputs structured recommendations and integration hooks to expedite remediation.

Related Skills

Explore More Software Engineering Skills→
AlterLab-IEUAlterLab-IEU
23

game-postmortem

Generate structured post-mortem reports from git history, milestones, and retrospective notes.

Community
Advanced
HakAlHakAl
5

codebase-cleanup

Analyze codebases to identify cleanup opportunities and generate prioritized remediation reports.

Community
Advanced
CANTAGESTUDIOCANTAGESTUDIO
3

hook-development

Create event-driven Claude Code hooks for automated tool calls and notifications.

Community
Advanced
hilaryosbornehilaryosborne

em-problem-solving

Guide engineering managers through root cause analysis and action planning.

Community
Intermediate