Full output enforcement

Skill wedabro/bro-skills/.agents/skills/full-output-enforcement

bro-skills - Spec-Driven Development CLI

Install

npx -y skills add wedabro/bro-skills --skill full-output-enforcement

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Overrides default LLM truncation behavior. Enforces complete code generation, bans placeholder patterns, and handles token-limit splits cleanly. Apply to any task requiring exhaustive, unabridged output.

SKILL.md

2.7 KB, as published. Nobody here has run it

Full-Output Enforcement

Baseline

When the user explicitly requests exhaustive output, optimize for completeness within higher-priority instructions and the available execution environment. If the user asks for a full file, deliver the full file. If the user asks for five components, deliver five components.

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

Scope — Read the full request. Count how many distinct deliverables are expected (files, functions, sections, answers). Lock that number.
Build — Generate every deliverable completely. No partial drafts, no "you can extend this later."
Cross-check — Before output, re-read the original request. Compare your deliverable count against the scope count. If anything is missing, add it before responding.

Handling Long Outputs

When a direct textual response approaches the token limit and the environment cannot continue the work automatically:

Do not compress remaining sections to squeeze them in.
Do not skip ahead to a conclusion.
Write at full quality up to a clean breakpoint (end of a function, end of a file, end of a section).
End with:

[PAUSED — X of Y complete. Send "continue" to resume from: next section name]

In agentic environments, continue through the available work mechanism instead of asking the user to resume. If a textual continuation is genuinely required, pick up exactly where the previous output stopped.

Quick Check

Before finalizing any response, verify:

No banned patterns from the list above appear anywhere in the output
Every item the user requested is present and finished
Code blocks contain actual runnable code, not descriptions of what code would do
Nothing was shortened to save space