Cursor
Add project MCP, agents, skills, and hooks to Cursor.
Canonical agent setup
Set up Planr with Cursor
Copy this complete prompt into Cursor. It previews repository changes, preserves existing configuration, verifies diagnostics, and stops before product work.
Set up Planr for Cursor in this repository. Perform setup only; do not implement product work.
1. Detect the current host, repository root, OS, available package manager, Planr binary path/version, existing Planr project, and existing client configuration. If network access exists, consult the stable Planr Agent Bootstrap page; if it does not, continue with these self-contained steps.
2. If Planr is missing, install the CLI only through a trusted supported method (prefer `brew install instructa/tap/planr` when Homebrew is available, otherwise the official GitHub Release installer), then run `planr --version` and report the resolved binary path.
3. This client needs no separate plugin step; the project installer owns its Planr agents and skills.
4. Run `planr project show --json`. If and only if no Planr project exists, infer a concise name from the repository and run `planr project init "<repository-name>"` once, without a client flag. This creates Planr project state without writing client integration files. Never reinitialize an existing project.
5. Run `planr install cursor --dry-run`. Explain every project path that would be reconciled. Then run `planr install cursor` only for project-scoped, non-conflicting changes. Preserve hand edits; never use `--force`, global MCP configuration, or a user-level install/deeplink without my explicit approval. Re-running setup must be idempotent.
6. Run `planr project show --json` and `planr doctor --client cursor --json`. Do not claim success unless the project is readable and diagnostics are reported honestly.
7. Return a compact setup receipt with: Detected client and repository root; Resolved Planr binary path and version; Existing or newly initialized Planr project; Project integration paths changed or left unchanged; Plugin and workflow-skill status; Structured doctor result; Reload or trust action still required; Exact next $planr prompt.
Reload guidance: Reload the Cursor window after setup so newly installed project agents and skills are discovered.
Exact next prompt after setup: Use $planr. Inspect this repository and tell me the verified next step.Expected integration artifacts
.cursor/mcp.json— Project MCP configuration (planr install).cursor/agents/planr-{worker,reviewer}.md— Project worker/reviewer agents (planr install).cursor/skills/planr*/SKILL.md— All ten workflow skills (planr install).cursor/hooks.json— Session and evidence hooks (planr install).cursor/hooks/planr-evidence-guard.sh— Fail-open evidence guard (planr install)
Success receipt
- Detected client and repository root
- Resolved Planr binary path and version
- Existing or newly initialized Planr project
- Project integration paths changed or left unchanged
- Plugin and workflow-skill status
- Structured doctor result
- Reload or trust action still required
- Exact next $planr prompt
Invoke: /planr
Reload: Reload the Cursor window after setup so newly installed project agents and skills are discovered.
First prompt: Use $planr. Inspect this repository and tell me the verified next step.
Technical details
Planr writes .cursor/mcp.json, Planr worker and reviewer agents, all ten workflow skills, and hooks. The preview also prints a Cursor deeplink for an intentional user-level MCP install.
Use --no-mcp when Cursor's MCP configuration is managed elsewhere; project agents, skills, and default hooks remain. Add --no-hooks to omit hooks too. Use --force only after reviewing generated-file changes. For a CLI-shaped prompt, run planr prompt cli --client cursor.
Continue with the shared Agent Prompt Recipes or full lifecycle. The recipe above is rendered from the typed contract shared with the Agent Quickstart, landing page, and verification.