docs: add /sentry-get-started design brainstorm

[evanpurkhiser]

A working brainstorm for /sentry-get-started — the proposed single entrypoint that walks a user into whatever they actually need from Sentry through an agent, without burning their token budget guessing.

The doc captures design principles (orient cheaply then let the user drive; close the loop by confirming events landed via MCP; aspire to do everything but be honest about current coverage), a cheap orientation probe, the tiered capability menu, and five flows (first error, add a signal, fix something, watch & alert, maintain). It also maps the gaps in the current skill set that this surfaces — most notably that setup never closes the loop today, and that the code-owned signals aren't reachable outside the SDK skills.

It's a flow-brainstorming artifact intended to become a flowchart and inform the actual skill/command work, not a final spec. Decisions made so far and still-open questions are tracked at the bottom.

[cursor]

MCP path skips orientation probe

Medium Severity

Step 0 requires re-running the full orientation probe after MCP connect/auth, but the master flowchart sends the post-connect path straight to ROUTE instead of back through PROBE. That omits the repo grep and find_projects signals needed for the new-vs-existing branch.

Additional Locations (1)

• GETTING-STARTED-DESIGN/index.md#L119-L120

 

^{Reviewed by Cursor Bugbot for commit c0fc04f. Configure here.}

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

There are 3 total unresolved issues (including 2 from previous reviews).

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit d545326. Configure here.}