DeepSeek-V4.1-Flash: Breaking Down Ice Cream App Requirements with a Markdown Specification Document

One-sentence takeaway

First have the model turn the requirements into one or more Markdown specification documents, then use those documents to drive implementation; the prompt asks the model to cover target customers, regions, parameters, technical scope, and roles, and to ask clarifying questions first. This is community experience, not a controlled test.

Use cases

• Suitable tasks: Product requirements decomposition, front-end/back-end/database architecture, or multi-page demo specifications in plain HTML, CSS, and JS.

• Unsuitable tasks: Tasks requiring verified code artifacts, performance data, cost data, or standardized API parameters.

• Applicable model version: The comment author explicitly wrote DS4.1f; this item is archived as DeepSeek-V4.1-Flash.

• Applicable client, agent, or API: The author later explicitly mentioned Claude Code Desktop and Cline Desktop; they did not state which client this prompt is fixed to run in.

• Recommended reasoning tier and parameters: Not specified.

Ready-to-use content

The following is the complete ice cream app specification prompt from the comment, with the original X, Y, and Z placeholders preserved:

hey, I want to build an ice cream app that serves ice cream the X type of customer, in Y areas, with Z parameters, and I want you to write me a tight specification (spec) as a markdown file or markdown files of what that would look like in detail. Please include (front-end, back-end, database integrations, etc. OR just a multi-page demo in plain html, css, and js), and ask me any clarifying questions you can think of so that we can get a spec that's exactly what customers, front-of-house, admin, business operators, and any other user roles/work roles may need in order to make the most of this application.

Testing or workflow steps

1. Replace X, Y, and Z with the customer type, service area, and business parameters, and add the application's objective.

2. Give the prompt to the model and ask it to produce one or more Markdown specification documents; choose a complete technical solution or a multi-page demo solution according to the requirements.

3. Answer the clarifying questions raised by the model and iterate on the specification until the needs of customers, front-of-house staff, administrators, operators, and other roles are clear enough.

4. Use the specification files as the basis for subsequent build tasks, or give them to other models to continue implementation. The comment also claimed that build mode produces a more detailed plan and can split it into multiple files for sub-agents to parse; this claim was not independently verified.

Original evidence and data

• Wrong_Visual5077 first suggested: “Have it write its own spec in markdown instead of planning mode before building.”

• The same comment said: “I went from burning usage on Claude to DS4.1f and it just runs.” This is a personal experience and cannot be treated as a performance conclusion.

• The complete prompt mentioned in the replies asks for a Markdown file or file series covering front-end, back-end, and database integrations, or a multi-page demo in plain HTML/CSS/JS, and asks about all relevant work roles.

• The author explicitly said that the model would then ask clarifying questions and produce specification documents, which could subsequently serve as the working specification for an actual build.

Scope and limitations

The comment provides no model outputs, code, success rate, elapsed time, token usage, or API parameters; it therefore cannot guarantee that DeepSeek-V4.1-Flash will automatically generate an executable solution for any project. X, Y, and Z are placeholders from the original text and must be replaced with real constraints when used. The environment information for Claude Code Desktop and Cline Desktop comes from later replies; it cannot be used to infer a dedicated integration or default client behavior for this prompt.

Reproduction notes

On 2026-09-16, the Reddit original post was accessed directly through Tabbit, including the post, Wrong_Visual5077's main comment, and the complete reply about the ice cream app; no search snippets were used, the prompt was not run, and the commenter's personal assessment was not rewritten as a test result.