Developer shares workflow of writing specs first before using Claude Code

On November 13, 2026, at 09:05, a developer published a write-up in the AI section of DEV Community describing a workflow built around Claude and Claude Code. Instead of asking an AI tool to build a product directly, the developer first has Claude help write five short specification documents through an question-and-answer process, and only then hands those specifications to Claude Code to generate the code, using the setup to build an e-commerce MVP.

The example project in the post uses an Angular front end together with an ASP.NET Core back end, but the author stresses that the approach is not tied to that stack and can be applied with any technology stack. As for why output so often drifts from what the user pictured, the author argues that the problem is not the AI itself. Rather, it comes from leaving hundreds of decisions open and letting the AI guess at them. For that reason, he changed the order of the process, defining specifications before requesting code instead of asking for code first.

The available reporting covers only this single share of the workflow, and no further developments, follow-up posts, or community responses are documented in the material. The description therefore stops at the point where the developer has presented the method and its reasoning, with no additional milestones to report. This overview is drawn strictly from that one source.