Investigate Capa Root Cause
Investigate root causes and manage CAPAs (Corrective and Preventive Actions) for compliance deviations. Covers investigation method selection (5-Why, fishbone, fault tree), structured root cause analysis, corrective vs preventive action design, effectiveness verification, and trend analysis. Use when an audit finding requires a CAPA, when a deviation or incident occurs in a validated system, when a regulatory observation needs a formal response, when a data integrity anomaly requires investigation, or when recurring issues suggest a systemic root cause.
Install
npx skills add pjt222/agent-almanac --skill investigate-capa-root-causegit clone --depth 1 https://github.com/pjt222/agent-almanac.git /tmp/agent-almanac
mkdir -p ~/.claude/skills
cp -r /tmp/agent-almanac/i18n/caveman-lite/skills/investigate-capa-root-cause ~/.claude/skills/investigate-capa-root-causePersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Investigate CAPA Root Cause Conduct a structured root cause investigation and develop effective corrective and preventive actions for compliance deviations. ## When to Use - An audit finding requires a CAPA - A deviation or incident occurred in a validated system - A regulatory inspection observation needs a formal response - A data integrity anomaly requires investigation - Recurring issues suggest a systemic root cause ## Inputs - **Required**: Description of the deviation, finding, or incident - **Required**: Severity classification (critical, major, minor) - **Required**: Evidence collected during the audit or investigation - **Optional**: Previous related CAPAs or investigations - **Optional**: Relevant SOPs, validation documents, and system logs - **Optional**: Interview notes from involved personnel ## Procedure ### Step 1: Initiate the Investigation
Details
- Skill name
investigate-capa-root-cause- Repository
- pjt222/agent-almanac
- Path
i18n/caveman-lite/skills/investigate-capa-root-cause/SKILL.md- License
- MIT
- Repo updated
- 18 November 2026
- Listed in
- BehiSecc/awesome-claude-skills
FAQ
What does the Investigate Capa Root Cause skill do?
Investigate root causes and manage CAPAs (Corrective and Preventive Actions) for compliance deviations. Covers investigation method selection (5-Why, fishbone, fault tree), structured root cause analysis, corrective vs preventive action design, effectiveness verification, and trend analysis. Use when an audit finding requires a CAPA, when a deviation or incident occurs in a validated system, when a regulatory observation needs a formal response, when a data integrity anomaly requires investigation, or when recurring issues suggest a systemic root cause.
How do I install the Investigate Capa Root Cause skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add pjt222/agent-almanac --skill investigate-capa-root-cause. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Investigate Capa Root Cause popular?
It lives in pjt222/agent-almanac, which has 45 GitHub stars and 4 forks, and is included in 1 curated skill list.
Related skills
Adapt Architecture
45pjt222/agent-almanac
Execute structural metamorphosis using strangler fig migration, chrysalis phases, and interface preservation. Covers transformation planning, parallel running, progressive cutover, rollback design, and post-metamorphosis stabilization for system architecture evolution. Use when assess-form has classified the system as READY for transformation, when migrating from monolith to microservices, when replacing a core subsystem while dependents continue operating, or when any architectural change must be gradual rather than big-bang.
Adaptic
45pjt222/agent-almanac
Master skill composing the 5-step synoptic cycle for panoramic synthesis across multiple domains. Orchestrates meditate, expand-awareness, observe, awareness, integrate-gestalt, and express-insight into a coherent process that produces unified understanding rather than sequential compromise. Use when a problem genuinely spans 3+ domains and the interactions between domains matter more than depth in any one, when sequential analysis feels like compromise rather than integration, or before major architectural decisions affecting multiple stakeholders.
Add Puzzle Type
45pjt222/agent-almanac
Scaffold a new puzzle type across all 10+ pipeline integration points in jigsawR. Creates the core puzzle module, wires it into the unified pipeline (generation, positioning, rendering, adjacency), adds ggpuzzle geom/stat layers, updates DESCRIPTION and config.yml, extends the Shiny app, and creates a comprehensive test suite. Use when adding a completely new puzzle type to the package or following the 10-point integration checklist to ensure nothing is missed end-to-end.
Investigation Add
43AlsKozlov/ru-legal
Add fact / interview / document / decision к existing investigation. Routes по типу: fact → facts.md timeline, interview → interviews/[name].md, evidence → evidence/ + log, decision → status.md.
Internal Investigation
43AlsKozlov/ru-legal
Backend framework для investigation suite — defines workspace structure, privilege protocols (РФ-specific!), interview templates, evidence chain of custody, дисциплинарные timing rules (ст.192-193 ТК). Sub-skill: вызывается из /investigation-open, -add, -query, -memo, -summary. Не user-invocable.
Investigation Memo
43AlsKozlov/ru-legal
Draft legal memo по результатам внутреннего расследования. РФ specifics: privilege ТОЛЬКО через outside-адв ФПА; дисциплинарка по ст.193 ТК (объяснение, сроки); стандарт доказывания "balance of probabilities" для внутренних целей, но "обоснованность" для оспаривания в суде. Recommended action: какое взыскание / какой алгоритм для оформления.
Browse the most popular Claude skills, all finance & crypto skills, or write your own with the skills generator.