Cursor

Prodscope ships as a native Cursor plugin with a marketplace entry. It bundles skills, rules, commands, and hooks that load automatically when the plugin is installed.

Install

Option A: Native plugin (recommended)

Clone the repo and copy the plugin files into your project. Cursor detects .cursor-plugin/plugin.json automatically:

git clone https://github.com/ashokdudhade/prodscope.git /tmp/prodscope
cp -r /tmp/prodscope/.cursor-plugin ./
cp -r /tmp/prodscope/rules ./
cp -r /tmp/prodscope/skills ./
cp -r /tmp/prodscope/hooks ./
cp /tmp/prodscope/mcp-config.json ./
mkdir -p .cursor/rules .cursor/commands
cp /tmp/prodscope/.cursor/rules/prodscope.md .cursor/rules/
cp /tmp/prodscope/.cursor/commands/prodscope-build.md .cursor/commands/
cp /tmp/prodscope/.cursor/commands/prodscope-verify.md .cursor/commands/

Option B: Shell installer

Run from your project root to copy all Cursor files automatically:

curl -fsSL https://raw.githubusercontent.com/ashokdudhade/prodscope/main/install.sh | bash -s -- --cursor-only

Option C: Remote rule (rules only)

For a lighter install without the full plugin, go to Settings → Rules → Add Rule → Remote Rule (GitHub) and paste:

ashokdudhade/prodscope

This loads the SRE rules but not skills, commands, or hooks.

Option D: Full install (all platforms)

curl -fsSL https://raw.githubusercontent.com/ashokdudhade/prodscope/main/install.sh | bash

Usage

The `/prodscope:build` command

Type /prodscope:build <task> in Cursor's chat to run the full Builder → Breaker → Verify → Score loop:

/prodscope:build "add rate limiting to the API"

You will see all four phases in a single response:

Builder — proposed diff + HEALTH_CHECK
Breaker — SRE review verdict (ACCEPT or REJECT)
Verification — smoke step evidence (or documented skips)
Reliability score — 1–10 rating

The `/prodscope:verify` command

After a build, run /prodscope:verify to check post-deploy signals via MCP integrations (Sentry, Datadog, etc.):

/prodscope:verify

This requires MCP servers configured in mcp-config.json. Without them it skips gracefully.

Always-on rules

Even without using /prodscope:build, the Composer rule at .cursor/rules/prodscope.md applies SRE skepticism to every interaction. It challenges:

Async / concurrency — race conditions, unbounded parallelism, missing cancellation
Data stores — missing indexes, N+1 queries, migration safety
Long-running processes — event listener leaks, growing caches, timer cleanup
Observability — can operators tell in production if a change breaks?

If a diff lacks verification steps, the rule prompts for a HEALTH_CHECK.

Files installed

.cursor-plugin/
  plugin.json              # Plugin manifest (with component paths)
  marketplace.json         # Marketplace entry for plugin discovery
.cursor/
  rules/prodscope.md       # Project-level rule (always-on SRE skepticism)
  commands/
    prodscope-build.md     # /prodscope:build command
    prodscope-verify.md    # /prodscope:verify command
rules/
  prodscope.mdc            # Plugin rule (.mdc format, auto-discovered)
hooks/
  hooks-cursor.json        # Cursor hook registration (sessionStart)
  session-start            # Session bootstrap hook
skills/
  using-prodscope/SKILL.md # Session bootstrap: when the loop runs
  builder/SKILL.md         # Builder instructions
  breaker/SKILL.md         # Breaker instructions
  verification/SKILL.md    # Evidence gate
  reliability/SKILL.md     # Reliability scoring
mcp-config.json            # MCP server placeholder (shared)
.prodscope/logs/           # Rejection/improvement logs (gitignored)

Session bootstrap

When a session starts, the sessionStart hook loads skills/using-prodscope/SKILL.md into agent context. This ensures the Builder-Breaker loop activates automatically for implementation tasks — you don't have to type /prodscope:build for every change.

How the plugin works

Cursor uses two layers to load Prodscope:

Plugin system

.cursor-plugin/plugin.json is the plugin manifest with explicit component paths. Cursor reads it to register Prodscope and discover:

Skills from skills/ — each subdirectory with a SKILL.md
Rules from rules/ — .mdc files with YAML frontmatter
Commands from commands/ — markdown files with YAML frontmatter

The marketplace entry at .cursor-plugin/marketplace.json enables discovery when the repo is used as a plugin source.

Project-level config

.cursor/rules/prodscope.md is loaded by Cursor's Composer automatically when the workspace is opened, providing SRE skepticism even if the plugin isn't formally installed. This acts as a fallback for lightweight installs.

Customizing

Add org-specific production checks by creating files in skills/breaker/checks/. These are automatically picked up during Breaker review. Keep rules thin — deep logic stays in skills/.