full-output-enforcement

Enforces complete code generation by banning placeholder patterns and truncation.

Updated Sep 17, 2026
One-click install
npx skills add https://github.com/juanjaragavi/utilities-manager --skill full-output-enforcement-juanjaragavi
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: full-output-enforcement
Source: https://github.com/juanjaragavi/utilities-manager/tree/main/.agents/skills/full-output-enforcement
Command: npx skills add https://github.com/juanjaragavi/utilities-manager --skill full-output-enforcement-juanjaragavi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? LLMs often truncate long outputs, insert placeholder comments like "// rest of code", or ask "want me to continue?" instead of delivering complete results. 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: Counts the requested deliverables before generating, then cross-checks the output against that count before responding. - Clean Token-Limit Handling: When output approaches the token limit, it stops at a clean breakpoint with a [PAUSED — X of Y complete] marker and resumes exactly 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 with no skeletons or 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 LLM from truncating code output?▼

Apply 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.

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 paused marker stating progress. On "continue", resume exactly from that point with no recap or repetition.

What placeholder patterns should be banned in AI code generation?▼

Ban patterns like "// ...", "// TODO", "// implement here", "// similar to above", and prose such as "for brevity" or "the rest follows the same pattern". These indicate omitted content and count as hard failures under this enforcement.

When should I not use full-output enforcement?▼

Avoid it for exploratory brainstorming, quick prototypes, or when you intentionally want a short sketch or outline. The enforcement treats every task as production-critical, which adds length and latency to casual requests.