agentleFS
strikersamstrikersam/autonomous-ai-agency/.cursor/rules/verification.mdc

autonomous-ai-agency / rules

Cursor rule12 starsChanged 29 days agoMITView on GitHub

Binding verification rule for every agent (mirrored from CLAUDE.md §2)

The file

We split this verification.mdc into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    No "done" without an independent verifier (pstack): Before any task is reported done, by a coding agent or by an agency agent, a verifier …

    line 9

≈ “Common” is an estimate: at least 1 in 5 of the 6,873 Cursor rule 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
verification.mdc
---
description: Binding verification rule for every agent (mirrored from CLAUDE.md §2)
alwaysApply: true
---

The full ruleset is CLAUDE.md §1 and §2.

<!-- pstack-verification:start -->
49. **No "done" without an independent verifier (pstack).** Before any task is reported
    done, by a coding agent or by an agency agent, a verifier that did not write the
    change tries to break it. It exercises the real artifact (runs the feature, the
    tests, the built page; not "it compiles", not the author's own report) and returns
    `PASS`, `PASS+NOTES`, or `FAIL` with a report: what it checked, what it found broken,
    what was fixed, and the evidence (command output; screenshots for any UI change).
    `FAIL` sends the work back: fix every defect it found, then verify again, until it
    passes. Only `PASS` or `PASS+NOTES` permits a done claim, and the report quotes that
    verdict. Work in small units that each end in a check. Agency tasks enforce this in
    code (`tasks/verification.py`, live control `TASK_VERIFICATION_REQUIRED`). Source:
    pstack's `principle-prove-it-works` and its independent per-PR verdict
    (github.com/cursor/plugins/tree/main/pstack, github.com/michael-denyer/pstack-claude).
    This rule is mirrored byte-for-byte in every agent instruction file;
    `python scripts/check_verification_rule.py` fails if a copy drifts.
<!-- pstack-verification:end -->

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.