T he document under review, posted to the Reddit forum r/ChatGPT under the imperative title "Review This Prompt And Feedback it," is a template—that is to say, a form letter addressed not to any human correspondent but to a large language model, instructing it to produce, upon the mere filling-in of bracketed fields, a complete and functional software system. The author, whose identity is immaterial and whose sincerity we do not question, presents this instrument to his fellow enthusiasts in the manner of a man circulating a draft memorandum at the office. One is invited to "feedback" it—the verb deployed here in its transitive sense, a usage that has no provenance in English prose but considerable provenance in machine output, where parts of speech are treated less as grammatical categories than as suggestions.

Let us attend to the specimen itself. It opens with a section headed ROLE, in which the operator is instructed to inform the machine that it is "an expert [e.g. full-stack developer / product designer / ML engineer] with deep experience in [tech stack / domain]." The brackets are load-bearing voids. Remove them and you are left with the sentence "You are an expert with deep experience in," which is not a sentence at all but a promissory note drawn on an empty account. The template then proceeds through PROJECT, GOAL, STACK, FEATURES, CONSTRAINTS, and DELIVER—section headings that reproduce, with the fidelity of a well-trained parrot, the silhouette of a professional software brief whilst containing none of its substance.

What is remarkable is not the ambition, which is considerable—one is asked to believe that a statistical model will produce "a complete, working, production-ready" application that is "immediately usable—not a skeleton, not a mockup"—but the specificity of the absence. Every concrete detail has been excised and replaced with a bracketed placeholder. The project name is "[Project name]." The one-liner describing what the software does is "[What it does in one sentence]." We are presented, in short, with the Platonic form of a requirements document: one from which all requirements have been carefully removed, leaving only the apparatus of requirement-having.

The double-curly-brace notations are worth a moment's scrutiny. The features section distinguishes between "Must have {{(MVP)}}" and "Nice to have {{(if scope allows)}}," a convention recognizable to anyone who has worked with templating engines—Handlebars, Mustache, Jinja—where such syntax denotes variables to be replaced at render time. That this notation appears in a document intended for manual completion by a human being suggests either that the author has chosen the syntax as an aesthetic preference, or—and one must weigh the probabilities here with care—that the document was itself produced by a system accustomed to emitting such syntax, and the author did not recognise the fingerprint for what it was.

This is the ouroboric condition that the specimen so elegantly, if inadvertently, illustrates. A machine has, in all probability, generated a template. A human has received it and, finding it impressive in its apparent thoroughness, has posted it for review. Other humans will annotate it, their annotations will be fed back to machines, and the refined template will be used to instruct machines to produce software that the original human will then attempt to deploy. At no point in this cycle does anyone execute code, test an application, or verify that the output corresponds to reality. The entire economy is one of text producing text producing text, each generation more confident in its formatting and less anchored to any material outcome.

The DELIVER and OUTPUT RULES sections are particularly instructive. "Write every file in full—no truncation, no '...rest of code here,'" the template demands, addressing a known tendency of language models to elide the middle portions of long outputs. "Don't explain basics. I know how to code. Be concise where it's obvious." The instruction "I know how to code" is not information the model can use. It is a spell, an incantation, a rhetorical gesture directed at a process that parses tokens—the equivalent of informing one's typewriter that one has a doctorate.

The phrase "zero hand-holding needed" deserves particular attention, as it is the template's most revealing confession. It means, translated from the managerial register into plain English: produce the entire thing yourself, because I will not be intervening. This is not a collaboration. It is a delegation—of architecture, of implementation, of judgement—to a system that possesses none of these capacities but is exceedingly fluent in mimicking their outputs. The template, in its comprehensive emptiness, is less a tool for producing software than a monument to the belief that the correct arrangement of imperatives, addressed to a sufficiently advanced autocomplete, will yield the thing itself rather than merely the shape of the thing.

What we have, then, is not slop in any simple sense but something more structurally interesting: a cargo-cult engineering document, one that has internalised every formal convention of professional software specification whilst retaining no actual specification whatsoever. It is all scaffold and no building, all frame and no canvas. And the author, admirably, wishes to improve it—to refine, through collective human effort, a machine-generated instrument for extracting machine-generated artefacts, in the evident conviction that the perfection of the form will eventually produce the substance. It is the literary equivalent of polishing a mirror in a dark room and wondering why one cannot see one's reflection.