domains / families / agent-tooling / full-output-enforcement

full-output-enforcement

authentic

Use when a task requires exhaustive unabridged output, complete files, or strict prevention of placeholders and skipped code.

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.

When not to use

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

Skill page

Source