Every project starts with a conversation with Claude Opus inside a Project. Not a single prompt. A real, multi-turn discussion lasting 30-60 minutes. You describe your vision, Claude pushes back, asks questions, recommends tech, debates scope, maybe prototypes a layout. The quality of this conversation determines everything that follows.
This is the highest-ROI activity in your entire project.
Why Opus: The initial conversation quality is dramatically better. Opus thinks deeper about scope, challenges assumptions more effectively, and the resulting foundation documents are 10X better. Don’t start with Sonnet or Haiku for this phase — the savings aren’t worth the quality loss.
Why a Project: Claude Projects give persistent file context. You can:
This isn’t “prompt → response → done.” It’s a real discussion.
Turn 1: Describe everything
Don’t hold back. Tell Claude the full vision:
“I want to build a community platform for event professionals. They can browse open-source tools, configure them with their branding, deploy them. Plus resources, guides, video tutorials. Eventually an AI assistant that knows the platform…”
Turn 2: Claude analyzes and asks questions
Claude should:
Turn 3-5: Back and forth
This is where the real value is:
Turn 6+: Converge on decisions
Claude lays out the technology recommendations with alternatives and trade-offs. Depending on your technical level, this is more or less detailed. Topics to cover:
Claude should be recommending, not just agreeing. If Claude never pushes back on your ideas, you’re not getting the value. Push Claude to challenge you:
“Be honest — is this scope realistic for 3 weeks? What would you cut?”
Tech stack discussion should include alternatives. Not just “use React” but “here are 3 options, here’s why I’d recommend this one for your situation.”
Data architecture matters early. Discuss how entities relate. What are the main database tables? How does auth connect to the rest? This prevents painful refactoring later.
Prototype if needed. If you and Claude aren’t sure you’re imagining the same thing, ask Claude to describe or prototype a page layout. Alignment now prevents rework later.
After 30-45 minutes of conversation (using a conference toolkit as an example):
Core insight:
“The unique value is making open-source event tools accessible to non-technical organizers. The community and resources support that mission. The AI assistant is V2.”
MVP scope:
Deferred to V2:
Tech stack:
Key decisions documented:
“Everything is essential”
“We need tools AND resources AND AI assistant AND messaging or it won’t work.”
Push back: “Can we validate that organizers want the tools first? Everything else supports that core.”
“It’s not that complex”
“AI assistant is just a chatbot, how hard can it be?”
Reality check: AI assistant = ghost cursor + speech synthesis + HUD overlay + RAG knowledge base + action system = 11 tasks spanning weeks. Defer it.
“Users won’t understand without X”
“We need a full onboarding wizard or users will be lost.”
Counter: Ship with a simple questionnaire. If users are confused, that tells you what to explain. Don’t guess.
By end of brainstorming:
This becomes the foundation for your README, ARCHITECTURE.md, and sprint plan.
Don’t close this conversation yet. The next step is asking Claude to generate your foundation documents — do that in the same conversation so all the brainstorming context is available.
Using Sonnet/Haiku for brainstorming. The quality difference is significant. Use Opus for this phase. It’s worth the cost.
One prompt, one response. Brainstorming needs back-and-forth. If you got a good answer on the first try, you probably didn’t explore enough.
Not using a Project. Without persistent context, you lose the brainstorming insights when you start a new conversation.
Skipping this entirely. Starting with “build me X” instead of “let’s discuss X.” You’ll regret it at $500 in rework.
Forgetting to document. The brainstorming insights are valuable. Make sure Claude generates the foundation docs before you move on.
Next: Documentation Architecture — The documents that make everything work.