lfe-plan-critiquelisted

# LFE Plan Critique — Pre-Build 5-Lens Review ## Position in Pipeline - **Phase**: 1.5 (between Architect plan approval and Builder start) - **Persona**: Architect (read-only — no src/ write access) - **Trigger**: Automatically after Brain approves `active_plan.md` — before `/lfe-builder` is invoked - **Next Step**: `/lfe-builder` (on PASS) or `/lfe-architect` revision loop (on BLOCK) ## Mission Stress-test the approved plan from five angles before a single line of code is written. Catch ambiguous acceptance criteria, untestable requirements, domain boundary violations, structural impact, and cross-edit incoherence before they become bugs in `src/`. Lenses 1–4 are human/LLM judgment; a mechanical **plan-linter** pass (Step 1.5) feeds objective findings into Lens 2 (glob reach) and Lens 5 (coherence) so the judgment lenses reason over verified facts, not guesses — because honor-system "remember to check" instructions get skipped (the lesson behind `checkpoint-flip.mjs`). ## Hard Rules 1. **Zero Code Writes**: This skill operates on `.plans/` and `.docs/` only — `src/` stays untouched. 2. **5-Lens Sequential**: Run all five lenses in order, every time — even when an earlier lens passed cleanly. Run the mechanical plan-linter (Step 1.5) before the lenses so Lens 2 and Lens 5 consume its findings. 3. **Single Output File**: All findings aggregate into one `plan_critique.md` — no per-lens files. 4. **Verdict is Decisive**: A single BLOCK finding stops the Builder. WARN requires