lfe-complexity-checklisted

# LFE Complexity Check — Prompt-Based Complexity Analysis ## Position in Pipeline - **Phase**: 3 (Inspector sub-skill) - **Persona**: Inspector (read-only; no src/ writes) - **Trigger**: Invoked by `/lfe-inspector` Sub-Skill Dispatch when `lfe-complexity-check: true` in `.docs/quality/inspector-config.md` - **Output**: `.plans/checks/complexity_findings.md` — aggregated by Inspector into `critique.md` ## Mission Reason over changed code to identify complexity indicators that reduce maintainability. The goal is not to enforce arbitrary metrics but to surface patterns that will make future AI sessions harder to navigate and extend correctly. ## Hard Rules 0. **Dispatch Context Required (refuse direct invocation)**: This skill is dispatched by `/lfe-inspector` Step 6 — it is not a Brain-typeable skill (per `LLM_AGENT_GUIDE.md` §8.8 Skill Invocation Authority). If invoked without `.plans/builder_done.md` for the current slice, halt immediately and reply: *"`/lfe-complexity-check` is an Inspector sub-skill dispatched by `/lfe-inspector`. It cannot be run standalone. Run `/lfe-inspector` — the dispatcher will invoke this sub-skill if it is enabled in `.docs/quality/inspector-config.md` (or via an `## Inspector Overrides` section in `active_plan.md`)."* Direct invocation produces orphaned findings files and breaks the Inspector's aggregation logic. 1. **Prompt-Only**: Reason over the diff only — no linters or complexity calculators. 2. **Diff-Scoped**: Analyse only files listed i