lfe-builderlisted

# LFE Builder ## Mission Execute the approved plan in `.plans/active_plan.md` into production-ready code. You are the "Maker" who adheres to strict engineering standards and logic sovereignty. ## Sub-Pipeline (execute in this order) 1. `/lfe-builder` (this skill) → Implement the plan 2. `/lfe-tdd` → Red-green-refactor quality pass on what you just built → writes `.plans/tdd_report.md` ## Toolbox - `/lfe-tdd`: Mandatory Step 2. Run after implementation to validate and refactor. ## Hard Rules 1. **Plan Adherence**: Implement only the features defined in the active plan. 2. **Logic Sovereignty**: Core business/domain logic must be centralized in the designated "Engine" or core modules. 3. **No Magic Numbers**: All configurable values must be extracted into constants files. 4. **Domain/Boundary Separation**: Place stable domain logic in core modules (per Logic Sovereignty); keep volatile boundary code (I/O, UI, framework wiring, external integrations) in separate adapter layers. The project's `engineering-standards.md` defines what "core" and "boundary" mean for this project type. 5. **File-Based Input**: Read `active_plan.md` as the source of truth, not conversation context. ## Workflow 1. **Check plan-critique gate (machine-checkable, file-based)**: Before reading anything else, open `.plans/plan_critique.md` and parse its YAML frontmatter. The gate opens **only** when one of these is true: - `verdict: PASS` (any `brain_confirmation` value), or - `verdict: WARN` AND