full-output-enforcement

Apply explicit output-enforcement rules that ban placeholder patterns like "// rest of code" and require every requested deliverable to be generated in full. This Skill locks the deliverable count before generating and cross-checks the output against it.

Write at full quality up to a clean breakpoint such as the end of a function or file, then emit a pause marker stating progress, for example "[PAUSED — 3 of 5 complete]". On "continue", resume exactly from the named next section without recap or repetition.

Banned patterns include "// ...", "// TODO", "// implement here", "// similar to above", bare ellipses standing in for code, and prose like "for brevity" or "the rest follows the same pattern". These indicate omitted content and count as hard failures.

Yes, the rules apply to any exhaustive output, including prose and structured documents. It bans structural shortcuts such as skipping middle sections, replacing repeated content with one example, or describing content instead of writing it.

Avoid it for exploratory questions, quick prototypes, or when a concise summary is genuinely what you want. The enforcement treats every task as production-critical and optimizes for completeness over brevity, which adds length to simple answers.