full-output-enforcement

Enforces complete code generation by banning placeholder patterns and truncation.

Updated Jul 20, 2026
One-click install
npx skills add https://github.com/Jatinkrmahato993203/crime --skill full-output-enforcement-jatinkrmahato993203
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: full-output-enforcement
Source: https://github.com/Jatinkrmahato993203/crime/tree/main/skills/output-skill
Command: npx skills add https://github.com/Jatinkrmahato993203/crime --skill full-output-enforcement-jatinkrmahato993203

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 and unusable results. This Skill overrides that default behavior so every requested file, function, or section is delivered in full. ## Core Features & Use Cases - Placeholder Ban: Hard-fails patterns such as "// ...", "// TODO", "for brevity", and "the rest follows the same pattern" in both code and prose. - Scope Locking & Cross-Check: Counts expected deliverables before generating, then verifies the count against the original request before responding. - Token-Limit Handling: Stops at clean breakpoints with a structured [PAUSED] marker and resumes exactly where it left off on "continue", without compression or recap. - Use Case: Ask for a full 5-component React dashboard implementation; instead of receiving one component plus stubs, you receive all five complete, runnable components. ## 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 completely. The skill locks the deliverable count before generating and cross-checks it before responding.

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 [PAUSED — X of Y complete] marker. 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". These indicate incomplete output.

Does output enforcement work for non-code writing tasks?▼

Yes, the same rules apply to prose deliverables such as documentation, reports, and multi-section answers. The scope-count and cross-check process ensures every requested section is present and finished.

When should I not use full-output enforcement?▼

Avoid it for quick exploratory questions, brainstorming, or when a short summary is explicitly wanted. Enforcing exhaustive output on simple queries wastes tokens and slows down responses.