You are in AUTONOMOUS MODE. Do NOT ask questions. Review every regulatory domain systematically.
TARGET:
$ARGUMENTS
If no arguments provided, review the entire financial services codebase in the current
working directory against all applicable regulations.
============================================================
PHASE 0: REGULATORY SCOPE DETECTION
Auto-detect the financial services scope:
BUSINESS MODEL DETECTION:
- Identify the type of financial service: banking, lending, payments, money transfer,
investment, insurance, cryptocurrency, BNPL, neobank, embedded finance
- Detect regulated activities: fund transfers, credit issuance, securities trading,
money transmission, deposit taking, insurance underwriting
- Identify jurisdictions from configuration, legal entities, or licensing references
- Determine applicable regulatory framework based on business model
TECH STACK:
- Identify web framework, database, ORM, message queues, third-party integrations
- Identify identity verification services (Jumio, Onfido, Alloy, Persona, Plaid Identity)
- Identify sanctions screening services (Dow Jones, Refinitiv, ComplyAdvantage, Chainalysis)
- Identify transaction monitoring systems (custom, Actimize, Featurespace, Unit21)
- Identify reporting systems (FinCEN filings, state reports, SAR/CTR generation)
Produce a regulatory applicability matrix before proceeding.
============================================================
PHASE 1: KYC / AML COMPLIANCE
Review Know Your Customer and Anti-Money Laundering implementation:
CUSTOMER IDENTIFICATION PROGRAM (CIP):
- Verify collection of required identification: name, date of birth, address, ID number
- Check identity verification against government databases or document verification
- Verify ID document validation (expiration, format, authenticity checks)
- Check for beneficial ownership collection for legal entities (25% threshold)
- Verify recordkeeping of identification information and verification methods
- Check for CIP exceptions handling (existing customers, regulated entities)
CUSTOMER DUE DILIGENCE (CDD):
- Verify risk rating assignment during onboarding (low, medium, high, prohibited)
- Check risk scoring factors: geography, product type, transaction volume, industry
- Verify ongoing monitoring adjusts risk rating based on activity
- Check for periodic re-verification schedules based on risk tier
- Verify CDD documentation retention (5-year minimum after account closure)
ENHANCED DUE DILIGENCE (EDD):
- Check for EDD triggers: high-risk customers, PEPs, high-risk jurisdictions
- Verify additional information collection for high-risk customers
- Check for source of funds / source of wealth verification
- Verify senior management approval for high-risk relationships
- Check for ongoing enhanced monitoring for EDD customers
SANCTIONS SCREENING:
- Verify OFAC SDN list screening on customer onboarding
- Check for ongoing sanctions screening (not just onboarding)
- Verify screening against all applicable lists (OFAC SDN, EU, UN, UK HMT)
- Check fuzzy matching logic and threshold configuration
- Verify match review workflow and false positive disposition
- Check for real-time screening on transactions (not just customer screening)
- Verify sanctions screening on counterparties and beneficiaries
TRANSACTION MONITORING:
- Check for suspicious activity detection rules
- Verify monitoring covers: structuring, rapid movement, unusual patterns, layering
- Check threshold calibration and tuning documentation
- Verify alert investigation workflow and escalation procedures
- Check for typology coverage (trade-based laundering, funnel accounts, etc.)
- Verify retroactive monitoring when customer risk changes
For each finding: regulatory reference, file path, severity, description, remediation.
============================================================
PHASE 2: BSA (BANK SECRECY ACT) COMPLIANCE
Review BSA-specific requirements:
SUSPICIOUS ACTIVITY REPORTING:
- Verify SAR filing workflow exists for transactions > $5,000
- Check SAR narrative generation includes required elements (5 W's)
- Verify 30-day filing deadline tracking from initial detection
- Check for continuing activity SAR filing (90-day reviews)
- Verify SAR confidentiality (no tipping off)
- Check SAR data retention (5 years from filing)
CURRENCY TRANSACTION REPORTING:
- Verify CTR generation for cash transactions > $10,000
- Check for aggregate same-day cash transaction calculation
- Verify CTR e-filing integration with FinCEN BSA E-Filing
- Check for multiple transaction aggregation by customer
- Verify CTR exemption management for eligible businesses
RECORDKEEPING:
- Check that records of transactions > $3,000 are maintained
- Verify funds transfer recordkeeping (Travel Rule for transfers > $3,000)
- Check for 5-year retention of BSA records
- Verify records are retrievable within reasonable timeframe
- Check for purchase of monetary instruments > $3,000 records
BSA/AML PROGRAM ELEMENTS:
- Verify internal controls implementation in code
- Check for compliance officer designation references
- Verify training program references or requirements
- Check for independent audit/testing references
============================================================
PHASE 3: REGULATION E COMPLIANCE
Review electronic fund transfer compliance:
DISCLOSURE REQUIREMENTS:
- Check for initial disclosures on EFT service enrollment
- Verify terms and conditions include required Reg E disclosures
- Check for change-in-terms notification implementation
- Verify periodic statement generation with required elements
- Check for receipt generation on electronic transfers
ERROR RESOLUTION:
- Verify error resolution workflow exists with required timelines:
- 10 business days to investigate (20 for new accounts)
- Provisional credit within 10 days if investigation extends
- 45 calendar days maximum resolution (90 for certain transactions)
- Check that error reports trigger investigation workflow
- Verify consumer notification of investigation results
- Check for error correction and credit application logic
UNAUTHORIZED TRANSFERS:
- Verify unauthorized transfer liability limits:
- $0 if reported before transfer
- $50 if reported within 2 business days
- $500 if reported within 60 days of statement
- Unlimited after 60 days
- Check that liability calculation logic matches regulatory requirements
- Verify provisional credit implementation during investigation
- Check for fraud detection on consumer accounts
PREAUTHORIZED TRANSFERS:
- Check for consumer authorization requirements
- Verify stop payment capability and processing
- Check for notification of varying amount preauthorized transfers
- Verify right to stop payment is communicated
============================================================
PHASE 4: SOX (SARBANES-OXLEY) COMPLIANCE
Review financial reporting controls in code:
FINANCIAL REPORTING CONTROLS:
- Check for data validation on financial calculations and reports
- Verify calculation accuracy (rounding, currency conversion, accrual logic)
- Check for reconciliation processes between systems
- Verify financial data cannot be modified without audit trail
- Check for approval workflows on financial adjustments
AUDIT TRAIL:
- Verify all financial data changes are logged with actor, timestamp, before/after values
- Check for immutable audit logs (append-only, no deletion)
- Verify audit log retention meets requirements (7-year minimum for SOX)
- Check that audit logs capture both successful and failed operations
- Verify audit log integrity protection (hashing, tamper detection)
SEGREGATION OF DUTIES:
- Check for role separation in financial workflows:
- Initiator cannot approve their own transactions
- Administrator cannot process financial transactions
- Developers cannot deploy to production without approval
- Verify dual authorization for high-value operations
- Check for separation between transaction recording and reconciliation
- Verify access control enforces segregation in code
INTERNAL CONTROLS:
- Check for automated control points in financial processes
- Verify exception reporting when controls are bypassed
- Check for management override logging
- Verify control testing automation or hooks
============================================================
PHASE 5: GLBA (GRAMM-LEACH-BLILEY ACT) COMPLIANCE
Review privacy and data protection:
PRIVACY NOTICES:
- Check for initial privacy notice delivery on account opening
- Verify annual privacy notice distribution mechanism
- Check that privacy notice content includes required elements:
- Categories of information collected
- Categories of information disclosed
- Third parties receiving information
- Consumer opt-out rights
- Verify opt-out mechanism implementation and processing
- Check for revised privacy notice when practices change
DATA SHARING CONTROLS:
- Verify data sharing with third parties respects opt-out elections
- Check for data sharing agreements referenced in code
- Verify exceptions to opt-out requirements (joint marketing, service providers)
- Check for third-party data use restrictions enforcement
- Verify data sharing logging and tracking
SAFEGUARDS RULE:
- Check for access controls protecting customer financial information
- Verify encryption of customer data at rest and in transit
- Check for data loss prevention measures
- Verify employee access is limited to business need
- Check for security incident response procedures
- Verify vendor management for third-party access to customer data
============================================================
PHASE 6: STATE MONEY TRANSMITTER COMPLIANCE
Review state-level requirements:
LICENSE TRACKING:
- Check for state license tracking system or configuration
- Verify multi-state compliance (each state has different requirements)
- Check for license renewal tracking and alerting
- Verify surety bond amount tracking per state
STATE REPORTING:
- Check for state-specific reporting generation (quarterly, annual)
- Verify transaction volume reporting by state
- Check for complaint tracking and reporting mechanisms
- Verify state examination support (data export, record retrieval)
STATE-SPECIFIC REQUIREMENTS:
- Check for state-specific transaction limits
- Verify state-specific disclosure requirements
- Check for state-specific refund policies (California, New York have specific rules)
- Verify state-specific record retention requirements
============================================================
SELF-HEALING VALIDATION (max 2 iterations)
After producing the review, validate completeness and consistency:
- Verify all required output sections are present and non-empty.
- Verify every finding references a specific file or code location.
- Verify recommendations are actionable (not vague).
- Verify severity ratings are justified by evidence.
IF VALIDATION FAILS:
- Identify which sections are incomplete or lack specificity
- Re-analyze the deficient areas
- Repeat up to 2 iterations
============================================================
OUTPUT
Financial Regulatory Compliance Review
System: [name/description]
Business Model: [detected financial service type]
Stack: [detected technologies]
Regulatory Applicability
| Regulation |
Applicable |
Reason |
| KYC/AML |
[YES/NO/PARTIAL] |
[reason] |
| BSA |
[YES/NO/PARTIAL] |
[reason] |
| Reg E |
[YES/NO/PARTIAL] |
[reason] |
| SOX |
[YES/NO/PARTIAL] |
[reason] |
| GLBA |
[YES/NO/PARTIAL] |
[reason] |
| State MTL |
[YES/NO/PARTIAL] |
[reason] |
Summary
| Regulation |
Status |
Findings |
Critical |
| KYC/AML |
[PASS/WARN/FAIL] |
N |
N |
| BSA |
[PASS/WARN/FAIL] |
N |
N |
| Reg E |
[PASS/WARN/FAIL] |
N |
N |
| SOX |
[PASS/WARN/FAIL] |
N |
N |
| GLBA |
[PASS/WARN/FAIL] |
N |
N |
| State MTL |
[PASS/WARN/FAIL] |
N |
N |
Detailed Findings
For each regulation with WARN or FAIL:
[Regulation Name]
| # |
Severity |
Reg Reference |
File |
Description |
Remediation |
Compliance Gap Analysis
- Missing workflows: [list of required but unimplemented regulatory workflows]
- Incomplete implementations: [list of partially implemented requirements]
- Documentation gaps: [list of missing required documentation]
Remediation Priority
[Ordered list by regulatory enforcement risk — KYC/AML and BSA first, then consumer protection]
============================================================
NEXT STEPS
After reviewing the compliance findings:
- "Run
/credit-risk to analyze credit decisioning models for fair lending compliance."
- "Run
/fraud-detection to evaluate transaction monitoring and SAR processes."
- "Run
/pci-dss to audit payment card data handling."
- "Run
/owasp to check security posture of financial APIs."
- "Run
/analyze to trace regulatory workflows end-to-end across the system."
============================================================
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:
### /financial-compliance — {{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.
============================================================
DO NOT
- Do NOT modify any code — this is a review skill, not a remediation skill.
- Do NOT make definitive legal or compliance determinations — flag issues for legal review.
- Do NOT access or display actual customer data (PII, financial records, account numbers).
- Do NOT skip any regulatory domain — review all applicable regulations.
- Do NOT assume compliance based on the presence of a library — verify implementation.
- Do NOT conflate best practices with legal requirements — clearly label each.
- Do NOT provide jurisdiction-specific legal advice — note requirements and recommend legal counsel.
1---2name: financial-compliance3description: "Audit fintech and financial services code for KYC/AML (CIP, CDD, EDD, sanctions screening, transaction monitoring), BSA (SAR/CTR filing, FinCEN reporting, Travel Rule), Reg E (EFT error resolution, unauthorized transfer liability, provisional credit), SOX (audit trails."4version: "2.0.1"5category: review6platforms:7 - CLAUDE_CODE8metadata:9 source: https://skillmd.com/skills/tinh2/financial-compliance10---1112You are in AUTONOMOUS MODE. Do NOT ask questions. Review every regulatory domain systematically.1314TARGET:15$ARGUMENTS1617If no arguments provided, review the entire financial services codebase in the current18working directory against all applicable regulations.1920============================================================21PHASE 0: REGULATORY SCOPE DETECTION22============================================================2324Auto-detect the financial services scope:2526BUSINESS MODEL DETECTION:27- Identify the type of financial service: banking, lending, payments, money transfer,28 investment, insurance, cryptocurrency, BNPL, neobank, embedded finance29- Detect regulated activities: fund transfers, credit issuance, securities trading,30 money transmission, deposit taking, insurance underwriting31- Identify jurisdictions from configuration, legal entities, or licensing references32- Determine applicable regulatory framework based on business model3334TECH STACK:35- Identify web framework, database, ORM, message queues, third-party integrations36- Identify identity verification services (Jumio, Onfido, Alloy, Persona, Plaid Identity)37- Identify sanctions screening services (Dow Jones, Refinitiv, ComplyAdvantage, Chainalysis)38- Identify transaction monitoring systems (custom, Actimize, Featurespace, Unit21)39- Identify reporting systems (FinCEN filings, state reports, SAR/CTR generation)4041Produce a regulatory applicability matrix before proceeding.4243============================================================44PHASE 1: KYC / AML COMPLIANCE45============================================================4647Review Know Your Customer and Anti-Money Laundering implementation:4849CUSTOMER IDENTIFICATION PROGRAM (CIP):50- Verify collection of required identification: name, date of birth, address, ID number51- Check identity verification against government databases or document verification52- Verify ID document validation (expiration, format, authenticity checks)53- Check for beneficial ownership collection for legal entities (25% threshold)54- Verify recordkeeping of identification information and verification methods55- Check for CIP exceptions handling (existing customers, regulated entities)5657CUSTOMER DUE DILIGENCE (CDD):58- Verify risk rating assignment during onboarding (low, medium, high, prohibited)59- Check risk scoring factors: geography, product type, transaction volume, industry60- Verify ongoing monitoring adjusts risk rating based on activity61- Check for periodic re-verification schedules based on risk tier62- Verify CDD documentation retention (5-year minimum after account closure)6364ENHANCED DUE DILIGENCE (EDD):65- Check for EDD triggers: high-risk customers, PEPs, high-risk jurisdictions66- Verify additional information collection for high-risk customers67- Check for source of funds / source of wealth verification68- Verify senior management approval for high-risk relationships69- Check for ongoing enhanced monitoring for EDD customers7071SANCTIONS SCREENING:72- Verify OFAC SDN list screening on customer onboarding73- Check for ongoing sanctions screening (not just onboarding)74- Verify screening against all applicable lists (OFAC SDN, EU, UN, UK HMT)75- Check fuzzy matching logic and threshold configuration76- Verify match review workflow and false positive disposition77- Check for real-time screening on transactions (not just customer screening)78- Verify sanctions screening on counterparties and beneficiaries7980TRANSACTION MONITORING:81- Check for suspicious activity detection rules82- Verify monitoring covers: structuring, rapid movement, unusual patterns, layering83- Check threshold calibration and tuning documentation84- Verify alert investigation workflow and escalation procedures85- Check for typology coverage (trade-based laundering, funnel accounts, etc.)86- Verify retroactive monitoring when customer risk changes8788For each finding: regulatory reference, file path, severity, description, remediation.8990============================================================91PHASE 2: BSA (BANK SECRECY ACT) COMPLIANCE92============================================================9394Review BSA-specific requirements:9596SUSPICIOUS ACTIVITY REPORTING:97- Verify SAR filing workflow exists for transactions > $5,00098- Check SAR narrative generation includes required elements (5 W's)99- Verify 30-day filing deadline tracking from initial detection100- Check for continuing activity SAR filing (90-day reviews)101- Verify SAR confidentiality (no tipping off)102- Check SAR data retention (5 years from filing)103104CURRENCY TRANSACTION REPORTING:105- Verify CTR generation for cash transactions > $10,000106- Check for aggregate same-day cash transaction calculation107- Verify CTR e-filing integration with FinCEN BSA E-Filing108- Check for multiple transaction aggregation by customer109- Verify CTR exemption management for eligible businesses110111RECORDKEEPING:112- Check that records of transactions > $3,000 are maintained113- Verify funds transfer recordkeeping (Travel Rule for transfers > $3,000)114- Check for 5-year retention of BSA records115- Verify records are retrievable within reasonable timeframe116- Check for purchase of monetary instruments > $3,000 records117118BSA/AML PROGRAM ELEMENTS:119- Verify internal controls implementation in code120- Check for compliance officer designation references121- Verify training program references or requirements122- Check for independent audit/testing references123124============================================================125PHASE 3: REGULATION E COMPLIANCE126============================================================127128Review electronic fund transfer compliance:129130DISCLOSURE REQUIREMENTS:131- Check for initial disclosures on EFT service enrollment132- Verify terms and conditions include required Reg E disclosures133- Check for change-in-terms notification implementation134- Verify periodic statement generation with required elements135- Check for receipt generation on electronic transfers136137ERROR RESOLUTION:138- Verify error resolution workflow exists with required timelines:139 - 10 business days to investigate (20 for new accounts)140 - Provisional credit within 10 days if investigation extends141 - 45 calendar days maximum resolution (90 for certain transactions)142- Check that error reports trigger investigation workflow143- Verify consumer notification of investigation results144- Check for error correction and credit application logic145146UNAUTHORIZED TRANSFERS:147- Verify unauthorized transfer liability limits:148 - $0 if reported before transfer149 - $50 if reported within 2 business days150 - $500 if reported within 60 days of statement151 - Unlimited after 60 days152- Check that liability calculation logic matches regulatory requirements153- Verify provisional credit implementation during investigation154- Check for fraud detection on consumer accounts155156PREAUTHORIZED TRANSFERS:157- Check for consumer authorization requirements158- Verify stop payment capability and processing159- Check for notification of varying amount preauthorized transfers160- Verify right to stop payment is communicated161162============================================================163PHASE 4: SOX (SARBANES-OXLEY) COMPLIANCE164============================================================165166Review financial reporting controls in code:167168FINANCIAL REPORTING CONTROLS:169- Check for data validation on financial calculations and reports170- Verify calculation accuracy (rounding, currency conversion, accrual logic)171- Check for reconciliation processes between systems172- Verify financial data cannot be modified without audit trail173- Check for approval workflows on financial adjustments174175AUDIT TRAIL:176- Verify all financial data changes are logged with actor, timestamp, before/after values177- Check for immutable audit logs (append-only, no deletion)178- Verify audit log retention meets requirements (7-year minimum for SOX)179- Check that audit logs capture both successful and failed operations180- Verify audit log integrity protection (hashing, tamper detection)181182SEGREGATION OF DUTIES:183- Check for role separation in financial workflows:184 - Initiator cannot approve their own transactions185 - Administrator cannot process financial transactions186 - Developers cannot deploy to production without approval187- Verify dual authorization for high-value operations188- Check for separation between transaction recording and reconciliation189- Verify access control enforces segregation in code190191INTERNAL CONTROLS:192- Check for automated control points in financial processes193- Verify exception reporting when controls are bypassed194- Check for management override logging195- Verify control testing automation or hooks196197============================================================198PHASE 5: GLBA (GRAMM-LEACH-BLILEY ACT) COMPLIANCE199============================================================200201Review privacy and data protection:202203PRIVACY NOTICES:204- Check for initial privacy notice delivery on account opening205- Verify annual privacy notice distribution mechanism206- Check that privacy notice content includes required elements:207 - Categories of information collected208 - Categories of information disclosed209 - Third parties receiving information210 - Consumer opt-out rights211- Verify opt-out mechanism implementation and processing212- Check for revised privacy notice when practices change213214DATA SHARING CONTROLS:215- Verify data sharing with third parties respects opt-out elections216- Check for data sharing agreements referenced in code217- Verify exceptions to opt-out requirements (joint marketing, service providers)218- Check for third-party data use restrictions enforcement219- Verify data sharing logging and tracking220221SAFEGUARDS RULE:222- Check for access controls protecting customer financial information223- Verify encryption of customer data at rest and in transit224- Check for data loss prevention measures225- Verify employee access is limited to business need226- Check for security incident response procedures227- Verify vendor management for third-party access to customer data228229============================================================230PHASE 6: STATE MONEY TRANSMITTER COMPLIANCE231============================================================232233Review state-level requirements:234235LICENSE TRACKING:236- Check for state license tracking system or configuration237- Verify multi-state compliance (each state has different requirements)238- Check for license renewal tracking and alerting239- Verify surety bond amount tracking per state240241STATE REPORTING:242- Check for state-specific reporting generation (quarterly, annual)243- Verify transaction volume reporting by state244- Check for complaint tracking and reporting mechanisms245- Verify state examination support (data export, record retrieval)246247STATE-SPECIFIC REQUIREMENTS:248- Check for state-specific transaction limits249- Verify state-specific disclosure requirements250- Check for state-specific refund policies (California, New York have specific rules)251- Verify state-specific record retention requirements252253254============================================================255SELF-HEALING VALIDATION (max 2 iterations)256============================================================257258After producing the review, validate completeness and consistency:2592601. Verify all required output sections are present and non-empty.2612. Verify every finding references a specific file or code location.2623. Verify recommendations are actionable (not vague).2634. Verify severity ratings are justified by evidence.264265IF VALIDATION FAILS:266- Identify which sections are incomplete or lack specificity267- Re-analyze the deficient areas268- Repeat up to 2 iterations269270============================================================271OUTPUT272============================================================273274## Financial Regulatory Compliance Review275276**System:** [name/description]277**Business Model:** [detected financial service type]278**Stack:** [detected technologies]279280### Regulatory Applicability281282| Regulation | Applicable | Reason |283|------------|-----------|--------|284| KYC/AML | [YES/NO/PARTIAL] | [reason] |285| BSA | [YES/NO/PARTIAL] | [reason] |286| Reg E | [YES/NO/PARTIAL] | [reason] |287| SOX | [YES/NO/PARTIAL] | [reason] |288| GLBA | [YES/NO/PARTIAL] | [reason] |289| State MTL | [YES/NO/PARTIAL] | [reason] |290291### Summary292293| Regulation | Status | Findings | Critical |294|------------|--------|----------|----------|295| KYC/AML | [PASS/WARN/FAIL] | N | N |296| BSA | [PASS/WARN/FAIL] | N | N |297| Reg E | [PASS/WARN/FAIL] | N | N |298| SOX | [PASS/WARN/FAIL] | N | N |299| GLBA | [PASS/WARN/FAIL] | N | N |300| State MTL | [PASS/WARN/FAIL] | N | N |301302### Detailed Findings303304For each regulation with WARN or FAIL:305306#### [Regulation Name]307308| # | Severity | Reg Reference | File | Description | Remediation |309|---|----------|---------------|------|-------------|-------------|310311### Compliance Gap Analysis312- **Missing workflows:** [list of required but unimplemented regulatory workflows]313- **Incomplete implementations:** [list of partially implemented requirements]314- **Documentation gaps:** [list of missing required documentation]315316### Remediation Priority317[Ordered list by regulatory enforcement risk — KYC/AML and BSA first, then consumer protection]318319============================================================320NEXT STEPS321============================================================322323After reviewing the compliance findings:324- "Run `/credit-risk` to analyze credit decisioning models for fair lending compliance."325- "Run `/fraud-detection` to evaluate transaction monitoring and SAR processes."326- "Run `/pci-dss` to audit payment card data handling."327- "Run `/owasp` to check security posture of financial APIs."328- "Run `/analyze` to trace regulatory workflows end-to-end across the system."329330331============================================================332SELF-EVOLUTION TELEMETRY333============================================================334335After producing output, record execution metadata for the /evolve pipeline.336337Check if a project memory directory exists:338- Look for the project path in `~/.claude/projects/`339- If found, append to `skill-telemetry.md` in that memory directory340341Entry format:342```343### /financial-compliance — {{YYYY-MM-DD}}344- Outcome: {{SUCCESS | PARTIAL | FAILED}}345- Self-healed: {{yes — what was healed | no}}346- Iterations used: {{N}} / {{N max}}347- Bottleneck: {{phase that struggled or "none"}}348- Suggestion: {{one-line improvement idea for /evolve, or "none"}}349```350351Only log if the memory directory exists. Skip silently if not found.352Keep entries concise — /evolve will parse these for skill improvement signals.353354============================================================355DO NOT356============================================================357358- Do NOT modify any code — this is a review skill, not a remediation skill.359- Do NOT make definitive legal or compliance determinations — flag issues for legal review.360- Do NOT access or display actual customer data (PII, financial records, account numbers).361- Do NOT skip any regulatory domain — review all applicable regulations.362- Do NOT assume compliance based on the presence of a library — verify implementation.363- Do NOT conflate best practices with legal requirements — clearly label each.364- Do NOT provide jurisdiction-specific legal advice — note requirements and recommend legal counsel.