output-completeness

Enforce complete, non-truncated outputs for multi-step tasks.

2|Updated Jan 3, 2026

Search Tags:#documentation #completeness #output #long-form #multi-part #no-truncation

Ready to run

npx skills add https://github.com/jlaws/dotfiles --skill output-completeness

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: output-completeness
Source: https://github.com/jlaws/dotfiles/tree/main/.agents/skills/workflow/output-completeness
Command: npx skills add https://github.com/jlaws/dotfiles --skill output-completeness

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Prevents incomplete results by enforcing non-truncated, fully complete outputs for long-running or multi-part tasks. It blocks skeletons, stubs, or partial results from being delivered and helps ensure high-integrity deliverables.

Core Features & Use Cases

End-to-end completion: Guarantees that tasks are finished in a single cohesive output, avoiding fragmented results.
Guardrails against placeholders: Detects and rejects ellipses, TODOs, or skeleton code in generated content.
Use Case: Ideal for large documentation, full-code refactors, or multi-file implementations that require complete, ready-to-use results.

Quick Start

Provide a complete, multi-part solution without truncation, ensuring every step is fully written and no placeholders remain.

Frequently Asked Questions about output-completeness

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I prevent truncated outputs when generating long-form documentation?▼

To prevent truncated outputs in long-form documentation, enforce non-truncated generation by rejecting skeleton code, placeholders, and deferred sections. This ensures multi-part responses deliver complete, end-to-end content without partial results.

Why does my multi-step code generation include stubs and TODOs?▼

Multi-step code generation includes stubs and TODOs when explicit guardrails against placeholders are missing. Applying completeness rules blocks skeleton code and ensures full implementations are delivered without deferred sections or partial results.

What is the best way to ensure complete outputs for multi-file implementations?▼

The best way to ensure complete outputs for multi-file implementations is to apply end-to-end completion guardrails. This blocks fragmented results and guarantees fully written, ready-to-use code without truncation or placeholders.

Can I use automated completeness checks for large code refactors?▼

Yes, you can use automated completeness checks for large code refactors. These checks detect and reject ellipses, TODOs, and partial code, ensuring high-integrity deliverables that are fully written in a single cohesive output.

When do I need guardrails against placeholders in complex plan writing?▼

You need guardrails against placeholders in complex plan writing when partial results create risk. If your exhaustive guides or multi-part responses require end-to-end completion with no stubs, guardrails prevent truncated or incomplete deliverables.