← ClaudeAtlas

retro-pattern-analyzerlisted

Analyze sprint retrospective files and surface recurring pain points, unresolved action items, and positive patterns across sprints. Use when preparing quarterly reviews or identifying systemic issues. Triggers: 'analyze retro files', 'retro pattern analysis', 'find recurring issues in retrospectives', 'проанализируй ретро', 'паттерны в ретроспективах'.
KirKruglov/claude-skills-kit · ★ 9 · AI & Automation · score 82
Install: claude install-skill KirKruglov/claude-skills-kit
# Retro Pattern Analyzer This skill analyzes retrospective files from multiple sprints and produces a structured report identifying recurring pain points, unresolved action items, and stable positive patterns. It reads `.md` and `.txt` files, normalizes different retro formats, and outputs `retro-patterns-YYYY-MM-DD.md`. **Input:** - 2 or more retrospective files in `.md` or `.txt` format - Optional: folder path or list of file paths - Optional: focus area (e.g., "technical issues only", "delivery problems") **Output:** - `retro-patterns-YYYY-MM-DD.md` — structured report with three blocks: recurring pains, unresolved action items, positive patterns --- ## Language Detection Detect the user's language from their message: - If Russian (or contains Cyrillic): respond in Russian - If English (or other Latin-script language): respond in English - If ambiguous: respond in the language of the trigger phrase used --- ## Instructions ### Step 1: Validate Input 1. Check that at least 2 files are provided - If only 1 file provided: stop. Report: "Pattern analysis requires at least 2 retrospective files. Please provide a second file or folder path." - If folder path given: list all `.md` and `.txt` files in the folder; if fewer than 2 found, stop with same message 2. Check each file is readable - If any file is unreadable or path does not exist: skip that file, report: "File [name] not found or unreadable — excluded from analysis." - Continue with remaining files