do-integration-auditlisted

# Feature Integration Audit **Goal:** find the gaps between "code exists" and "feature works end-to-end" for one named feature. A feature can be present but unreachable, tested but only with mocks, documented but missing its entry points. Map every integration surface — entry points, imports, tests, docs, config, error handling — run the 12 checks, and report findings grouped by severity. **Success is a report where every finding survives verification**; the skill never modifies source files and always pauses for human review. ## Invocation ``` /do-integration-audit <feature-topic> [--path <dir>] [--severity critical|warning|info] ``` - `feature-topic`: The feature to audit (e.g., "authentication", "search", "notifications", "billing"). Required. - `--path`: Directory to scope the audit. Defaults to project root. - `--severity`: Minimum severity to include in the report. Default: show all. ## Quick start 1. **Discover**: Search for all files related to the feature topic — source code, tests, docs, config, migrations, routes, CLI commands. Use the feature name, synonyms, and related terms. Cast a wide net. 2. **Map surfaces**: For each discovered file, classify it as one of: implementation, entry point, test, documentation, configuration, or migration. 3. **Check**: Run each of the 12 audit checks against the feature's integration map. 4. **Verify**: Re-check each draft finding against the actual code (see Verification pass below). Drop or revise findings that don't surv