validate-delivery
Skill14 starsChanged 5 days agoMITView on GitHub
Use when the person and the agent go over what was just delivered together, live: on execute-plan's recommendation at a plan's close, or whenever the person asks to walk or rework a delivery with the agent. Runs the project's verify skill with the person guiding it, judging and deciding, the agent proposing what to check. Not for the agent's quality pass alone (the project's verify skill).
2 other projects use a version of this.
Adopted by
Most recently taken up by
- Ovich/swarmstormword for word, first seen Oct 25, 2026
- matiesmengo/spec-driven-design-blackjacktheir own version, first seen Apr 20, 2026
Other versions2 projects use a version of this.
Word for word · 1
- Ovich/swarmstorm★ 14100% same
Edited · 0
None found.
Wrote their own version · 1
- matiesmengo/spec-driven-design-blackjack★ 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 repository34 other files it gives its agents.
- AGENTS.mdAGENTS.md
- brainstormSkill
- brainswarmSkill
- interviewSkill
- whiteboard-defenseSkill
- complexity-reworkSkill
- deepen-moduleSkill
- dependency-graphSkill
- simplify-reworkSkill
- simplifySkill
- write-diagramsSkill
- aiviewSkill
- swarm-boardSkill
- execute-planSkill
- long-horizonSkill
- orchestrate-planSkill
- guide-complexitySkill
- guide-createSkill
- guide-deepen-moduleSkill
- helpSkill
- next-stepSkill
- orchestrateSkill
- cold-readSkill
- write-planSkill
- roadmapSkill
- technical-writingSkill
- write-conventionsSkill
- pr-reviewSkill
- recurring-review-findingsSkill
- swarmSkill
- design-prototypeSkill
- point-atSkill
- verification-skill-createSkill
- create-workbenchSkill
The file
Files
Validate a delivery
No verify-<app>-<focus> skill in the project's local skills: do not start. Say so and propose generating it first through the verification-skill-create skill.
Run the project's verify process with the person guiding it. The verify skill's steps, on the delivery's branch at its head, taken together one part at a time. The person decides where to go next and what holds; the agent drives the app and proposes.
- Propose what to check next: the parts the delivery touched, the journeys and hidden states the verify skill and its map know, what you would look at first and why. The person picks, or goes elsewhere.
- Show it in the watched browser or the right tool, and say what you see against the specification.
- The appreciation is the person's. Your own verdict is a recommendation beside theirs.
- A change they want is made at once and shown before moving on. One that changes a decision is a row of the plan's decisions; one too large for the session becomes a task.
Whether the slot is done is the person's call.
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.