Roberto Bortolaso
Claude Code Plugin

Engineering discipline, enforced by hooks.

Look Before You Leap for Claude Code turns planning, verification, and skill routing into an operating layer. It makes Claude stop improvising and start working like a careful engineer.

Install pluginView README
11Enforcement hooks that block sloppy behavior at the tool-call level.
3-layerConductor, checklists, and deep guides — loaded progressively to save context.
OrbitPlan review workflow so non-trivial work gets approved before edits begin.
Why it exists

Built against the failure modes that make coding agents expensive.

Failure mode

Scope drift

Rules that make silent scope cuts explicit and unacceptable. Ask for 5, get 5 — or hear why not.

Failure mode

Blind edits

Mandatory exploration, consumer checks, and blast-radius review before touching shared code.

Failure mode

Context loss

Plans written to disk and updated every 2-3 edits so work survives compaction intact.

Failure mode

Weak verification

Completion means typecheck, lint, tests, and the relevant discipline checks are actually run.

Conductor layer

Route the task to the right discipline.

The conductor decides when work needs planning, frontend design, TDD, systematic debugging, refactoring, or skill creation — then forces the right sequence.

Plan integrity

Make compaction survivable by default.

Persistent plans are not optional. They live in the repo, become the execution source of truth, and are updated often enough that a fresh context window can resume cleanly.

Hook enforcement

Block sloppy behavior at the tool-call level.

PreToolUse hooks block code edits without a plan. PostToolUse hooks remind checkpointing. Stop hooks prevent abandoning unfinished work. No workarounds, no bypasses.

Skill pack

Disciplines, not a generic prompt bundle.

Core operating layer

Conductor + engineering discipline

The default rails for coding work. They enforce exploration, blast-radius checks, no type shortcuts, and explicit verification.

  • Conductor orchestrates the workflow
  • Engineering discipline governs how edits are made
  • Persistent plans keep progress recoverable on disk
Behavior change layer

Debugging, TDD, refactoring

When the task becomes specific, the system routes to a narrower discipline rather than relying on vague best-effort behavior.

  • Systematic debugging requires root-cause work before fixes
  • Test-driven development enforces red/green rhythm
  • Refactoring protects cross-file structural changes
Interface layer

Frontend and skill authoring

Creative and meta-disciplines for building polished interfaces and authoring new reusable skills.

  • Frontend design prevents generic UI output
  • Immersive frontend handles motion-heavy surfaces
  • Skill creator improves or ships new skills
Workflow

A session rhythm that makes the agent legible.

The plugin turns the session into a sequence that can be inspected: explore first, write the plan, execute with the right disciplines, then verify.

1. Discover the real shape of the taskRead files, imports, consumers, adjacent patterns, and conventions before implementation begins.
2. Freeze intent in plan.json and masterPlan.mdPersist what will be built, how it will be verified, and where the risk lives.
3. Execute with routed skillsCall the right specialty: frontend design, debugging, TDD, refactoring, or skill creation.
4. Finish only after verificationTypecheck, lint, tests, and domain-specific review are part of completion, not an optional afterthought.
Install

Drop the plugin into Claude Code and make disciplined execution the default.

The plugin ships as a single installable package. Hooks activate on first session, auto-detect your stack, and create the local config.

claude plugin install look-before-you-leap@claude-control
Ships with

11 enforcement hooks, 9 specialized skills, 3-layer progressive architecture, and Orbit integration.

Built for

Teams that need the agent to behave like a senior engineer, not a fast autocomplete engine.

View on GitHub →