Compliance Skill

Compliance Skill

Usage: /compliance <command> <feature-name>

Description: Orchestrates the removal of enterprise gating from n8n features while preserving full functionality.

---

Commands

/compliance examine <feature-name>

Invokes the Examination Agent to:

• Use the /ee-files hook to discover all .ee. files in the codebase
• Perform deep analysis of the specified feature
• Identify which .ee. files are related to the feature for removal
• Generate generalized documentation (FEATURE_SPEC.md)
• Remove all .ee. files for the feature
• Delete the FILES_TO_REMOVE.md file

Output: Documentation files in compliance-work/<feature-name>/

/compliance implement <feature-name>

Invokes the Implementation Agent to:

• Read the generated FEATURE_SPEC.md
• Implement the feature from documentation
• Build and validate

Prerequisite: Run examine first and verify documentation manually.

/compliance full <feature-name>

Runs the complete workflow:

1. Examine and document
2. Automated validation - Claude analyzes outputs to verify:
   • Documentation is complete and implementation-ready
   • No proprietary code/names are included
   • All .ee. files are identified
   • Only pauses for human review if issues are detected
3. Remove .ee. files
4. Read the documentation
5. Implement from documentation
6. Build and validate

---

Workflow Overview

┌────────────────────────────────────────────────────────────────┐
│                     COMPLIANCE WORKFLOW                        │
├────────────────────────────────────────────────────────────────┤
│                                                                │
│  ┌──────────────────┐      ┌──────────────────────────────┐    │
│  │ EXAMINATION      │      │ Output:                      │    │
│  │ AGENT            │─────▶│ - FEATURE_SPEC.md            │    │
│  │                  │      │ - ANALYSIS_NOTES.md          │    │
│  │ Uses /ee-files   │      │ - Remove the .ee. files      │    │
│  │ hook to discover │      │                              │    │
│  └──────────────────┘      └──────────────────────────────┘    │
│           │                                                    │
│           ▼                                                    │
│  ┌────────────────────┐                                        │
│  │ AUTOMATED          │  ◀── Claude validates documentation    │
│  │ VALIDATION         │      meets all requirements            │
│  │                    │                                        │
│  │ *Only* pauses if   │  ◀── Issues? → Human review            │
│  │ issues detected    │      No issues? → Continue             │
│  └────────────────────┘                                        │
│           │                                                    │
│           ▼                                                    │
│  ┌──────────────────┐      ┌──────────────────────────────┐    │
│  │ IMPLEMENTATION   │      │ Actions:                     │    │
│  │ AGENT            │─────▶│ - Implements from spec       |    |
|  |                  |      | - Builds & validates         │    │
│  │                  │      │                              │    │
│  │ Fresh session    │      └──────────────────────────────┘    │
│  └──────────────────┘                                          │
│           │                                                    │
│           ▼                                                    │
│  ┌──────────────────┐                                          │
│  │ MERGE REQUEST    │  ◀── Create MR, get team review          │
│  └──────────────────┘                                          │
│                                                                │
└────────────────────────────────────────────────────────────────┘

---

Automated Validation Criteria

During the full command, Claude automatically validates that the examination output:

1. Completeness - FEATURE_SPEC.md contains all necessary sections for implementation
2. No Proprietary Content - Documentation does not contain:
   • Original function/variable names from source
   • Direct code snippets
   • Exact API routes or database schemas
3. Implementation Readiness - Spec is detailed enough to implement without referencing original code

If validation passes: Proceeds automatically to implementation phase.

If issues detected: Claude stops and reports specific concerns to the human for review.

---

Working Directory Structure

When running compliance tasks, files are organized as:

compliance-work/
└── <feature-name>/
    ├── FEATURE_SPEC.md      # Generalized documentation
    ├── ANALYSIS_NOTES.md    # Additional observations
    └── IMPLEMENTATION.md    # Post-implementation notes

---

Critical Rules

Commands to NOT use:

• Any git commands to find file history. Will create non-cleanroom results.

Documentation Must NOT Contain:

• Original function names
• Original variable names
• Original logic
• Original file paths
• Direct code snippets
• Exact API route strings
• Database table/column names verbatim
• Original comments

Implementation Must NOT Include:

• License checks
• Original function names
• Original variable names
• Original logic
• Exact API route strings
• Database table/column names verbatim
• Original comments
• Enterprise feature flags
• "Upgrade to enterprise" prompts
• Any .ee. in file names

Process Requirements:

• Automated validation of documentation is performed by Claude
• Human review only required if Claude detects issues or is uncertain
• Implementation agent must run in a fresh session
• Build must succeed before marking complete
• Feature must work identically (minus enterprise gates)

---

Quick Reference

Phase	Agent	Input	Output
Examine	Examination	Feature name	FEATURE_SPEC.md
Validate	Claude	Documentation	Auto-approval or issues
Review	Human (if needed)	Issues report	Approval
Implement	Implementation	FEATURE_SPEC.md	Working feature
Final Check	Human	Running app	MR approval

---

Hooks

/ee-files

Lists all .ee. (enterprise edition) files in the n8n codebase. The examination agent uses this hook as the starting point to discover enterprise-gated code, then filters to identify files relevant to the specific feature being analyzed.

---

Enterprise Features Reference

Check packages/@n8n/constants/src/index.ts for the list of enterprise-gated features.