mcpField
C
completion-evidence-discipline

completion-evidence-discipline

github.com/fudesign2008Testing & quality653 installsUpdated today
Repository

About completion-evidence-discipline

completion-evidence-discipline is an internal shared skill that governs completion and verification claims. It requires fresh evidence from the current turn or an explicit pending label for checks that have not been run.

Key features

  1. 01Require current-turn verification evidence
  2. 02Label unrun checks as pending
  3. 03Distinguish executed actions from pending work
  4. 04Require inspection of screenshots after UI checks

Use cases

  1. 01Report test and build results accurately
  2. 02Close out work without unsupported pass claims
  3. 03Track manual verification still required
  4. 04Validate screenshots from UI checks

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/fudesign2008/open-skills --skill completion-evidence-discipline

After installing, type/completion-evidence-disciplinein Claude Code to confirm it loaded.

Details

From the project README

Completion Evidence Discipline

Internal shared skill. Single source of truth for fresh-evidence gates on completion and verification claims. Hosts declare it in dependencies (directly or via staged-review-flow) and abort if missing — no silent fallback.

Name note: this skill is intentionally not named verification-before-completion (reserved by an external skills repo). Use this name only.

Iron Law

NO COMPLETION OR PASS CLAIMS WITHOUT FRESH EVIDENCE FROM THE CURRENT TURN.

  • Fresh = produced by a command, check, or observed tool result executed in this assistant turn (or an attached log from that same turn).
  • Not fresh = prior-turn memory, “we designed a test”, subagent success text alone, or assumed green CI.

Required behavior

When about to claim any of: tests passed, typecheck/build OK, verification complete, bug fixed, ready to merge/archive:

  1. Run the relevant command/check in this turn, or
  2. Label Pending with the exact manual action still required — and do not say it passed.

When the check opened a UI, that fresh evidence includes a filesystem path to a non-empty png, jpg, jpeg, or webp saved this turn. A path with no such file does not support a pass claim. Checks that did not open a UI do not require an image. Before an opened-UI image supports the check, look at the saved image in this turn. A blank frame, a solid black frame, or an image with no readable interface stays pending and states that the capture is still required. A readable interface that is not the screen this check was supposed to open stays pending and states the expected screen and what the image shows. If the image was not inspected, the item stays pending and states that the image was not inspected. Keep the file. Do not treat any of those as the expected capture.

Compose with staged-review-flow verification honesty:

LabelMeaning
ExecutedCommand/action + concise output summary from this turn
PendingExact action the user (or a later turn) must still run

Forbidden

  • Reporting “all green” / “verified” when no verifying command was run this turn
  • Treating designed scenarios or unchecked assertions as executed passes
  • Renaming or aliasing this skill to verification-before-completion inside this repository

Integration guide

  • Hosts: one-line pointer at verification / closeout — load this skill; do not paste the Iron Law or opened-UI screenshot inspection prose.
  • staged-review-flow: honesty rule MUST compose with this gate (Executed ⇒ fresh evidence).
  • Orthogonal to runtime-verification-discipline: this skill gates evidence freshness (did you run it this turn); that skill gates verification environment and executor (which tier, who ran it, sufficient?). A pass claim must satisfy both.
  • Prefer user-invocable: false; users reach it through PDCA hosts.

Comments

Markdown supported