An agentic skills framework & software development methodology that works.
refactor(skills): drop persuasion sections from verification-before-completion
Jesse Vincent3be5aad3dd24
diff --git a/skills/verification-before-completion/SKILL.md b/skills/verification-before-completion/SKILL.mdindex 2f14076e5..7d45333cc 100644--- a/skills/verification-before-completion/SKILL.md+++ b/skills/verification-before-completion/SKILL.md@@ -7,8 +7,6 @@ description: Use when about to claim work is complete, fixed, or passing, before## Overview-Claiming work is complete without verification is dishonesty, not efficiency.-**Core principle:** Evidence before claims, always.**Violating the letter of this rule is violating the spirit of this rule.**@@ -105,15 +103,6 @@ Skip any step = lying, not verifying❌ Trust agent report```-## Why This Matters--From 24 failure memories:-- your human partner said "I don't believe you" - trust broken-- Undefined functions shipped - would crash-- Missing requirements shipped - incomplete features-- Time wasted on false completion → redirect → rework-- Violates: "Honesty is a core value. If you lie, you'll be replaced."-## When To Apply**ALWAYS before:**@@ -129,11 +118,3 @@ From 24 failure memories:- Paraphrases and synonyms- Implications of success- ANY communication suggesting completion/correctness--## The Bottom Line--**No shortcuts for verification.**--Run the command. Read the output. THEN claim the result.--This is non-negotiable.