Verified:GitHub

full-output-enforcement

Enforces complete code generation by banning placeholder patterns and truncation.

1|Updated Jul 19, 2026

Search Tags:#code generation #token limit #llm behavior #placeholder ban #output completeness #truncation prevention

One-click install

npx skills add https://github.com/leobbaroni/maestro --skill full-output-enforcement-leobbaroni

Or copy as Structured Prompt for Agent▼

Please help me install this Agent Skill.
Skill: full-output-enforcement
Source: https://github.com/leobbaroni/maestro/tree/main/skills/maestro/library/taste-skill/skills/output-skill
Command: npx skills add https://github.com/leobbaroni/maestro --skill full-output-enforcement-leobbaroni

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 broken or incomplete code. 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 exact number of requested deliverables before generating, then cross-checks the output against that count. - Token-Limit Handling: When output approaches the token limit, pauses at a clean breakpoint with a resumable marker instead of compressing or skipping content. - Use Case: Ask for a full multi-file component library or a long configuration file, and receive every file completely written with runnable code rather than skeletons. ## Quick Start Apply full-output enforcement and generate the complete implementation for all five requested components 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?▼

Apply full-output enforcement rules that ban placeholder patterns like "// rest of code" and "for brevity". The skill locks the deliverable count upfront and cross-checks the final output so nothing is skipped or compressed.

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

What placeholder patterns indicate incomplete AI-generated code?▼

Common failure patterns include "// ...", "// TODO", "// implement here", "// similar to above", and prose like "the rest follows the same pattern" or "and so on". These signal omitted logic and should be treated as hard failures.

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 unnecessary for casual queries.