full-output-enforcement

Apply output enforcement rules that ban placeholder patterns like "// rest of code" and require every requested deliverable to be generated in full. When token limits approach, the output pauses at a clean breakpoint with a resume marker instead of compressing content.

Instruct the model to treat partial output as failure and cross-check deliverable counts against the original request before responding. Banned patterns include "// implement here", "// similar to above", and prose like "for brevity" or "the rest follows the same pattern".

The output stops at a clean breakpoint such as the end of a function or file, then emits a pause marker stating progress, for example "[PAUSED — 3 of 5 complete]". Sending "continue" resumes exactly from the next section with no recap or repetition.

Yes, the same rules apply to prose deliverables such as multi-section documents or enumerated answers. The deliverable count is locked from the request, and every section must be written in full without summarizing remaining items.

Avoid it for quick exploratory questions, brainstorming, or cases where a short illustrative snippet is genuinely sufficient. Enforcing exhaustive output on simple queries wastes tokens and slows down iteration.