Agent skill · software engineering · sickn33
full-output-enforcement
Use when a task requires exhaustive unabridged output, complete files, or strict prevention of placeholders and skipped code.
Why this skill is useful
Enforces strict output completeness and prevents common placeholder patterns, ensuring full implementations are delivered without omissions.
What it needs
About 3k tokens when loaded. Last updated 2026-08-07. 44,571 stars on the source repository.
What this skill does
Full-Output Enforcement When to Use Use when the user explicitly asks for full files, complete implementations, exhaustive lists, or unabridged deliverables. Use when placeholder code, skipped sections, TODO stubs, or descriptions in place of implementation would break the request. Use when a long answer may need clean continuation chunks without losing completeness or structural integrity. Limitations This skill enforces completeness, but it does not override token limits, safety constraints, missing source context, or user-provided scope boundaries. Split long outputs into clearly labeled continuation chunks when necessary, and verify that each chunk connects cleanly to the previous one. Do not invent unavailable code, credentials, private APIs, or project files to satisfy a request for complete output. Baseline Match completeness to the requested deliverable and its actual stakes. Do not optimize for brevity — optimize for completeness. If the user asks for a full file, deliver the full file. If the user asks for 5 components, deliver 5 components. Respect the limitations above and report unavailable inputs honestly. Banned Output Patterns The following patterns are hard failures. Never produce them: In code blocks: // ..., // rest of code, // implement here, // TODO, / ... /, // similar to above, // continue pattern, // add more as needed, bare ... standing in for omitted code In prose: "Let me know if you want me to continue", "I can provide more details if needed", "for brevity", "the rest follows the same pattern", "similarly for the remaining", "and so on" (when replacing actual content), "I'll leave that as an exercise" Structural shortcuts: Outputting a skeleton when the request was for a full implementation. Showing the first and last section while skipping the middle. Replacing repeated logic with one example and a description. Describing what code should do instead of writing it. Execution Process 1. Scope — Read the full request. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills sickn33/full-output-enforcement--b1b1a7