Menú
Give a high-level system map when encountering unfamiliar code. Use in the Inspector sub-pipeline as Step 1 before verification.
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
Act as the Archivist for an LFE-compliant project. Use when a change is approved and needs documentation sync, changelog updates, or pipeline status cleanup.
Act as the Architect for an LFE-compliant project. Design solutions and draft high-fidelity plans.
Act as the Builder for an LFE-compliant project. Use when implementing an approved plan, writing code in src/**, or running unit tests.
Inspector sub-skill. Analyses changed code for cyclomatic complexity, excessive nesting, oversized functions, and cognitive load indicators. Pure LLM reasoning — no external tooling. Writes .plans/checks/complexity_findings.md. Called by lfe-inspector when enabled in inspector-config.md.
Inspector sub-skill. Reviews dependency manifest files (package.json, requirements.txt, go.mod, Cargo.toml, pom.xml) changed in the current diff for risky version patterns and stale majors. Emits a human-run audit instruction rather than executing tools. Writes .plans/checks/dep_findings.md. Called by lfe-inspector when enabled in inspector-config.md.
Disciplined bug-diagnosis loop. Reproduce → Hypothesise → Fix. Use in the Inspector sub-pipeline (Step 3, conditional) when verification fails.
| name | lfe-zoom-out |
| description | Give a high-level system map when encountering unfamiliar code. Use in the Inspector sub-pipeline as Step 1 before verification. |
| disable-model-invocation | false |
Treat this area of code as unfamiliar. Go up a layer of abstraction. Give me a map of all the relevant modules and callers, using the project's domain glossary vocabulary from CONTEXT.md.
Focus on:
