full-output-enforcement

Enforces complete code generation by banning placeholder patterns and truncation.

Updated Apr 20, 2026
One-click install
npx skills add https://github.com/ShyamRavidath/oscc-detection-v2 --skill full-output-enforcement-shyamravidath
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: full-output-enforcement
Source: https://github.com/ShyamRavidath/oscc-detection-v2/tree/main/.agents/skills/full-output-enforcement
Command: npx skills add https://github.com/ShyamRavidath/oscc-detection-v2 --skill full-output-enforcement-shyamravidath

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? LLMs often truncate long outputs, insert placeholder comments like "// rest of code", or skip deliverables when generating large files or multi-part responses. This Skill overrides that default behavior so every requested deliverable is produced 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 distinct deliverables in a request up front and cross-checks the output against that count before responding. - Token-Limit Handling: When output approaches the token limit, it pauses at a clean breakpoint with a resumable marker instead of compressing or skipping content. - Use Case: Ask for a full 5-component React dashboard; instead of receiving one complete component and four stubs, you receive all five fully implemented, or a clean pause marker with exact resume instructions. ## 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 locks the deliverable count before generating and cross-checks the output against it.

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 from that point with no recap or repetition.

What placeholder patterns should be banned in AI code generation?

Banned patterns include "// ...", "// TODO", "// implement here", "// similar to above", bare ellipses standing in for code, and prose like "for brevity" or "the rest follows the same pattern" replacing actual content.

When should I not use full-output enforcement?

Avoid it for exploratory brainstorming, quick prototypes, or questions where a concise answer is appropriate. The skill treats every task as production-critical, which adds unnecessary length to casual or iterative exchanges.

Does output enforcement work with any LLM or framework?

Yes, it is a prompt-level instruction set with no code dependencies, so it works with any LLM that accepts system or skill instructions. It contains no scripts, external APIs, or platform-specific requirements.