agentleFS
Sign inStart free
VuDZVuDZ/RoslynMcpServer/.cursor/rules/roslyn-mcp-docs-lifecycle.mdc

RoslynMcpServer / rules

Cursor rule8 starsChanged 45 days agoMITView on GitHub

Archive finished specs; strip review junk before starting a spec

The file

We split this roslyn-mcp-docs-lifecycle.mdc into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

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

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

    Before implementing or editing docs/<topic>/:

    line 12
  2. Very specific:

    Look next to the canon for leftover process: review/, review-response/, arbitration/, or pre-arb epoch copies with the same names as the …

    line 14
  3. Very specific:

    If any sit on the live shelf, propose moving them to <topic>/_archive/ first.

    line 15
  4. Distinctive:

    When every epoch is accepted/shipped and UNRESOLVED / U-ARB gates for that series are closed or explicitly skipped, remind the user to …

    line 19
  5. Distinctive:

    Do not delete accepted/rejected review.

    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
roslyn-mcp-docs-lifecycle.mdc
---
description: Archive finished specs; strip review junk before starting a spec
alwaysApply: true
---

# Docs spec lifecycle

Index: [`docs/README.md`](docs/README.md). Canon vs process: `_archive/` inside the topic; closed series without contract → `docs/archive/`.

## Starting a spec

Before implementing or editing `docs/<topic>/`:

- Look next to the canon for leftover **process**: `review/`, `review-response/`, `arbitration/`, or pre-arb epoch copies with the same names as the live spec.
- If any sit on the live shelf, **propose** moving them to `<topic>/_archive/` first. Do not treat review as the spec. Do not move silently.

## Closing a series

When every epoch is accepted/shipped **and** UNRESOLVED / U-ARB gates for that series are closed or explicitly skipped, **remind** the user to archive:

- Still cited from ARCHITECTURE / product README as live contract → keep in `docs/`; archive only process.
- History only (no remaining contract) → `docs/archive/<topic>/` and update the tables in `docs/README.md`.

Do not delete accepted/rejected review. Do not rewrite specs “to match reality” after ship — copy facts into ARCHITECTURE / README and mark the design shipped.

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