full-output-enforcement

Enforces complete code generation by banning placeholder patterns and truncation.

Updated Jun 12, 2026
One-click install
npx skills add https://github.com/oleyna80/agentic-sdlc-framework --skill full-output-enforcement-oleyna80
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: full-output-enforcement
Source: https://github.com/oleyna80/agentic-sdlc-framework/tree/main/skills/output-skill
Command: npx skills add https://github.com/oleyna80/agentic-sdlc-framework --skill full-output-enforcement-oleyna80

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? LLMs often truncate long outputs, insert placeholder comments like "// rest of code", or stop mid-task to save tokens. This Skill overrides that default behavior so every requested deliverable is generated in full, with clean pause-and-resume handling when token limits are hit. ## Core Features & Use Cases - Placeholder Ban: Hard-fails on patterns like // ..., // TODO, "for brevity", and skeleton-only outputs, forcing complete implementations. - Deliverable Counting: Scopes the request, locks the expected number of deliverables, and cross-checks the output against that count before responding. - Token-Limit Splitting: Pauses at clean breakpoints with a structured resume marker instead of compressing or skipping remaining sections. - 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 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?▼

Use explicit output-enforcement instructions that ban placeholder patterns like "// rest of code" and require every requested deliverable to be generated in full. This Skill locks the deliverable count upfront 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 emit a pause marker stating progress and the next section. On "continue", resume exactly where you stopped without recap or repetition.

What placeholder patterns indicate incomplete AI-generated code?▼

Common signs include comments like "// ...", "// implement here", "// TODO", "// similar to above", and prose such as "for brevity" or "the rest follows the same pattern". Skeleton structures replacing full implementations are also incomplete output.

When should I not use full-output enforcement?▼

Avoid it for exploratory questions, quick prototypes, or when you only need a snippet or conceptual example. Forcing exhaustive output on small questions wastes tokens and slows iteration.