Claude Code Ultraplan Launched: I Just Tested It (And It’s Better Than It Looks)

Source: Joe Njenga, Claude Code Ultraplan Launched: I Just Tested It (Medium, 2026-04-04)

Key takeaways

  • /ultraplan is Claude Code’s built-in planning mode.
  • Njenga’s verdict: “Better than it looks” — tested and found genuinely useful, not a marketing feature.
  • Complements /ultrareview (shipped with Opus 4.7) — plan first with /ultraplan, review before merge with /ultrareview.
  • Fits the broader “effort as a dial” pattern (see Opus 4.7 Reference) where reasoning depth is now a per-task choice.

What /ultraplan does

Claude Code spins up a dedicated planning session — reads your request, drafts an implementation plan, surfaces assumptions, and lets you iterate on the plan before any code is written. Distinct from just “thinking more” in a regular session because it produces a structured plan artefact you can review, edit, or reject entirely.

Njenga’s test

His overall verdict: “Better than it looks.” Initially skeptical, found that for non-trivial work the planning step produced materially better output than jumping straight to implementation.

Where it fits

A spectrum of intentional-slowdown patterns in Claude Code:

Intent Command
Plan before implementation /ultraplan
Review before merge /ultrareview (shipped with Opus 4.7)
Interactive learn-the-tool /powerup
Autonomous sprint execution /bad (via npx skills add)

Each lets you dial how much thinking Claude Code does for a given task.

When to use it

  • Multi-file features where sequencing matters
  • Refactors that touch multiple subsystems
  • Anything where getting the wrong approach wastes more time than the planning cost
  • Pair with Hightower’s commitment-device pattern (see Prompt Discipline) — stated plans are committed plans

Built by Force Information Systems · Harris Computer · Constellation Software. Licensed under MIT.