{"enrichment":{"faq":[{"a":"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\u2014not 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.","q":"How do I verify task completion before claiming success?"},{"a":"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\u2014linter 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.","q":"What are verification commands for tests and builds?"},{"a":"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\u2014do 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.","q":"How can I ensure work is actually done, not just assumed?"},{"a":"Verification Mastery requires running the full test command and reviewing complete output. Execute your test suite in full\u2014not 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.","q":"How do I verify tests pass with actual output?"},{"a":"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\u2014actual command output you have read and confirmed\u2014before accepting any completion claim.","q":"What red flags indicate unverified work?"},{"a":"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\u2014tests, 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.","q":"What is the verification mastery best practice workflow?"}],"shadow_tags":["evidence-based-workflow","completion-gates","proof-driven-quality","anti-hallucination","verification-first","integrity-checks","claim-validation","artifact-proof","assumption-prevention"],"summary_rewrite":"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\u2014identify 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."},"files":[{"bytes":6724,"path":"skills/verification-mastery/SKILL.md","sha256":"138e8504faad039e21539e315331cb085b7bc7b335bdf2ea5873d5ef05f7e68f","url":"https://skillfed.io/files/xenitV1/claude-code-maestro/verification-mastery/4952165b/SKILL.md"}],"id":"xenitV1/claude-code-maestro/verification-mastery","links":{"html":"https://skillfed.io/xenitV1/claude-code-maestro/verification-mastery","md":"https://skillfed.io/xenitV1/claude-code-maestro/verification-mastery.md","repo":"https://github.com/xenitV1/claude-code-maestro"},"meta":{"agents_supported":[],"first_seen":"2026-07-28","forks":34,"language":"JavaScript","last_updated":"2026-01-24","license":"MIT","name":"verification-mastery","publisher":"xenitV1","stars":230},"relations":{"similar":[{"id":"xenitV1/claude-code-maestro/tdd-mastery"},{"id":"obra/superpowers-skills/verification-before-completion"},{"id":"mrgoonie/claudekit-skills/verification-before-completion"},{"id":"eyadsibai/ltk/verification-before-completion"},{"id":"foryourhealth111-pixel/Vibe-Skills/verification-before-completion"},{"id":"family3253/skill/superpowers-verification-before-completion"},{"id":"getcrew44/crew44/verification-before-completion"},{"id":"rpamis/comet/verification-before-completion"},{"id":"qodex-ai/ai-agent-skills/quality-validation"},{"id":"Ibrahim-3d/orchestrator-supaconductor/verification-before-completion"}]},"slug":{"owner":"xenitV1","repo":"claude-code-maestro","skill":"verification-mastery"},"version":"4952165b"}