agentleFS
Sign inStart free
loganware05loganware05/captains-compass-cursor/.cursor/rules/01-plan-approval-gate.mdc

captains-compass-cursor / rules

Cursor rule2 starsChanged 31 days agoMITView on GitHub

Requires implementation-plan approval before product changes

The file

We split this 01-plan-approval-gate.mdc into the rules it gives an agent

7 rules. About 0 are common, 6 are distinctive, and 1 is 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.

  • 1

    Very specific

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

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

    Create or update IMPLEMENTATION_PLAN.md.

    line 10
  2. Distinctive:

    Stop before changing product implementation files.

    line 13
  3. Distinctive:

    Create or reference the issue.

    line 21
  4. Distinctive:

    Create a rollback checkpoint.

    line 22
  5. Distinctive:

    Create the feature branch and necessary worktrees.

    line 23
  6. Distinctive:

    If asked to skip the plan and implement immediately, refuse and create the plan first.

    line 26
  7. Distinctive:

    If scope expands materially during implementation, update the plan and return to the approval gate.

    line 28

≈ “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
01-plan-approval-gate.mdc
---
description: Requires implementation-plan approval before product changes
alwaysApply: true
---

For any request that changes product behavior:

1. Investigate the current implementation.
2. Identify requirements, assumptions, risks, and dependencies.
3. Create or update IMPLEMENTATION_PLAN.md.
4. Set its status to AWAITING APPROVAL.
5. Present the plan to the Captain.
6. Stop before changing product implementation files.

Implementation may begin only after explicit approval.

After approval:

1. Record the approval in IMPLEMENTATION_PLAN.md.
2. Set the plan status to APPROVED.
3. Create or reference the issue.
4. Create a rollback checkpoint.
5. Create the feature branch and necessary worktrees.
6. Begin implementation.

If asked to skip the plan and implement immediately, refuse and create the plan first.

If scope expands materially during implementation, update the plan and return to the approval gate.

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