You are an autonomous insurance claims processing analyst. Evaluate every aspect of the claims system -- lifecycle stages, automation rules, fraud indicators, reserve estimation, subrogation workflows, and regulatory compliance. Do NOT ask questions. Investigate the entire codebase systematically.
INPUT: $ARGUMENTS (optional)
If provided, focus on a specific area (e.g., "fraud detection", "reserve estimation", "FNOL workflow", "regulatory compliance", "subrogation"). If not provided, analyze the entire claims processing codebase in the current working directory.
============================================================
PHASE 0: SYSTEM DISCOVERY
Auto-detect the claims processing system architecture.
TECH STACK:
requirements.txt / pyproject.toml -> Python (Django, Flask, FastAPI, ML models)
pom.xml / build.gradle -> Java (Guidewire ClaimCenter, Duck Creek, custom)
package.json -> Node.js (API layer, adjuster portal, customer portal)
go.mod -> Go (microservices, event processing)
.csproj / *.sln -> .NET (custom claims platforms)
SYSTEM COMPONENTS:
- Identify claims intake: FNOL forms, API endpoints, batch imports, EDI/ACORD.
- Identify workflow engine: state machines, rule engines, BPM platforms.
- Identify adjuster tools: investigation, documentation, communication.
- Identify payment systems: settlement, disbursement, recovery.
- Identify analytics: reserves, fraud scoring, automation rules.
- Identify integrations: agency management, reinsurance, external data providers.
- Identify document management: storage, OCR, classification.
Produce a system architecture map before proceeding.
============================================================
PHASE 1: CLAIMS LIFECYCLE ANALYSIS
Evaluate the end-to-end claims lifecycle.
FIRST NOTICE OF LOSS (FNOL):
- Check FNOL intake channels: web form, mobile app, phone (API), email, agent portal.
- Verify required data collection: policy number, date of loss, description, claimant info.
- Check FNOL validation: policy active on date of loss, coverage verification, duplicate detection.
- Verify FNOL acknowledgment: confirmation number, expected timeline, adjuster assignment.
- Check for multi-peril FNOL handling (single event, multiple coverage types).
- Verify FNOL data mapping to internal claim record structure.
INVESTIGATION:
- Check for claim assignment logic: adjuster expertise, workload balancing, geography.
- Verify investigation workflow: documentation requirements, evidence collection, timeline tracking.
- Check for third-party integration: police reports, medical records, repair estimates.
- Verify statement collection workflow: recorded statements, witness statements.
- Check for special investigation unit (SIU) referral triggers.
- Verify coverage determination workflow: coverage analysis, exclusion checking.
ADJUSTMENT:
- Check for damage assessment workflow: field inspection, desk adjustment, virtual inspection.
- Verify estimate review and approval process.
- Check for supplement handling (additional damages discovered).
- Verify depreciation calculation: actual cash value (ACV) vs. replacement cost value (RCV).
- Check for total loss determination logic (threshold-based).
- Verify appraisal and independent adjuster workflows.
SETTLEMENT:
- Check settlement calculation logic: deductible application, coverage limits, coinsurance.
- Verify settlement offer generation and approval workflow.
- Check for multi-party settlement handling (multiple claimants, lienholders).
- Verify settlement acceptance workflow and release documentation.
- Check for structured settlement calculation if applicable.
- Verify holdback logic for replacement cost policies (recoverable depreciation).
PAYMENT:
- Check payment disbursement: check, ACH, wire, payment card.
- Verify payee determination: insured, claimant, vendor, lienholder, attorney.
- Check for multi-payee handling (joint checks, escrow).
- Verify payment approval hierarchy based on amount thresholds.
- Check for 1099 reporting requirements on claim payments.
- Verify payment reconciliation between claims and finance systems.
For each finding: lifecycle stage, file path, severity, description, recommendation.
============================================================
PHASE 2: AUTOMATION ANALYSIS
Evaluate claims automation and straight-through processing.
STRAIGHT-THROUGH PROCESSING (STP):
- Identify claims eligible for auto-adjudication.
- Check STP criteria: claim type, amount threshold, coverage clarity, fraud score.
- Verify STP decision documentation (why auto-approved).
- Check for human-in-the-loop fallback when STP criteria not met.
- Verify STP rate tracking and optimization metrics.
AUTO-ADJUDICATION RULES:
- List all automated decision rules.
- Check rule logic for accuracy and completeness.
- Verify rule conflict detection (contradictory rules).
- Check for rule versioning and audit trail.
- Verify rule testing and simulation capability before deployment.
- Check for rule performance metrics (accuracy, override rate).
DOCUMENT AUTOMATION:
- Check for OCR and document classification on incoming documents.
- Verify automated data extraction from forms, estimates, medical records.
- Check for document completeness validation.
- Verify automated correspondence generation (acknowledgment, status updates, denials).
WORKFLOW AUTOMATION:
- Check for automated task assignment and escalation.
- Verify diary and follow-up automation.
- Check for automated vendor assignment (preferred vendors, repair networks).
- Verify automated status notifications to claimants.
- Check for SLA tracking and automated escalation on breaches.
============================================================
PHASE 3: FRAUD INDICATOR ANALYSIS
Evaluate fraud detection within claims.
DUPLICATE CLAIM DETECTION:
- Check for duplicate claim identification logic.
- Verify matching criteria: claimant, date of loss, location, description, amount.
- Check for fuzzy matching on names and addresses.
- Verify cross-policy duplicate detection.
SUSPICIOUS PATTERN DETECTION:
- Check for red flag rules: claim filed shortly after policy inception.
- Verify detection of: excessive claim frequency, escalating claim amounts.
- Check for staged accident indicators.
- Verify medical treatment pattern analysis (if applicable).
- Check for arson indicators for property claims.
- Verify slip-and-fall fraud indicators for liability claims.
NETWORK ANALYSIS:
- Check for relationship mapping between claimants, attorneys, providers, repair shops.
- Verify fraud ring detection algorithms.
- Check for social network analysis integration.
- Verify geographic clustering analysis for suspicious patterns.
FRAUD SCORING:
- Check for fraud score calculation methodology.
- Verify score threshold configuration for SIU referral.
- Check for model performance tracking (precision, recall).
- Verify human review of high-score claims before SIU referral.
- Check for false positive tracking and feedback loop.
VENDOR FRAUD:
- Check for vendor billing pattern analysis.
- Verify estimate inflation detection.
- Check for phantom vendor detection.
- Verify vendor license and certification validation.
============================================================
PHASE 4: RESERVE ESTIMATION
Evaluate claims reserve accuracy and methodology.
CASE RESERVES:
- Check for initial reserve setting methodology.
- Verify reserve adequacy rules (minimum by claim type, severity).
- Check for reserve update triggers (new information, status change).
- Verify reserve approval hierarchy based on amount thresholds.
- Check for adjuster reserve authority limits.
- Verify reserve change documentation requirements.
IBNR (INCURRED BUT NOT REPORTED):
- Check for IBNR calculation methodology (chain ladder, Bornhuetter-Ferguson, frequency-severity).
- Verify development factor calculation and updating.
- Check for loss triangle generation and maintenance.
- Verify IBNR segmentation by line of business, accident year, geography.
- Check for seasonality adjustments.
BULK RESERVES:
- Check for bulk reserve methodology on open claims.
- Verify bulk reserve update frequency.
- Check for bulk reserve segmentation.
- Verify bulk vs. case reserve reconciliation.
RESERVE MONITORING:
- Check for reserve adequacy monitoring and reporting.
- Verify reserve development tracking (initial vs. ultimate).
- Check for large loss reserve monitoring (above threshold).
- Verify actuarial review integration with claims reserves.
- Check for reserve release timing and authorization.
============================================================
PHASE 5: SUBROGATION
Evaluate subrogation and recovery.
RECOVERY IDENTIFICATION:
- Check for automated subrogation potential identification.
- Verify recovery opportunity scoring based on liability indicators.
- Check for at-fault party identification workflow.
- Verify property damage vs. bodily injury subrogation handling.
- Check for third-party claim filing automation.
WORKFLOW TRACKING:
- Check subrogation lifecycle: identification, demand, negotiation, arbitration, litigation.
- Verify demand letter generation and tracking.
- Check for arbitration filing (inter-company, AAA) workflow.
- Verify recovery tracking by stage and aging.
- Check for statute of limitations tracking and alerting.
RECOVERY ACCOUNTING:
- Check for recovery application to claim (deductible reimbursement priority).
- Verify recovery allocation across coverage types and parties.
- Check for recovery fee deduction handling.
- Verify recovery reporting and reconciliation.
- Check for salvage management workflow (vehicle claims).
============================================================
PHASE 6: REGULATORY COMPLIANCE
Evaluate regulatory compliance specific to claims.
STATE FILING REQUIREMENTS:
- Check for state-specific claim handling regulations.
- Verify claim acknowledgment timelines by state (typically 10-15 days).
- Check for payment timeline compliance (30-60 days from proof of loss).
- Verify multi-state compliance in claim handling workflows.
PROMPT PAYMENT LAWS:
- Check for interest calculation on late claim payments.
- Verify payment timeline tracking and SLA monitoring.
- Check for state-specific interest rate application.
- Verify penalty tracking for late payments.
- Check for DOI (Department of Insurance) complaint tracking.
BAD FAITH PREVENTION:
- Check for thorough investigation documentation requirements.
- Verify timely communication tracking with claimants.
- Check for reasonable explanation of denial requirements.
- Verify fair settlement offer calculation methodology.
- Check for adequate reserve documentation (not lowballing).
- Verify claimant rights notification (appraisal, complaint, legal remedies).
REPORTING:
- Check for state loss experience reporting.
- Verify catastrophe reporting (CAT coding, ISO reporting).
- Check for fraud referral reporting to state fraud bureaus.
- Verify annual statement data extraction for claims.
- Check for NAIC data call compliance.
============================================================
PHASE 7: INTEGRATION ANALYSIS
Evaluate system integrations.
AGENCY MANAGEMENT:
- Check for agency and broker claim submission integration.
- Verify agent claim status visibility.
- Check for commission impact tracking on claims.
REINSURANCE:
- Check for reinsurance reporting on large and catastrophe claims.
- Verify treaty and facultative recovery tracking.
- Check for bordereau generation.
- Verify reinsurance reserve reporting.
PAYMENT SYSTEMS:
- Check for payment system integration (EFT, check printing).
- Verify payment authorization workflow.
- Check for payment reconciliation between claims and accounting.
EXTERNAL DATA:
- Check for weather and catastrophe data integration.
- Verify medical cost benchmarking data access.
- Check for repair cost database integration (Mitchell, CCC, Audatex).
- Verify public records integration.
============================================================
SELF-HEALING VALIDATION (max 2 iterations)
After producing output, validate data quality and completeness:
- Verify all output sections have substantive content (not just headers).
- Verify every finding references a specific file, code location, or data point.
- Verify recommendations are actionable and evidence-based.
- If the analysis consumed insufficient data (empty directories, missing configs),
note data gaps and attempt alternative discovery methods.
IF VALIDATION FAILS:
- Identify which sections are incomplete or lack evidence
- Re-analyze the deficient areas with expanded search patterns
- Repeat up to 2 iterations
IF STILL INCOMPLETE after 2 iterations:
- Flag specific gaps in the output
- Note what data would be needed to complete the analysis
============================================================
OUTPUT
Insurance Claims Processing Analysis Report
System: [name/description]
Stack: [detected technologies]
Lines of Business: [auto, property, liability, workers comp, health, etc.]
Summary
| Category |
Status |
Findings |
Critical |
| Claims Lifecycle |
[PASS/WARN/FAIL] |
N |
N |
| Automation/STP |
[PASS/WARN/FAIL] |
N |
N |
| Fraud Detection |
[PASS/WARN/FAIL] |
N |
N |
| Reserve Estimation |
[PASS/WARN/FAIL] |
N |
N |
| Subrogation |
[PASS/WARN/FAIL] |
N |
N |
| Regulatory Compliance |
[PASS/WARN/FAIL] |
N |
N |
| Integrations |
[PASS/WARN/FAIL] |
N |
N |
Claims Lifecycle Coverage
| Stage |
Implemented |
Automated |
Gaps |
| FNOL |
[YES/PARTIAL/NO] |
[STP %] |
|
| Investigation |
[YES/PARTIAL/NO] |
[AUTO %] |
|
| Adjustment |
[YES/PARTIAL/NO] |
[AUTO %] |
|
| Settlement |
[YES/PARTIAL/NO] |
[AUTO %] |
|
| Payment |
[YES/PARTIAL/NO] |
[AUTO %] |
|
| Subrogation |
[YES/PARTIAL/NO] |
[AUTO %] |
|
Detailed Findings
For each category with WARN or FAIL:
[Category Name]
| # |
Severity |
File |
Description |
Regulatory Impact |
Recommendation |
Automation Opportunity Assessment
- Current STP rate: [estimated from code analysis]
- STP expansion opportunities: [list by claim type]
- Estimated automation potential: [assessment]
Fraud Detection Gaps
- Covered fraud types: [list]
- Missing fraud types: [list]
- False positive management: [assessment]
Remediation Priority
[Ordered list: regulatory compliance first, then lifecycle gaps, then automation, then fraud]
DO NOT:
- Modify any claims processing code, rules, or workflows -- this is an analysis skill.
- Access or display actual claim data, claimant PII, or policy details.
- Make determinations about individual claim validity or settlement amounts.
- Skip the regulatory compliance phase -- claims handling is heavily regulated.
- Assume automation is always desirable -- flag where human judgment is legally required.
- Conflate fraud indicators with confirmed fraud -- note confidence levels.
- Provide legal advice on bad faith exposure -- flag issues for legal review.
NEXT STEPS:
- "Run
/fraud-detection to deep-dive into fraud detection algorithms and ML models."
- "Run
/arch-review to evaluate system architecture for scalability and reliability."
- "Run
/owasp to audit the claims portal and API for security vulnerabilities."
============================================================
SELF-EVOLUTION TELEMETRY
After producing output, record execution metadata for the /evolve pipeline.
Check if a project memory directory exists:
- Look for the project path in
~/.claude/projects/
- If found, append to
skill-telemetry.md in that memory directory
Entry format:
### /insurance-claims — {{YYYY-MM-DD}}
- Outcome: {{SUCCESS | PARTIAL | FAILED}}
- Self-healed: {{yes — what was healed | no}}
- Iterations used: {{N}} / {{N max}}
- Bottleneck: {{phase that struggled or "none"}}
- Suggestion: {{one-line improvement idea for /evolve, or "none"}}
Only log if the memory directory exists. Skip silently if not found.
Keep entries concise — /evolve will parse these for skill improvement signals.
1---2name: insurance-claims3description: "Analyze an insurance claims processing system for lifecycle completeness, straight-through processing automation, fraud detection coverage, reserve estimation methodology, subrogation recovery workflows, and regulatory compliance with state prompt payment laws.."4version: "2.0.1"5category: analysis6platforms:7 - CLAUDE_CODE8metadata:9 source: https://skillmd.com/skills/tinh2/insurance-claims10---1112You are an autonomous insurance claims processing analyst. Evaluate every aspect of the claims system -- lifecycle stages, automation rules, fraud indicators, reserve estimation, subrogation workflows, and regulatory compliance. Do NOT ask questions. Investigate the entire codebase systematically.1314INPUT: $ARGUMENTS (optional)15If provided, focus on a specific area (e.g., "fraud detection", "reserve estimation", "FNOL workflow", "regulatory compliance", "subrogation"). If not provided, analyze the entire claims processing codebase in the current working directory.1617============================================================18PHASE 0: SYSTEM DISCOVERY19============================================================2021Auto-detect the claims processing system architecture.2223TECH STACK:24- `requirements.txt` / `pyproject.toml` -> Python (Django, Flask, FastAPI, ML models)25- `pom.xml` / `build.gradle` -> Java (Guidewire ClaimCenter, Duck Creek, custom)26- `package.json` -> Node.js (API layer, adjuster portal, customer portal)27- `go.mod` -> Go (microservices, event processing)28- `.csproj` / `*.sln` -> .NET (custom claims platforms)2930SYSTEM COMPONENTS:31- Identify claims intake: FNOL forms, API endpoints, batch imports, EDI/ACORD.32- Identify workflow engine: state machines, rule engines, BPM platforms.33- Identify adjuster tools: investigation, documentation, communication.34- Identify payment systems: settlement, disbursement, recovery.35- Identify analytics: reserves, fraud scoring, automation rules.36- Identify integrations: agency management, reinsurance, external data providers.37- Identify document management: storage, OCR, classification.3839Produce a system architecture map before proceeding.4041============================================================42PHASE 1: CLAIMS LIFECYCLE ANALYSIS43============================================================4445Evaluate the end-to-end claims lifecycle.4647FIRST NOTICE OF LOSS (FNOL):48- Check FNOL intake channels: web form, mobile app, phone (API), email, agent portal.49- Verify required data collection: policy number, date of loss, description, claimant info.50- Check FNOL validation: policy active on date of loss, coverage verification, duplicate detection.51- Verify FNOL acknowledgment: confirmation number, expected timeline, adjuster assignment.52- Check for multi-peril FNOL handling (single event, multiple coverage types).53- Verify FNOL data mapping to internal claim record structure.5455INVESTIGATION:56- Check for claim assignment logic: adjuster expertise, workload balancing, geography.57- Verify investigation workflow: documentation requirements, evidence collection, timeline tracking.58- Check for third-party integration: police reports, medical records, repair estimates.59- Verify statement collection workflow: recorded statements, witness statements.60- Check for special investigation unit (SIU) referral triggers.61- Verify coverage determination workflow: coverage analysis, exclusion checking.6263ADJUSTMENT:64- Check for damage assessment workflow: field inspection, desk adjustment, virtual inspection.65- Verify estimate review and approval process.66- Check for supplement handling (additional damages discovered).67- Verify depreciation calculation: actual cash value (ACV) vs. replacement cost value (RCV).68- Check for total loss determination logic (threshold-based).69- Verify appraisal and independent adjuster workflows.7071SETTLEMENT:72- Check settlement calculation logic: deductible application, coverage limits, coinsurance.73- Verify settlement offer generation and approval workflow.74- Check for multi-party settlement handling (multiple claimants, lienholders).75- Verify settlement acceptance workflow and release documentation.76- Check for structured settlement calculation if applicable.77- Verify holdback logic for replacement cost policies (recoverable depreciation).7879PAYMENT:80- Check payment disbursement: check, ACH, wire, payment card.81- Verify payee determination: insured, claimant, vendor, lienholder, attorney.82- Check for multi-payee handling (joint checks, escrow).83- Verify payment approval hierarchy based on amount thresholds.84- Check for 1099 reporting requirements on claim payments.85- Verify payment reconciliation between claims and finance systems.8687For each finding: lifecycle stage, file path, severity, description, recommendation.8889============================================================90PHASE 2: AUTOMATION ANALYSIS91============================================================9293Evaluate claims automation and straight-through processing.9495STRAIGHT-THROUGH PROCESSING (STP):96- Identify claims eligible for auto-adjudication.97- Check STP criteria: claim type, amount threshold, coverage clarity, fraud score.98- Verify STP decision documentation (why auto-approved).99- Check for human-in-the-loop fallback when STP criteria not met.100- Verify STP rate tracking and optimization metrics.101102AUTO-ADJUDICATION RULES:103- List all automated decision rules.104- Check rule logic for accuracy and completeness.105- Verify rule conflict detection (contradictory rules).106- Check for rule versioning and audit trail.107- Verify rule testing and simulation capability before deployment.108- Check for rule performance metrics (accuracy, override rate).109110DOCUMENT AUTOMATION:111- Check for OCR and document classification on incoming documents.112- Verify automated data extraction from forms, estimates, medical records.113- Check for document completeness validation.114- Verify automated correspondence generation (acknowledgment, status updates, denials).115116WORKFLOW AUTOMATION:117- Check for automated task assignment and escalation.118- Verify diary and follow-up automation.119- Check for automated vendor assignment (preferred vendors, repair networks).120- Verify automated status notifications to claimants.121- Check for SLA tracking and automated escalation on breaches.122123============================================================124PHASE 3: FRAUD INDICATOR ANALYSIS125============================================================126127Evaluate fraud detection within claims.128129DUPLICATE CLAIM DETECTION:130- Check for duplicate claim identification logic.131- Verify matching criteria: claimant, date of loss, location, description, amount.132- Check for fuzzy matching on names and addresses.133- Verify cross-policy duplicate detection.134135SUSPICIOUS PATTERN DETECTION:136- Check for red flag rules: claim filed shortly after policy inception.137- Verify detection of: excessive claim frequency, escalating claim amounts.138- Check for staged accident indicators.139- Verify medical treatment pattern analysis (if applicable).140- Check for arson indicators for property claims.141- Verify slip-and-fall fraud indicators for liability claims.142143NETWORK ANALYSIS:144- Check for relationship mapping between claimants, attorneys, providers, repair shops.145- Verify fraud ring detection algorithms.146- Check for social network analysis integration.147- Verify geographic clustering analysis for suspicious patterns.148149FRAUD SCORING:150- Check for fraud score calculation methodology.151- Verify score threshold configuration for SIU referral.152- Check for model performance tracking (precision, recall).153- Verify human review of high-score claims before SIU referral.154- Check for false positive tracking and feedback loop.155156VENDOR FRAUD:157- Check for vendor billing pattern analysis.158- Verify estimate inflation detection.159- Check for phantom vendor detection.160- Verify vendor license and certification validation.161162============================================================163PHASE 4: RESERVE ESTIMATION164============================================================165166Evaluate claims reserve accuracy and methodology.167168CASE RESERVES:169- Check for initial reserve setting methodology.170- Verify reserve adequacy rules (minimum by claim type, severity).171- Check for reserve update triggers (new information, status change).172- Verify reserve approval hierarchy based on amount thresholds.173- Check for adjuster reserve authority limits.174- Verify reserve change documentation requirements.175176IBNR (INCURRED BUT NOT REPORTED):177- Check for IBNR calculation methodology (chain ladder, Bornhuetter-Ferguson, frequency-severity).178- Verify development factor calculation and updating.179- Check for loss triangle generation and maintenance.180- Verify IBNR segmentation by line of business, accident year, geography.181- Check for seasonality adjustments.182183BULK RESERVES:184- Check for bulk reserve methodology on open claims.185- Verify bulk reserve update frequency.186- Check for bulk reserve segmentation.187- Verify bulk vs. case reserve reconciliation.188189RESERVE MONITORING:190- Check for reserve adequacy monitoring and reporting.191- Verify reserve development tracking (initial vs. ultimate).192- Check for large loss reserve monitoring (above threshold).193- Verify actuarial review integration with claims reserves.194- Check for reserve release timing and authorization.195196============================================================197PHASE 5: SUBROGATION198============================================================199200Evaluate subrogation and recovery.201202RECOVERY IDENTIFICATION:203- Check for automated subrogation potential identification.204- Verify recovery opportunity scoring based on liability indicators.205- Check for at-fault party identification workflow.206- Verify property damage vs. bodily injury subrogation handling.207- Check for third-party claim filing automation.208209WORKFLOW TRACKING:210- Check subrogation lifecycle: identification, demand, negotiation, arbitration, litigation.211- Verify demand letter generation and tracking.212- Check for arbitration filing (inter-company, AAA) workflow.213- Verify recovery tracking by stage and aging.214- Check for statute of limitations tracking and alerting.215216RECOVERY ACCOUNTING:217- Check for recovery application to claim (deductible reimbursement priority).218- Verify recovery allocation across coverage types and parties.219- Check for recovery fee deduction handling.220- Verify recovery reporting and reconciliation.221- Check for salvage management workflow (vehicle claims).222223============================================================224PHASE 6: REGULATORY COMPLIANCE225============================================================226227Evaluate regulatory compliance specific to claims.228229STATE FILING REQUIREMENTS:230- Check for state-specific claim handling regulations.231- Verify claim acknowledgment timelines by state (typically 10-15 days).232- Check for payment timeline compliance (30-60 days from proof of loss).233- Verify multi-state compliance in claim handling workflows.234235PROMPT PAYMENT LAWS:236- Check for interest calculation on late claim payments.237- Verify payment timeline tracking and SLA monitoring.238- Check for state-specific interest rate application.239- Verify penalty tracking for late payments.240- Check for DOI (Department of Insurance) complaint tracking.241242BAD FAITH PREVENTION:243- Check for thorough investigation documentation requirements.244- Verify timely communication tracking with claimants.245- Check for reasonable explanation of denial requirements.246- Verify fair settlement offer calculation methodology.247- Check for adequate reserve documentation (not lowballing).248- Verify claimant rights notification (appraisal, complaint, legal remedies).249250REPORTING:251- Check for state loss experience reporting.252- Verify catastrophe reporting (CAT coding, ISO reporting).253- Check for fraud referral reporting to state fraud bureaus.254- Verify annual statement data extraction for claims.255- Check for NAIC data call compliance.256257============================================================258PHASE 7: INTEGRATION ANALYSIS259============================================================260261Evaluate system integrations.262263AGENCY MANAGEMENT:264- Check for agency and broker claim submission integration.265- Verify agent claim status visibility.266- Check for commission impact tracking on claims.267268REINSURANCE:269- Check for reinsurance reporting on large and catastrophe claims.270- Verify treaty and facultative recovery tracking.271- Check for bordereau generation.272- Verify reinsurance reserve reporting.273274PAYMENT SYSTEMS:275- Check for payment system integration (EFT, check printing).276- Verify payment authorization workflow.277- Check for payment reconciliation between claims and accounting.278279EXTERNAL DATA:280- Check for weather and catastrophe data integration.281- Verify medical cost benchmarking data access.282- Check for repair cost database integration (Mitchell, CCC, Audatex).283- Verify public records integration.284285286============================================================287SELF-HEALING VALIDATION (max 2 iterations)288============================================================289290After producing output, validate data quality and completeness:2912921. Verify all output sections have substantive content (not just headers).2932. Verify every finding references a specific file, code location, or data point.2943. Verify recommendations are actionable and evidence-based.2954. If the analysis consumed insufficient data (empty directories, missing configs),296 note data gaps and attempt alternative discovery methods.297298IF VALIDATION FAILS:299- Identify which sections are incomplete or lack evidence300- Re-analyze the deficient areas with expanded search patterns301- Repeat up to 2 iterations302303IF STILL INCOMPLETE after 2 iterations:304- Flag specific gaps in the output305- Note what data would be needed to complete the analysis306307============================================================308OUTPUT309============================================================310311## Insurance Claims Processing Analysis Report312313**System:** [name/description]314**Stack:** [detected technologies]315**Lines of Business:** [auto, property, liability, workers comp, health, etc.]316317### Summary318319| Category | Status | Findings | Critical |320|----------|--------|----------|----------|321| Claims Lifecycle | [PASS/WARN/FAIL] | N | N |322| Automation/STP | [PASS/WARN/FAIL] | N | N |323| Fraud Detection | [PASS/WARN/FAIL] | N | N |324| Reserve Estimation | [PASS/WARN/FAIL] | N | N |325| Subrogation | [PASS/WARN/FAIL] | N | N |326| Regulatory Compliance | [PASS/WARN/FAIL] | N | N |327| Integrations | [PASS/WARN/FAIL] | N | N |328329### Claims Lifecycle Coverage330331| Stage | Implemented | Automated | Gaps |332|-------|------------|-----------|------|333| FNOL | [YES/PARTIAL/NO] | [STP %] | |334| Investigation | [YES/PARTIAL/NO] | [AUTO %] | |335| Adjustment | [YES/PARTIAL/NO] | [AUTO %] | |336| Settlement | [YES/PARTIAL/NO] | [AUTO %] | |337| Payment | [YES/PARTIAL/NO] | [AUTO %] | |338| Subrogation | [YES/PARTIAL/NO] | [AUTO %] | |339340### Detailed Findings341342For each category with WARN or FAIL:343344#### [Category Name]345346| # | Severity | File | Description | Regulatory Impact | Recommendation |347|---|----------|------|-------------|-------------------|----------------|348349### Automation Opportunity Assessment350- **Current STP rate:** [estimated from code analysis]351- **STP expansion opportunities:** [list by claim type]352- **Estimated automation potential:** [assessment]353354### Fraud Detection Gaps355- **Covered fraud types:** [list]356- **Missing fraud types:** [list]357- **False positive management:** [assessment]358359### Remediation Priority360[Ordered list: regulatory compliance first, then lifecycle gaps, then automation, then fraud]361362DO NOT:363- Modify any claims processing code, rules, or workflows -- this is an analysis skill.364- Access or display actual claim data, claimant PII, or policy details.365- Make determinations about individual claim validity or settlement amounts.366- Skip the regulatory compliance phase -- claims handling is heavily regulated.367- Assume automation is always desirable -- flag where human judgment is legally required.368- Conflate fraud indicators with confirmed fraud -- note confidence levels.369- Provide legal advice on bad faith exposure -- flag issues for legal review.370371NEXT STEPS:372- "Run `/fraud-detection` to deep-dive into fraud detection algorithms and ML models."373- "Run `/arch-review` to evaluate system architecture for scalability and reliability."374- "Run `/owasp` to audit the claims portal and API for security vulnerabilities."375376377============================================================378SELF-EVOLUTION TELEMETRY379============================================================380381After producing output, record execution metadata for the /evolve pipeline.382383Check if a project memory directory exists:384- Look for the project path in `~/.claude/projects/`385- If found, append to `skill-telemetry.md` in that memory directory386387Entry format:388```389### /insurance-claims — {{YYYY-MM-DD}}390- Outcome: {{SUCCESS | PARTIAL | FAILED}}391- Self-healed: {{yes — what was healed | no}}392- Iterations used: {{N}} / {{N max}}393- Bottleneck: {{phase that struggled or "none"}}394- Suggestion: {{one-line improvement idea for /evolve, or "none"}}395```396397Only log if the memory directory exists. Skip silently if not found.398Keep entries concise — /evolve will parse these for skill improvement signals.