full-output-enforcement

Use explicit anti-truncation rules that ban placeholder patterns like "// rest of code" and require every requested deliverable to be completed. This Skill enforces a scope-build-cross-check process so nothing is skipped or shortened.

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. On "continue", resume exactly from that point without recap or repetition.

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 count as hard failures.

Yes, the same rules apply to prose and structured documents. The deliverable counting and cross-check steps ensure every requested section or answer is present and finished, regardless of content type.

Avoid it for quick exploratory questions, brainstorming, or when a short summary is explicitly wanted. The enforcement optimizes for completeness, which adds length that is unnecessary for simple lookups.