agentleFS
aaronreneaaronrene/knowtation/.cursor/rules/build-verification-required.mdc

knowtation / rules

Cursor rule1 starsChanged 2 months agoMITView on GitHub

Mandatory build verification before marking Auto phases DONE (SD-3 honesty gate)

The file

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

5 rules. About 0 are common, 0 are distinctive, and 5 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 5

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    After any Auto build phase ({step}b, or any roadmap row with Model: Auto), before setting the phase to DONE in {{docs.roadmap_path}}:

    line 8
  2. Very specific:

    Run /build-verification-review (skill: .cursor/skills/build-verification-review/SKILL.md)

    line 11
  3. Very specific:

    Use thinking-high model — independent verifier posture.

    line 12
  4. Very specific:

    Before any Auto phase starts, the frozen spec must have pass freeze review (/freeze-review-loop when needed).

    line 19
  5. Very specific:

    Sibling (shipped / live-health claims only): when the session claims a live deploy, production health, or "shipped" outside the local repo, …

    line 24

≈ “Common” is an estimate: at least 1 in 5 of the 6,668 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
build-verification-required.mdc
---
description: Mandatory build verification before marking Auto phases DONE (SD-3 honesty gate)
alwaysApply: true
---

# Build verification — mandatory before DONE

After any **Auto** build phase (`{step}b`, or any roadmap row with **Model: Auto**), **before** setting
the phase to **DONE** in `{{docs.roadmap_path}}`:

1. Run **`/build-verification-review`** (skill: `.cursor/skills/build-verification-review/SKILL.md`)
2. Use **`thinking-high`** model — independent verifier posture; not the build session model
3. Compare the **frozen spec** (`frozen: true`) to the **actual diff**, tests, and claims in
   `{{docs.handover_path}}`
4. **Do not mark DONE** until verdict is **`pass`**
5. On **`findings`**: fix only cited path:line items; re-run verification (max 5 rounds per skill)
6. On **`blocked`** or escalation (`security`, `irreversible`, `real_money`, `gates_tier3`): stop for human

Before any **Auto** phase **starts**, the frozen spec must have **`pass`** freeze review
(`/freeze-review-loop` when needed).

Tests green alone is **not** sufficient for DONE.

**Sibling (shipped / live-health claims only):** when the session claims a live deploy, production
health, or "shipped" outside the local repo, also run **`/deploy-verification-review`**
(`.cursor/skills/deploy-verification-review/SKILL.md`). Do **not** run it for ordinary kit-only
Auto builds — that would false-close non-ship phases. Build verification is never waived.

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.