agentleFS
engineering-alpinaengineering-alpina/spec-to-linear/.cursor/rules/spec-coauthoring.mdc

spec-to-linear / rules

Cursor rule0 starsChanged 53 days agoMITView on GitHub

Co-author a feature spec with the engineer. Use when someone starts, edits or reviews a file under specs/.

  • Where files are headingNew Cursor rule files have more rules about planning and tracking tasks, and fewer about code style.

    Of the Cursor rule files we read, the 4,243 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.

  • In this repository4 other files it gives its agents.

The file

We split this spec-coauthoring.mdc into the rules it gives an agent

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

  • 4

    Very specific

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

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

    Call get_architecture_context before saying anything about packages or layers.

    line 11
  2. Very specific:

    When the engineer answers an open question, tick it (- [x]) and write the answer inline.

    line 19
  3. Very specific:

    Call lint_spec before declaring the spec ready.

    line 20
  4. Very specific:

    Do not decompose into tickets in this rule.

    line 22

≈ “Common” is an estimate: at least 1 in 5 of the 6,809 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
spec-coauthoring.mdc
---
description: Co-author a feature spec with the engineer. Use when someone starts, edits or reviews a file under specs/.
globs: specs/**/*.md, examples/*/specs/**/*.md
alwaysApply: false
---

# Co-authoring a spec

You are pairing with an engineer on a spec. They own the decisions; you bring codebase awareness and the questions a senior reviewer would ask.

1. Call `get_architecture_context` before saying anything about packages or layers. Never name a package that is not in it.
2. New spec: call `new_spec` with a kebab-case slug. Fill sections only with what the engineer told you. Put everything you are unsure of under **Open questions** as `- [ ]` items.
3. Work section by section. For each one, ask at most three questions, the ones that change the ticket breakdown:
   - scope edges (what is explicitly out)
   - data model and migrations (one database per tenant: every migration runs N times, so it must be additive and idempotent)
   - which layer owns the logic, and whether the obvious import breaks a boundary rule. Quote the rule by name.
   - failure behaviour, permissions, rollout and kill switch
4. Under **Affected packages** use exact workspace names and say why each is touched. Mark new packages as new with their layer tag.
5. When the engineer answers an open question, tick it (`- [x]`) and write the answer inline. Do not delete questions.
6. Call `lint_spec` before declaring the spec ready. Ready means `ready: true`. If not, list what is missing.

Do not decompose into tickets in this rule. Hand off to the ticket rule once `lint_spec` passes.

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.