Master-Planner / rules
Cursor rule0 starsChanged 5 months agoMITView on GitHub
Routes planning intent to the Master-Planner harness instead of Cursor native Plan mode
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,183 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 repository12 other files it gives its agents.
- .cursor/rules/001-planning-safety.mdcCursor rule
- .cursor/rules/002-source-discipline.mdcCursor rule
- .cursor/rules/003-anti-rationalization.mdcCursor rule
- .cursor/rules/004-memory-and-resume.mdcCursor rule
- doubt-researchSkill
- intake-interviewSkill
- master-plannerSkill
- plan-grillerSkill
- project-memorySkill
- security-rollbackSkill
- spec-drafterSkill
- task-decomposerSkill
The file
We split this 000-harness-bootstrap.mdc into the rules it gives an agent
3 rules. About 0 are common, 0 are distinctive, and 3 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.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 12
If the user wants to plan, architect, spec, design, or figure out how to build something — including /mp-plan, "how should we build", PRD, …
- Very specific: line 21
Use /mp-plan <intent> to start or continue planning.
- Very specific: line 23
Do not rely on bare /plan — on most Cursor builds it triggers the IDE's native Plan mode instead of this harness.
≈ “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.
Files
--- description: Routes planning intent to the Master-Planner harness instead of Cursor native Plan mode globs: * alwaysApply: true --- # Master-Planner Bootstrap This project has the Master-Planner harness installed under `.cursor/`. ## When planning is requested If the user wants to plan, architect, spec, design, or figure out how to build something — including `/mp-plan`, "how should we build", PRD, roadmap, or resume planning: 1. **Read** `.cursor/skills/master-planner/SKILL.md` immediately and follow its pipeline. 2. **Do NOT** switch to Cursor native Plan mode or use `CreatePlan` / `SwitchMode` to `plan` for project planning in this repo. That produces ephemeral Cursor UI plans, not durable harness artifacts. 3. Persist state under `.cursor/plans/<project>/` (`manifest.md`, `spec.md`, `tasks.md`, `context.md`). 4. Obey `001-planning-safety`: no production implementation before plan approval. ## Primary slash command Use **`/mp-plan <intent>`** to start or continue planning. Do **not** rely on bare **`/plan`** — on most Cursor builds it triggers the IDE's native Plan mode instead of this harness.
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
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.