Shape First. Then Plan.

Skip the shaping conversation and you'll build the wrong thing faster.

Brian Casel · April 10, 2026

Every major coding tool now has plan mode. Claude Code, Cursor, Codex — they've all converged on the same pattern. You describe what you want, the AI asks clarifying questions, and out pops an implementation plan.

But most of us are skipping the step that should come first.

Plan mode is the what and how. Before that, you need the why and whether. That's the shaping conversation.

Shaping isn't about figuring out the technical approach. It's about getting clear on the problem you're actually solving — before you start solving it. Here's the process:

Start with a brain dump. Raw idea, no polish. Voice dictation works great here. "Users are spending too much time context-switching between email and our app. I want to surface unread messages right in the dashboard." That's it. Get it out of your head.

Add real customer context. Not assumptions — actual words. "Sarah said she'd switch tools if she didn't have to alt-tab. Tom uses the app on his phone during meetings and can't check email there." Real constraints, real problems.

Describe what exists and where it breaks. "Our notification system just pings — no history, no summary. Competitors have email integration but it's slow and bloated." Locate the real gap, not the imagined one.

Ask the AI to push back. This is where most people miss the opportunity. Don't let the AI be a yes-machine. Ask: "What could go wrong? Where am I oversimplifying? What problem am I actually solving here?" The AI shifts from tool to collaborator.

Capture the output. The result isn't a technical spec. It's clarity — a problem statement with teeth, scope boundaries, key decisions with rationale, and core user flows. That's your PRD.

Then — and only then — open plan mode. Now you know you're building the right thing.

The process at a glance:

  1. Brain dump your raw idea
  2. Add real customer context and actual words
  3. Map what exists today and where it breaks
  4. Ask the AI to challenge your assumptions
  5. Capture: problem statement, scope, key decisions, user flows
  6. Now open plan mode

Keep building.

Brian Casel

Brian Casel

Creator of Builder Methods

Product designer, teacher, and creator of tools and training here at Builder Methods.

Builder Methods

Training and community for developers and founders building with AI.

Created by Brian Casel (that's me) — multi-time founder, product designer, teacher, and the creator behind Builder Methods.

© 2026 CasJam Media, LLC / Builder Methods