full-output-enforcement

Enforces complete code generation by banning placeholder patterns and truncation.

Updated Apr 15, 2026

Search Tags:#code generation #token limit #llm prompting #anti-truncation #placeholder ban #deliverable verification #complete output

One-click install

npx skills add https://github.com/joaopaulotr/PesquiseMaisHealth --skill full-output-enforcement-joaopaulotr

Or copy as Structured Prompt for Agent▼

Please help me install this Agent Skill.
Skill: full-output-enforcement
Source: https://github.com/joaopaulotr/PesquiseMaisHealth/tree/main/.agents/skills/full-output-enforcement
Command: npx skills add https://github.com/joaopaulotr/PesquiseMaisHealth --skill full-output-enforcement-joaopaulotr

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, leaving users with incomplete code that requires manual follow-up. This Skill overrides that default behavior so every requested deliverable is generated in full. ## Core Features & Use Cases - Placeholder Ban: Hard-fails on patterns like "// ...", "// TODO", "for brevity", and "the rest follows the same pattern" in both code and prose. - Scope Locking and Cross-Check: Counts expected deliverables before generating, then verifies the count before responding so nothing is omitted. - Token-Limit Handling: Splits long outputs at clean breakpoints with a structured [PAUSED] marker and resumes exactly where it stopped on "continue". - Use Case: Ask for a full multi-file project scaffold or five complete React components, and receive every file and component fully implemented without skeletons or "extend this later" shortcuts. ## 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 LLM 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, generates every item fully, and cross-checks completeness before responding.

How to handle token limits when generating long code files?▼

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.

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" or "and so on". This Skill treats all of these as hard failures that must never appear in output.

When should I not use full-output enforcement?▼

Avoid it for quick exploratory questions, short snippets, or brainstorming where brevity is appropriate. It is designed for tasks explicitly requiring exhaustive deliverables, such as complete files or a fixed number of components.