full-output-enforcement

Apply explicit output-enforcement instructions 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 it before responding.

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

Ban "// ...", "// 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 patterns indicate omitted content and produce broken deliverables.

Models optimize for brevity by default and compress or drop deliverables when output grows long. Scope locking, which counts expected deliverables upfront and re-verifies before responding, prevents silent omissions.

Avoid it for quick exploratory questions, short snippets, or brainstorming where brevity is appropriate. It is designed for tasks explicitly requiring exhaustive output, such as complete implementations or full document drafts.