agentleFS
Sign inStart free
joinwell52-AIjoinwell52-AI/CodeFlowMu-open/skills/pm-acceptance-criteria/SKILL.md

pm-acceptance-criteria

Skill2 starsChanged 4 months agoMITView on GitHub

Convert "done" into checkable CodeFlowMu acceptance criteria. Use before PM dispatch, PM review, QA verification, or ADMIN closure to define functional, file, behavior, evidence, and forbidden-item checks.

The file

We split this skill into the rules it gives an agent

8 rules. About 0 are common, 6 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈6

    Distinctive · estimate

    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
  1. Distinctive:

    Use this skill before sending work downstream or when reviewing a REPORT.

    line 10
  2. Distinctive:

    Keep lifecycle acceptance separate from business acceptance.

    line 17
  3. Very specific:

    Use the checklist in docs/skills/pm-playbook/acceptance-criteria.md.

    line 21
  4. Distinctive:

    Do not treat lifecycle state as business acceptance.

    line 25
  5. Distinctive:

    Do not accept completion without evidence.

    line 26
  6. Distinctive:

    Do not archive automatically.

    line 27
  7. Distinctive:

    Do not delete audit files.

    line 28
  8. Very specific:

    Do not add adopted-pending 0003.

    line 29

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “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

PM Acceptance Criteria

When to use

Use this skill before sending work downstream or when reviewing a REPORT.

Rules

  • Make acceptance checkable.
  • Include function, file, behavior, evidence, and forbidden item checks.
  • Require REPORT evidence when work claims completion.
  • Keep lifecycle acceptance separate from business acceptance.

Required output

Use the checklist in docs/skills/pm-playbook/acceptance-criteria.md.

Forbidden actions

  • Do not treat lifecycle state as business acceptance.
  • Do not accept completion without evidence.
  • Do not archive automatically.
  • Do not delete audit files.
  • Do not add adopted-pending 0003.

Minimal example

- [ ] JSON parses
- [ ] Required SKILL.md files exist
- [ ] Existing pm.* IDs unchanged
- [ ] No Panel/API changes

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