Validate completed work against plan criteria or git diff-based checks.
npx skills add https://github.com/bcbeidel/toolkit --skill verify-work-bcbeidel
Please help me install this Agent Skill. Skill: verify-work Source: https://github.com/bcbeidel/toolkit/tree/main/plugins/work/skills/verify-work Command: npx skills add https://github.com/bcbeidel/toolkit --skill verify-work-bcbeidel
Verifies completed work against predefined validation criteria, ensuring alignment with a plan's Validation section or, in ad-hoc mode, checks signals from git diff, project configuration, and project documentation.
Run the skill with a plan file path to validate your current work against the plan, or run it without a plan for ad-hoc validation.
High-intent search queries and answers about installing and using this skill.
To validate completed work against a plan, the skill reads the plan's Validation section and enforces its criteria. It applies automated checks first, then prompts for human judgment on qualitative items, outputting per-criterion results and recovery actions.
You can verify code changes without a formal validation plan using ad-hoc mode. This mode builds a hypothesis from git diff, project config, and project docs to propose and run automated checks, followed by human judgment for qualitative criteria.
The best way to automate workflow validation is using an automated-first plus human-check flow. The skill runs automated criteria first, then applies human judgment for qualitative criteria, returning a structured report with outcomes and next steps.
Yes, plan-mode validation requires plan integrity before checking work. The skill reads the predefined validation criteria from the plan's Validation section and enforces those checks to ensure alignment with the original requirements.
To get structured reporting and recovery guidance after verifying work, the skill outputs per-criterion results and recovery actions. This structured report includes validation outcomes and next steps to enable quick repair of any failed checks.
You should use ad-hoc validation instead of plan-mode verification when you lack a formal plan file. Ad-hoc mode builds checks from git diff, project config, and project docs, whereas plan mode requires a predefined Validation section to enforce criteria.
atomicinnovationValidate implementation plans against git history and test results.
FlexNetOSDiagnose and repair failed GitHub Actions workflows by analyzing logs.
him55710-sudoReview code diffs via Codex CLI and return a gate verdict.
nselugaWrite and execute tests against task 'done when:' criteria and report PASS/FAIL status.
