agentleFS
Sign inStart free
wedabrowedabro/bro-skills/.agents/skills/full-output-enforcement/SKILL.md

full-output-enforcement

Skill3 starsChanged 45 days agoMITView on GitHub

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.

We split this skill into the rules it gives an agent

8 rules. 7 are common, 1 is distinctive, and 0 are very specific to this project.

  • 7

    Common

    Most of the 80 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    When the user explicitly requests exhaustive output, optimize for completeness within higher-priority instructions and the available …

    line 10
  2. Common:

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

    line 33
  3. Common:

    Do not compress remaining sections to squeeze them in.

    line 36
  4. Common:

    Do not skip ahead to a conclusion.

    line 37
  5. Common:

    Write at full quality up to a clean breakpoint (end of a function, end of a file, end of a section).

    line 38
  6. Common:

    Before finalizing any response, verify:

    line 51
  7. Common:

    No banned patterns from the list above appear anywhere in the output

    line 52
  8. Common:

    Every item the user requested is present and finished

    line 53

“Common” is measured: kept by at least 6 in 10 of the 80 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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

  1. Scope — Read the full request. Count how many distinct deliverables are expected (files, functions, sections, answers). Lock that number.
  2. Build — Generate every deliverable completely. No partial drafts, no "you can extend this later."
  3. 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

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

Reviews can't be read right now.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free