full-output-enforcement

Enforces complete code generation by banning placeholder patterns and truncation.

Updated Jun 9, 2026
One-click install
npx skills add https://github.com/timikalo7/Execute --skill full-output-enforcement-timikalo7
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: full-output-enforcement
Source: https://github.com/timikalo7/Execute/tree/main/.claude/skills/output-skill
Command: npx skills add https://github.com/timikalo7/Execute --skill full-output-enforcement-timikalo7

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 back-and-forth. 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 skeleton-only outputs, forcing real runnable code. - Scope Locking: Counts the requested deliverables up front and cross-checks the final output against that count before responding. - Token-Limit Handling: When output approaches the token limit, it pauses at a clean breakpoint with a resume marker instead of compressing or skipping content. - Use Case: Ask for a full multi-file project scaffold or five complete React components, and receive every file and component fully implemented without "continue?" interruptions 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 output enforcement rules that ban placeholder patterns like "// rest of code" and require every requested deliverable to be generated in full. The skill counts expected deliverables up front and cross-checks the response before finalizing.

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 end with a pause marker stating progress. On "continue", resume exactly where you stopped without recap or repetition.

What placeholder patterns should be banned in AI code generation?

Ban patterns like "// ...", "// TODO", "// implement here", "for brevity", "the rest follows the same pattern", and bare ellipses standing in for omitted code. These indicate incomplete output that fails the request.

When should I not use full-output enforcement?

Avoid it for exploratory brainstorming, quick prototypes, or when you explicitly want a short sketch or outline. The enforcement treats every task as production-critical, which adds length even when brevity is preferred.