verification-mastery
Verification Mastery establishes a mandatory gate: never claim work is done without running fresh verification commands and reviewing their output. The skill teaches a five-step workflow—identify what proves your claim, execute the full command, read the complete output, confirm it matches your assertion, and only then make the claim. It covers common scenarios like test passes, builds, linter checks, and bug fixes, each with specific evidence requirements.
Verification Mastery teaches you to run fresh verification commands and check their output before claiming any task is complete.
AI-generated summary based on this skill's SKILL.md
Install
xenitV1/claude-code-maestro/verification-mastery · repository language: JavaScript
git clone https://github.com/xenitV1/claude-code-maestro
cp -r claude-code-maestro/skills/verification-mastery ~/.claude/skills/verification-masteryFrequently asked questions
AI-generated answers based on this skill's SKILL.md and metadata
How do I verify task completion before claiming success?
Verification Mastery teaches a five-step workflow: first, identify what concrete evidence would prove your claim (e.g., test output, build log, linter report). Second, execute the full verification command without shortcuts. Third, read the complete output—not just the exit code. Fourth, confirm the output actually matches your assertion. Fifth, only then claim the work is done. Never assume success; always run fresh verification commands and review their results before making any completion claim.
What are verification commands for tests and builds?
Verification Mastery covers specific verification scenarios: for tests, run the full test suite and confirm all pass (not just that the command ran). For builds, execute the complete build and verify it succeeds—linter passing is not enough. For bug fixes, run regression tests to confirm the fix works and nothing broke. For requirements, use a checklist and verify each item with concrete evidence. Each scenario requires running the actual command, capturing its output, and confirming the output proves your specific claim.
How can I ensure work is actually done, not just assumed?
Verification Mastery prevents false completion claims by requiring evidence-based verification every time. Never skip verification steps or assume success based on partial signals. Always execute fresh commands—do not rely on cached results or prior runs. Read the complete output, not just the summary line. Look for red flags like rationalization patterns that bypass verification gates, missing test output, or claims without supporting evidence. Make verification a mandatory gate in your workflow; completion signals only count when backed by actual command output you have reviewed.
How do I verify tests pass with actual output?
Verification Mastery requires running the full test command and reviewing complete output. Execute your test suite in full—not a subset. Capture the entire output, including pass/fail counts and any failures. Confirm every test passed, not just that the command exited cleanly. For regression tests, verify both that the fix works and that existing tests still pass. Never claim tests pass without showing the actual test output. Use git diff to confirm agent changes match your expectations. Quality standards demand fresh verification output every time, with no assumptions.
What red flags indicate unverified work?
Verification Mastery identifies red flags that signal unverified work: claiming done without running verification commands, showing only exit codes instead of full output, assuming success based on partial signals like linter passes alone, skipping regression tests, using cached results instead of fresh verification, rationalizing away missing evidence, or claiming requirements met without a checklist. Stop claiming done without proof. Watch for patterns where verification gates are bypassed. Require concrete evidence—actual command output you have read and confirmed—before accepting any completion claim.
What is the verification mastery best practice workflow?
Verification Mastery's core workflow is: identify what proves your claim, execute the full command, read complete output, confirm it matches your assertion, then claim success. Apply this to every task—tests, builds, bug fixes, requirements. Never skip steps. Always run fresh verification; no assumptions. Review actual output, not summaries. Use git diff to confirm changes. Run regression tests. Build a checklist for requirements and verify each item. Make verification a mandatory gate before any completion signal. This evidence-based approach prevents hallucinated success reports and ensures quality standards are met.
SKILL.md
rendered from the published skill — quoted content, verbatim
<domain_overview>
✅ VERIFICATION MASTERY: EVIDENCE BEFORE CLAIMS
> Philosophy: Claiming work is complete without verification is dishonesty, not efficiency. Evidence before claims, always. EVIDENCE INTEGRITY MANDATE (CRITICAL): Never claim a task is complete based on assumption or past memory. You MUST generate fresh evidence (logs, screenshots, test output) for every claim. AI-generated success reports are untrustworthy without proof. Any completion signal sent without accompanying verification artifacts must be rejected as "Hallucinated Success".
🚨 THE IRON LAW
NO COMPLETION CLAIMS WITHOUT FRESH VERIFICATION EVIDENCE
If you haven't run the verification command in this message, you cannot claim it passes. Violating the letter of this rule is violating the spirit of this rule. </domain_overview> <core_workflow>
🚪 THE GATE FUNCTION
``` BEFORE claiming any status or expressing satisfaction: 1. IDENTIFY: What command proves this claim? 2. RUN: Execute the FULL command (fresh,
(truncated - see the full file via the links below)
Read as markdown · JSON record · Browse the source repository
File tree — 1 file
skills/verification-mastery/SKILL.md