Source playbooks
Updated 2026-10-01
Source playbooks
Section titled “Source playbooks”The why skill spawns one investigator per available evidence category, each reading a single source-specific playbook below. The playbooks are concrete examples for common MCPs. Adapt them for a different MCP in the same category.
| Category | Playbook | Example MCP it documents |
|---|---|---|
| Source control history | code-archaeology.md |
git, gh |
| Issue / ticket tracker | linear.md |
Linear (adapt for Jira, GitHub Issues, Plane, Shortcut) |
| Long-form documents | notion.md |
Notion (adapt for Confluence, Google Docs, Coda) |
| Real-time team chat | slack.md |
Slack (adapt for Discord, Microsoft Teams, Mattermost) |
| Infrastructure observability | datadog.md |
Datadog (adapt for New Relic, Honeycomb, Grafana, Splunk) |
| Error / exception tracking | sentry.md |
Sentry (adapt for Rollbar, Bugsnag, Airbrake) |
| Product analytics warehouse | databricks.md |
Databricks SQL (adapt for Snowflake, BigQuery, ClickHouse, dbt) |
Cross-cutting:
incident-postmortem.md. Add this if the target code looks defensive (null checks, retry, timeout, rate limit, feature flag, egress guard, OOM handler).
This is an unofficial Chinese learning site for pstack. It is not affiliated with poteto. Translations follow the pstack/ directory in the cursor/plugins repository. This site does not ship a Chinese plugin. github.com/cursor/plugins