verify-feature
Skill0 starsChanged 15 days agoMITView on GitHub
Verify a feature in the running product against its acceptance criteria and states, with evidence. Use before you call a feature done.
8 other projects use a version of this.
Adopted by
Most recently taken up by
- baichen99/skillstheir own version, first seen Nov 16, 2026
- GTStagg/project-eyastheir own version, first seen Nov 16, 2026
- arcasilesgroup/ai-engineeringtheir own version, first seen Nov 8, 2026
- phatysddev/skillstheir own version, first seen Oct 9, 2026
- ProxiBlue/claude-skillstheir own version, first seen Oct 7, 2026
- quaat/autonomous-developmenttheir own version, first seen Sep 24, 2026
Other versions8 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 8
- arcasilesgroup/ai-engineering★ 65same name
- ProxiBlue/claude-skills★ 18same name
- phatysddev/skills★ 8same name
- quaat/autonomous-development★ 3same name
- SemanticMatter/autonomous-development★ 3same name
- GTStagg/project-eyas★ 2same name
- TomWebwalker/skills★ 2same name
- baichen99/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 repository25 other files it gives its agents.
- AGENTS.mdAGENTS.md
- templates/CLAUDE.mdCLAUDE.md
- a11y-auditSkill
- architecture-reviewSkill
- bootstrap-projectSkill
- capture-screenshotsSkill
- customizeSkill
- deliver-featureSkill
- design-reviewSkill
- docs-upkeepSkill
- fix-bugSkill
- handoffSkill
- implementSkill
- leadSkill
- log-decisionSkill
- refine-requirementsSkill
- release-readinessSkill
- reproduce-in-worktreeSkill
- security-auditSkill
- ship-prSkill
- start-taskSkill
- sync-branchSkill
- threat-modelSkill
- vet-dependencySkill
- write-adrSkill
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 15
Start only what's needed (the local backend, the app in a browser, the service).
- Distinctive: line 16
Use the project's runbook for launch commands and the test accounts (a scripted second user for multi-user flows).
- Very specific: line 21
Do the impact assessment in ${CLAUDE_PLUGIN_ROOT}/principles/08-testing-qa.md, "Tests for a change".
- Distinctive: line 23
Run only the automated tests that the change can affect.
- Distinctive: line 26
Put the impact assessment in your report.
- Distinctive: line 34
Data: check the rows, files and jobs the action should create, with direct queries, counts and outcomes.
- Very specific: line 47
When another agent or session continues from here, write a handoff with these results.
“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
Verify in the real app
Playbook files named here: when the project has its own copy at
.playbook/local/<same path>, use that copy instead.
Target: $ARGUMENTS
Setup
- Start only what's needed (the local backend, the app in a browser, the service). Note each process so you can stop it.
- Use the project's runbook for launch commands and the test accounts (a scripted second user for multi-user flows).
- Pick the driver for the platform (
${CLAUDE_PLUGIN_ROOT}/principles/08-testing-qa.md→ "Drivers"): Playwright or the agent's browser tools for web;curlor the test client for an API.
Find the impact
Do the impact assessment in ${CLAUDE_PLUGIN_ROOT}/principles/08-testing-qa.md, "Tests for a change". Then:
- Run only the automated tests that the change can affect. Do not run all the tests, except when the assessment tells you to.
- Walk the acceptance criteria of the task (below).
- A changed shared file can affect other features. For each of these features, walk its main path one time, and its state that uses the shared file.
- Put the impact assessment in your report.
Walk it
- Acceptance criteria, one by one, as a customer would. Record what you did and what you saw.
- States: loading (throttle or pause the backend), error (stop the API so reads fail), offline (the browser offline plus the backend unreachable), empty (a fresh account).
- Unhappy paths: close the tab or kill the process mid-write or mid-upload, then reopen; a plan limit; permission denied; two users at once; a slow network.
- Accessibility: the largest text size (200% zoom, 320 px reflow), keyboard only, screen reader labels on new controls, reduce motion on. Reset each setting afterwards.
- Data: check the rows, files and jobs the action should create, with direct queries, counts and outcomes.
- Lifecycle: a reload, a second tab, the back button, a session that expires, a deploy while the page is open.
Scenarios
offline: warm the cache, go offline (network off and backend unreachable), reload: everything the product promises offline shows from cache. Make one of each write, close the tab, reconnect: each write lands exactly once. Measure the latency to the other user with a realtime listener.layout: 320 px, a tablet, a desktop, 200% zoom, portrait and landscape. Screenshot each key screen.
Evidence and cleanup
- Capture screenshots with
capture-screenshots(states × sizes × settings, each one looked at), plus numbers (row counts, latencies). - Report each criterion as pass / fail / not verified (why). Never round "not verified" up to "pass".
- File tickets for anything found that's outside the task's scope.
- When another agent or session continues from here, write a
handoffwith these results. - Stop everything you started (dev server, browsers, local stack, listeners) and reset changed settings. Leave alone what you didn't start.
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.

