full-output-enforcement

Use explicit anti-truncation instructions that ban placeholder patterns like "// rest of code" and require every requested deliverable to be generated in full. This skill enforces that behavior with a scope-count and cross-check process before responding.

Instead of compressing remaining content, pause at a clean breakpoint such as the end of a function or file, emit a resumable marker like "[PAUSED — X of Y complete]", and continue exactly from that point when the user replies "continue".

Ban patterns like "// ...", "// TODO", "// implement here", "// similar to above", and prose such as "for brevity" or "the rest follows the same pattern". These indicate omitted content and produce non-runnable code.

Yes, it is a prompt-level instruction set with no code dependencies, so it applies to any LLM that accepts system or skill instructions. It changes generation behavior rather than integrating with a specific API.

Avoid it for exploratory brainstorming, quick prototypes, or when the user explicitly asks for a sketch or outline. Enforcing exhaustive output in those cases wastes tokens and slows iteration.