Verify Work
Multi-phase UAT gate — cold-start smoke, build, typecheck, lint, tests, step-by-step manual verification, gaps-closure loop. Use after execute-plan or develop-tdd, before audit-code.
Install
npx skills add danielvm-git/bigpowers --skill verify-workgit clone --depth 1 https://github.com/danielvm-git/bigpowers.git /tmp/bigpowers
mkdir -p ~/.claude/skills
cp -r /tmp/bigpowers/.cline/skills/verify-work ~/.claude/skills/verify-workPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Verify Work > **HARD GATE** — No story is "done" until manual UAT for the active story is confirmed with evidence. > > **HARD GATE** — Do NOT run on `main` or `master`. Use the feature branch from `kickoff-branch`. Review answers "is the code good?"; Verify answers "does the built thing do what was promised?" ## Modes - Default: full UAT plus gaps loop - --smoke: Cold-start only plus one happy-path flow. Use for hotfixes. - --cli: CLI tool verification — replaces cold-start with binary smoke checklist. Use for CLI tools with no server process. ## Risk-Scaled Depth `verify-work` reads the `risk:` field from the story template (defaults to `P1` if absent) to scale verification rigor: - **P0**: Full verify-work multi-phase + `security-review` (step 5) + NFR evidence gate (step 5b). - **P1**: Standard verify-work (build, test, lint, step-by-step manual). - **P2**: Smoke, typecheck, lint only. Skip tests, security scan, and step-by-step manual UAT. - **P3**: Typecheck and lint only. Skip smoke, tests, security scan, and step-by-step manual UAT. ## Process > **Timing:** `bash scripts/bp-timing.sh start verify-work` at invocation; `bash scripts/bp-timing.sh end verify-work` before handoff. 0. **Branch check** — must not be `main`/`master`. 0a. **Preflight / CI green (HARD GATE — e51s03)** — Run Preflight from `CLAUDE.md` or `BP_PREFLIGHT` (`bp-read-agents.sh`). If PR open: `gh pr checks` (**CI green**). Failure blocks all phases → `quick-fix` or `fix-bug`.
Details
- Skill name
verify-work- Repository
- danielvm-git/bigpowers
- Path
.cline/skills/verify-work/SKILL.md- License
- MIT
- Repo updated
- 9 November 2026
FAQ
What does the Verify Work skill do?
Multi-phase UAT gate — cold-start smoke, build, typecheck, lint, tests, step-by-step manual verification, gaps-closure loop. Use after execute-plan or develop-tdd, before audit-code.
How do I install the Verify Work skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add danielvm-git/bigpowers --skill verify-work. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Verify Work popular?
It lives in danielvm-git/bigpowers, which has 292 GitHub stars and 23 forks.
Related skills
Align Grid
292danielvm-git/bigpowers
Build editorial/magazine/report webpages on a GENUINE Müller-Brockmann modular grid (International Typographic Style) — not a decorative one. Encodes the discipline (columns + modules + baseline, grotesque type, flush-left, restrained black/white/red palette) AND the hard-won front-end engineering to make the grid real, visible, and verified: one CSS-variable source of truth, an interactive grid-toggle overlay that lives in the SAME content box as the content, subgrid "bands" so every element snaps to a column line, an 8px baseline lock, and runtime OPTICAL ALIGNMENT that puts display type's i
Assess Impact
292danielvm-git/bigpowers
Analyze the blast radius of a proposed change before any code is written. Maps dependents, affected stories, and test coverage. Produces specs/IMPACT_LATEST.md. Use before plan-work on any non-trivial change, when touching a shared module, or when the user asks "what does this break?".
Audit Code
292danielvm-git/bigpowers
Self-review checklist for the coding agent to run before dispatching a reviewer. Checks CONVENTIONS.md compliance, Boy Scout Rule, test coverage, types, and SOLID. Produces a pass/fail checklist. Use before request-review, before committing, or when user asks for a code quality check.
Browserstack
100adriannoes/awesome-agentic-ai
Run tests on BrowserStack. Use when user mentions "browserstack", "cross-browser", "cloud testing", "browser matrix", "test on safari", "test on firefox", or "browser compatibility".
Validate Fix
292danielvm-git/bigpowers
Prove a fix works before declaring done — re-run the failing test, run the full suite, typecheck, lint, and harden against recurrence. Use after implementing a bug fix, when user says "is this fixed?", or before closing an investigation.
Coverage
100adriannoes/awesome-agentic-ai
Analyze test coverage gaps. Use when user says "test coverage", "what's not tested", "coverage gaps", "missing tests", "coverage report", or "what needs testing".
Browse the most popular Claude skills, all testing & qa skills, or write your own with the skills generator.