do-integration-auditlisted

# Feature Integration Audit Audits how thoroughly a named feature is wired into its host project. A feature can exist in a codebase without being truly integrated — code is present but unreachable, tests exist but don't exercise real paths, documentation mentions it but entry points are missing. This audit finds the gaps between "code exists" and "feature works end-to-end." Takes a feature topic as its argument and maps every integration surface: entry points, imports, tests, docs, config, and error handling. Produces a severity-grouped findings report and pauses for human review. ## What this skill does 1. Discovers all code, config, docs, and tests related to the given feature topic 2. Maps the feature's integration surfaces: how it's entered, imported, configured, tested, and documented 3. Runs 12 semantic checks against each integration surface 4. Produces a structured findings report organized by severity (CRITICAL, WARNING, INFO) 5. Pauses for discussion — no auto-fix, findings only ## 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,