full-output-enforcement

Apply explicit output-enforcement instructions that ban placeholder patterns like "// rest of code" and require every requested deliverable to be generated completely. This Skill defines a banned-pattern list and a pre-response cross-check to guarantee completeness.

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 without recap or repetition.

Ban inline omissions like "// ...", "// TODO", "// implement here", and prose shortcuts like "for brevity" or "the rest follows the same pattern". Also ban structural shortcuts such as skeleton-only output or describing code instead of writing it.

Yes, the same scope-build-crosscheck process applies to any enumerated deliverables such as documents, sections, or answers. The deliverable count is locked before generation and verified before responding.

Avoid it for exploratory brainstorming or quick drafts where brevity is the goal, since it treats every task as production-critical and optimizes for completeness over conciseness. It is designed for tasks explicitly requiring exhaustive output.