full-output-enforcement

Enforces complete code generation by banning placeholder patterns and truncation.

Updated Jul 1, 2026
One-click install
npx skills add https://github.com/w0lzard/Wolzard-s-Marketplace --skill full-output-enforcement-w0lzard
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: full-output-enforcement
Source: https://github.com/w0lzard/Wolzard-s-Marketplace/tree/main/plugins/personal-skills/skills/full-output-enforcement
Command: npx skills add https://github.com/w0lzard/Wolzard-s-Marketplace --skill full-output-enforcement-w0lzard

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? LLMs often truncate long outputs, insert placeholder comments like "// rest of code", or skip deliverables to save tokens. This Skill overrides that default behavior so every requested file, function, or section is delivered in full. ## Core Features & Use Cases - Placeholder Ban: Hard-fails on patterns like // ..., // TODO, "for brevity", and skeleton-only outputs. - Scope Locking: Counts expected deliverables before generating and cross-checks them before responding. - Token-Limit Handling: Pauses at clean breakpoints with a resumable [PAUSED — X of Y complete] marker instead of compressing content. - Use Case: When asking an AI to generate five complete React components or a full configuration file, this Skill ensures all five arrive fully implemented with no omitted sections. ## Quick Start Apply the full-output-enforcement skill and generate the complete implementation of all requested files with no placeholders or omissions.

Frequently Asked Questions about full-output-enforcement

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I stop an AI from truncating code output?

Use explicit anti-truncation rules that ban placeholder patterns like "// rest of code" and "for brevity". This Skill locks the deliverable count upfront, cross-checks completeness before responding, and pauses at clean breakpoints instead of compressing content.

How to handle token limits during long code generation?

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

What placeholder patterns indicate incomplete AI-generated code?

Common signs include "// ...", "// implement here", "// TODO", "// similar to above", and prose like "the rest follows the same pattern". Skeleton outputs showing only first and last sections also signal incomplete generation.

When should I not use full-output enforcement?

Avoid it for exploratory brainstorming, quick prototypes, or when you explicitly want a summary or skeleton. Forcing exhaustive output on open-ended questions wastes tokens and slows iteration on early-stage ideas.