I chat with Claude about viability, capability, existing solutions, alternative approaches, etc.

This helps me get an idea of what we’re doing. I get pushback and have to be clear and Opus is good at asking questions.

Then I get it to write a set of documents for Claude Code describing the vision, the solution, the technical choices, the testing plan, the validation approach, how to share with colleagues, future ideas and a table of contents.

I tried both ways. Letting design emerge incrementally adds vibe-coded technical debt.

At minimum prepare project specs with features as .md file. I found claude to be useful for this task.

If you’re using Cursor, pick a template from here. https://cursor.directory/rules