agentleFS
Sign inStart free
irwebtoolsirwebtools/Product-Skills/skills/product/validation/SKILL.md

validation

Skill0 starsChanged 2 months agoMITView on GitHub

Validate POC behavior with Product against acceptance criteria.

20 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

6 rules. 0 are common, 5 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 20 edited versions we read keep these.

  • 5

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use when the task matches: validation, product acceptance, preview review.

    line 10
  2. Distinctive:

    Keep Product validation and engineering verification distinct.

    line 39
  3. Distinctive:

    Do not claim completion without evidence.

    line 40
  4. Very specific:

    Do not treat PREVIEW_READY as production release.

    line 44
  5. Distinctive:

    Do not skip Product review by substituting automated tests.

    line 45
  6. Distinctive:

    Do not claim acceptance without named reviewer evidence.

    line 46

“Common” is measured: kept by at least 6 in 10 of the 20 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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

validation

When to use

Use when the task matches: validation, product acceptance, preview review.

Purpose

Record Product acceptance or rejection of demonstrated behavior.

Inputs

  • Runnable POC
  • Acceptance criteria
  • UX flow

Process

  1. Walk acceptance criteria with Product using the POC.
  2. Record who reviewed which revision and when.
  3. Separate Product validation from engineering verification.
  4. Send rejected behavior back to definition or UX as needed.

Outputs

  • Validation record
  • Accepted criteria
  • Rejected feedback
  • Revision requests

Verification

  • Confirm each output exists and is reviewable.
  • Keep Product validation and engineering verification distinct.
  • Do not claim completion without evidence.

Restrictions

  • Do not treat PREVIEW_READY as production release.
  • Do not skip Product review by substituting automated tests.
  • Do not claim acceptance without named reviewer evidence.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.

Check your setup, free