completion-enforcer

Detect incomplete completion claims in agent outputs with five heuristic checks.

6|Updated Apr 7, 2026
One-click install
npx skills add https://github.com/Kgan01/ghengis-skills --skill completion-enforcer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: completion-enforcer
Source: https://github.com/Kgan01/ghengis-skills/tree/main/plugins/ghengis-skills/skills/completion-enforcer
Command: npx skills add https://github.com/Kgan01/ghengis-skills --skill completion-enforcer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Signal-based verification that work is really finished, catching premature "done" claims, placeholder content, and missing deliverables before they ship.

Core Features & Use Cases

  • Five heuristic checks ensure outputs are complete, not just optimistic.
  • Writes status and evidence to the shared scratchpad for reliable chain coordination.
  • Helps teams recover from partial results and trigger retries or fallbacks.

Quick Start

Run the five-check verifier on the latest agent output to confirm completion status before finalizing a task.

Frequently Asked Questions about completion-enforcer

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

FAQPage Schema
How do I verify agent task completion and catch premature done claims?

To verify task completion, you can apply five heuristic checks to agent outputs to detect incomplete results and flag partial deliverables. This catches premature done claims by validating outputs before finalizing the task.

What is signal-based verification for multi-step agent outputs?

Signal-based verification is a checking mechanism that ensures work is genuinely finished by applying five heuristic checks. It catches premature done claims, placeholder content, and missing deliverables before they ship.

How do I enforce completion checks for post-subagent tasks?

You enforce completion checks by running a five-check verifier on the latest post-subagent output. This confirms completion status and writes the evidence to a shared scratchpad for reliable chain coordination.

How does chain coordination handle partial results from subagents?

Chain coordination handles partial results by writing verification status and evidence to a shared scratchpad. This allows the system to recover from incomplete deliverables and trigger retries or fallbacks automatically.

What is the best way to detect placeholder content in agent outputs?

The best way to detect placeholder content is to apply heuristic verification checks to the agent output. These checks flag misleading done claims and missing deliverables, ensuring outputs are complete rather than optimistic.

When should I use heuristic verification for agent task completion?

You should use heuristic verification for post-subagent and multi-step tasks to ensure deliverables are complete. It is essential for catching incomplete or misleading done claims before reporting task completion.