verify-work
Skill288 starsChanged 5 days agoMITView on GitHub
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.
8 other projects use a version of this.
Adopted by
Most recently taken up by
- jisuzzzz/haechitheir own version, first seen Nov 8, 2026
- buildomator/buildomatortheir own version, first seen Nov 4, 2026
- Astatide1337/Skillstheir own version, first seen Oct 20, 2026
- linellazatin/skillstheir own version, first seen Oct 17, 2026
- tonygorb/skillstheir own version, first seen Oct 15, 2026
- hassan-mohiddin/freeflowtheir own version, first seen Oct 4, 2026
Other versions8 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 8
- hamzafarooq/claude-code-starter★ 145same name
- buildomator/buildomator★ 102same name
- jisuzzzz/haechi★ 17same name
- hassan-mohiddin/freeflow★ 5same name
- tonygorb/skills★ 2same name
- aprameyak/coding-skills★ 1same name
- Astatide1337/Skills★ 1same name
- linellazatin/skills★ 1same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository162 other files it gives its agents.
- AGENTS.mdAGENTS.md
- docs/AGENTS.mdAGENTS.md
- website/AGENTS.mdAGENTS.md
- .cursor/rules/align-grid.mdcCursor rule
- .cursor/rules/assess-impact.mdcCursor rule
- .cursor/rules/audit-code.mdcCursor rule
- .cursor/rules/audit-plan.mdcCursor rule
- .cursor/rules/build-epic.mdcCursor rule
- .cursor/rules/change-request.mdcCursor rule
- .cursor/rules/commit-message.mdcCursor rule
- .cursor/rules/compose-workflow.mdcCursor rule
- .cursor/rules/craft-skill.mdcCursor rule
- .cursor/rules/deepen-architecture.mdcCursor rule
- .cursor/rules/define-language.mdcCursor rule
- .cursor/rules/define-success.mdcCursor rule
- .cursor/rules/delegate-task.mdcCursor rule
- .cursor/rules/deploy.mdcCursor rule
- .cursor/rules/design-interface.mdcCursor rule
- .cursor/rules/develop-tdd.mdcCursor rule
- .cursor/rules/diagnose-root.mdcCursor rule
- .cursor/rules/diagnose-stall.mdcCursor rule
- .cursor/rules/dispatch-agents.mdcCursor rule
- .cursor/rules/edit-document.mdcCursor rule
- .cursor/rules/elaborate-spec.mdcCursor rule
- .cursor/rules/enforce-first.mdcCursor rule
- .cursor/rules/evolve-skill.mdcCursor rule
- .cursor/rules/execute-plan.mdcCursor rule
- .cursor/rules/extract-design.mdcCursor rule
- .cursor/rules/find-way.mdcCursor rule
- .cursor/rules/fix-bug.mdcCursor rule
- .cursor/rules/gate-trace.mdcCursor rule
- .cursor/rules/generate-allure-report.mdcCursor rule
- .cursor/rules/grill-me.mdcCursor rule
- .cursor/rules/grill-with-docs.mdcCursor rule
- .cursor/rules/guard-git.mdcCursor rule
- .cursor/rules/harden-vps.mdcCursor rule
- .cursor/rules/hook-commits.mdcCursor rule
- .cursor/rules/inspect-quality.mdcCursor rule
- .cursor/rules/investigate-bug.mdcCursor rule
- .cursor/rules/kickoff-branch.mdcCursor rule
- .cursor/rules/maintain-wiki.mdcCursor rule
- .cursor/rules/map-codebase.mdcCursor rule
- .cursor/rules/migrate-spec.mdcCursor rule
- .cursor/rules/model-domain.mdcCursor rule
- .cursor/rules/orchestrate-project.mdcCursor rule
- .cursor/rules/organize-workspace.mdcCursor rule
- .cursor/rules/plan-refactor.mdcCursor rule
- .cursor/rules/plan-release.mdcCursor rule
- .cursor/rules/plan-tests.mdcCursor rule
- .cursor/rules/plan-work.mdcCursor rule
- .cursor/rules/publish-package.mdcCursor rule
- .cursor/rules/quick-fix.mdcCursor rule
- .cursor/rules/release-branch.mdcCursor rule
- .cursor/rules/request-review.mdcCursor rule
- .cursor/rules/research-first.mdcCursor rule
- .cursor/rules/reset-baseline.mdcCursor rule
- .cursor/rules/respond-review.mdcCursor rule
- .cursor/rules/run-benchmark.mdcCursor rule
- .cursor/rules/run-evals.mdcCursor rule
- .cursor/rules/run-planning.mdcCursor rule
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
7 rules. 0 are common, 5 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 8 edited versions we read keep these.
5
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 29
Default: full UAT plus gaps loop
- Very specific: line 49
Read active story tasks from specs/epics/<capsule>/eNNsYY-tasks.yaml and story spec from specs/epics/<capsule>/eNNsYY-<slug>.md …
- Distinctive: line 78
Stop server, clear caches, boot from scratch.
- Distinctive: line 82
After UAT, identify and close any gaps between promised behavior and actual behavior:
- Distinctive: line 85
Document what actually happened (expected vs actual)
- Distinctive: line 86
If behavior doesn't match the promises, log the gap
- Very specific: line 97
After UAT passes, write structured evidence to specs/verifications/eNNsYY-verify.yaml:
“Common” is measured: kept by at least 6 in 10 of the 8 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
<!-- story: e02s01 e46s03 --><!-- story: e38s05 --><!-- story: e45s05 --><!-- story: e45s09 --><!-- story: e45s13 --><!-- story: e45s40 --><!-- story: e51s03 --><!-- story: e20s04 --><!-- story: e20s06 -->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
mainormaster. Use the feature branch fromkickoff-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-workat invocation;bash scripts/bp-timing.sh end verify-workbefore handoff.
- 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.
- Read active story tasks from
specs/epics/<capsule>/eNNsYY-tasks.yamland story spec fromspecs/epics/<capsule>/eNNsYY-<slug>.md(countable-story-format, Gherkin in §17). Note therisk:level (P0–P3). 1a. Pre-UAT verify validation — for each task'sverify:command, run it and detect pattern mismatches before UAT begins. If a grep/awk/jq command fails, check whether the pattern is wrong vs. a genuine failure:
Report:# For a failing grep -q 'PATTERN' FILE, check what is actually in FILE grep 'PATTERN' FILE || grep -n '' FILE | head -20 # show nearest lines"Pattern 'X' not found. Nearest match: 'Y' at line N"and ask"Update verify command? [Y/n]". Fix before proceeding — a mismatched verify command produces false failures during UAT. - Cold-start smoke (if app; skip if P3): stop server, clear caches, boot from scratch.
- AGENTS.md preflight — if 0a skipped BP_PREFLIGHT, run
bash scripts/bp-read-agents.shand use detected command. - Mechanical gates: build → typecheck → lint → tests (from
CLAUDE.mdor AGENTS.md). Skip tests if P2/P3.
HARD GATE — One-test-minimum terminal verdict (e45s13): At least one mechanical gate MUST be a real terminal-verdict command (shell exits 0 or non-zero — not prose, not combined log excerpts). Record that command's stdout/stderr from a single contiguous run in
specs/verifications/eNNsYY-verify.yamlunderterminal_verdict. Bug reports and gap logs MUST NOT merge evidence from multiple runs into one verdict — each failing run gets its own evidence block.
- Security scan (skip if P2/P3) — run
security-reviewagainst the git diff (working tree vs merge-base). Parse findings report. If any HIGH findings with confidence ≥ 8 exist → block the gate. Write findings tospecs/security/REVIEW.md. Allow documented exceptions viaspecs/security/EXCEPTIONS.md. MEDIUM/LOW findings warn but don't block. 5a. Blind-spot check — runbash scripts/check-blind-spots.sh. This detects structural quality gaps (verify-gap, test-gap, stale-tag, etc.) beyond percentage coverage. If any HIGH-severity findings exist → block the verify-work PASS gate. Findings are written tospecs/blind-spots.json. MEDIUM/LOW findings warn but don't block. 5a2. Completeness critic (e45s05) —bash scripts/lib/completeness-critic.sh. BLOCKER aborts merge gate; WARNING → gaps loop; FILLED = evidence only.
5b. NFR Evidence Gate (P0 only) — Go/no-go on Performance, Reliability, Operability against specs/tech-architecture/eNN-TEST_PLAN_LATEST.md. Evidence written to specs/verifications/NFR-eNNsYY.json. FAIL blocks gate.
5c. Adversarial Defect Mutation Gate (HARD GATE — e86 / ab-20) — bash scripts/verify-adversarial.sh. Boundary fuzzing & parameter injection against modified interfaces. Crashes or failures block PASS gate; evidence in specs/verifications/ADVERSARIAL_LATEST.yaml.
6. Step-by-step UAT (skip if P2/P3) — one user-observable action at a time.
7. Gaps loop — failures → log → plan-work → re-verify. Unaddressed HIGH findings from step 5 feed into this loop alongside other quality gaps.
7a. Validation gate (e45s09) — All tasks status: passing; evidence in specs/verifications/; update execution-status.yaml.
7b. Reopen-don't-refile (e45s09) — Regressions reopen existing story/bug — no duplicate capsule entries.
Verify sub-operations
Cold-Start Smoke (absorbed)
Stop server, clear caches, boot from scratch; confirm no stale config affects behavior.
Gaps Loop (absorbed)
After UAT, identify and close any gaps between promised behavior and actual behavior:
- Capture what was promised in the epic task description
- Document what actually happened (expected vs actual)
- If behavior doesn't match the promises, log the gap
- Loop back to
plan-workordevelop-tddto fix the gap - Re-verify until all gaps are closed (gaps count = 0)
UAT dialogue
- Pass: user confirms per step.
- Fail: capture expected vs actual; do not mark done in
execution-status.yaml.
Persist verification evidence
After UAT passes, write structured evidence to specs/verifications/eNNsYY-verify.yaml:
story_id: e01s01
verified_at: "2026-06-11T14:30:00Z"
verifier: verify-work
phases:
smoke:
passed: true
build:
passed: true
command: "npm run build"
typecheck:
passed: true
lint:
passed: true
tests:
passed: true
coverage: "94.2%"
terminal_verdict:
command: "npm test"
exit_code: 0
captured_at: "2026-06-11T14:25:00Z"
note: "Single run — do not merge output from other attempts"
manual:
steps:
- step: "Open /login"
expected: "Login form renders"
actual: "Login form rendered correctly"
passed: true
gaps:
closed: true5b. OKF wiki LINT (e39s08)
for p in specs/skills-wiki/skills/*.md; do s="skills/$(basename "$p" .md)/SKILL.md"; [ -f "$s" ]&&[ "$p" -ot "$s" ]&&echo "STALE: $p"; done
for p in specs/conventions-wiki/*.md; do [ "$(basename "$p")" = "index.md" ]&&continue; grep -q "$(basename "$p" .md)" CONVENTIONS.md||echo "ORPHAN: $p"; doneHARD GATE — Verification evidence MUST be persisted before marking the story done. No evidence = not verified.
--cli mode
CLI tools: use --cli when no server process. Binary detect + checklist: REFERENCE.md.
Verify
→ verify: find specs/verifications -maxdepth 1 -name '*-verify.yaml' 2>/dev/null | grep -q .
Handoff
READY -> next: audit-code Writes: state.yaml handoff.next_skill = audit-code
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

