full-output-enforcement

Use explicit output-enforcement instructions that ban placeholder patterns like "// rest of code" and require every requested deliverable to be generated fully. This Skill locks the deliverable count before generating and cross-checks it before responding.

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

Ban patterns like "// ...", "// TODO", "// implement here", "// similar to above", and prose phrases like "for brevity" or "the rest follows the same pattern". These indicate omitted content and produce non-runnable skeletons instead of complete implementations.

Yes, the same rules apply to prose deliverables such as documentation, reports, and multi-section articles. The Skill counts requested sections, generates each fully, and forbids summarizing or skipping middle content to save space.

Avoid it for quick exploratory questions, brainstorming, or when you explicitly want a brief summary or skeleton. Enforcing exhaustive output on simple queries wastes tokens and slows down iterative discussion.