# Full Output Enforcement

> 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.

Source: https://skillsagentes.com/skills/leonxlnx/taste-skill/full-output-enforcement
Repository: https://github.com/Leonxlnx/taste-skill
Author: leonxlnx
License: MIT
Updated: hace 4 meses
Context cost: 51 tok installed, 648 tok once triggered, 648 tok with every bundled file
Bundle: 1 file, 3 KB
Permissions requested: none declared

## Install

```bash
npx -y skills add Leonxlnx/taste-skill --skill output-skill --agent claude-code
```

## What it does

- Prohíbe patrones de placeholder como "// ...", "// TODO", "and so on" tanto en código como en prosa
- Obliga a contar los deliverables solicitados y a verificar el conteo antes de responder
- Define un formato de pausa/continuación limpio cuando la respuesta se acerca al límite de tokens
- Exige generar cada entregable completo, sin omitir secciones ni describir código en vez de escribirlo

## Use it when

- Cualquier tarea que requiera salida exhaustiva y sin abreviar
- El usuario pide un archivo completo, varios componentes o secciones múltiples

## What triggers it

- "Dame el archivo completo, sin resúmenes ni placeholders"
- "Genera los 5 componentes completos, no me dejes ningún TODO"
- "Continúa exactamente donde te quedaste, sin repetir nada"

## Files

- SKILL.md — 3 KB

## SKILL.md

Reproduced verbatim from Leonxlnx/taste-skill under MIT. This section is the upstream document and is in English.

# Full-Output Enforcement

## Baseline

Treat every task as production-critical. A partial output is a broken output. 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. No exceptions.

## 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 response approaches the token limit:

- 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]
```

On "continue", pick up exactly where you stopped. No recap, no repetition.

## 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

---

Skills Agentes — https://skillsagentes.com/skills/leonxlnx/taste-skill/full-output-enforcement