| name | task-completion-gate |
| description | Invoke before reporting a task "done", "complete", "fixed", "green", or "shipped" — the final gate that blocks a completion claim unless a this-session tool result proves the desired state was reached, tested, and left green. Prevents CASHE (incomplete / untidy / false-result work): stale cache hits, partial summaries, unverified claims. Model: inherits caller tier.
|
| allowed-tools | Bash, Read, Grep, Glob |
task-completion-gate — no "done" without green proof
The permanent completion gate for Pi-CEO agents (RA-2141). A task is not done when the
work looks finished; it is done when a this-session tool result proves the target
state was reached, tested, and left green. This skill is the last step before any
completion claim leaves an agent.
Founder rule (2026-05-21): no agent may report "done" or "completed" until the green
confirmation is present. CASHE = a Cache of incomplete / untidy / false-result work
that breaks the autonomous chain. This gate exists to stop CASHE regrowing in emits,
Linear, or the wiki.
When to invoke
Immediately before emitting any of: "done", "complete", "completed", "fixed", "resolved",
"green", "shipped", "verified", or closing a Linear ticket / posting a done-status comment.
If the draft asserts a finished state, run this gate first.
The gate — four checks, all must pass
- State reached — the requested end state exists now. Point to the tool result that
shows it (file contents, PR
state: MERGED, endpoint 200, row present).
- Tested — the change was exercised, not just written. Point to the test/smoke/CI run
from this session with a pass line (
N passed, checks , exit 0). A green run
from a previous turn is a hypothesis — re-run it.
