pstack: add Benny issue automation pack

pstack/.cursor-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
 	"name": "pstack",
 	"displayName": "pstack",
-	"version": "0.9.2",
+	"version": "0.10.0",
 	"description": "if you want to go fast, go deep first. pstack helps you write less, but higher quality code. rigorous agent workflows you can parallelize with confidence.",
 	"author": {
 		"name": "Lauren Tan"

pstack/README.md

@@ -26,6 +26,12 @@ type `/automate-me`. it mines your recent transcripts, drafts a `<your-name>-mod
 
 models are configurable too. type `/setup-pstack`. it detects the models you have access to and writes a small always-applied rule mapping each role (code, judgment, the review panels) to a model. every skill reads it and falls back to sensible defaults when the rule is absent, so you override only what you want.
 
+## automations
+
+pstack also ships a dormant [benny automation pack](./automations/benny/). benny triages slack issue reports, then reproduces and fixes confirmed bugs with real ui evidence. its files are not registered as slash skills.
+
+to set it up, point cursor at [`FOR_AGENTS.md`](./automations/benny/FOR_AGENTS.md). setup copies the pack into the target repository at `.cursor/automations/benny/`, enables pstack there for shared skills, and keeps user configuration outside the copied pack.
+
 ## usage
 
 use `/poteto-mode` at the start of a task. it reads your request, picks from a set of playbooks, and runs the other skills as the steps need them.

pstack/automations/benny/FOR_AGENTS.md

@@ -0,0 +1,89 @@
+# benny automation intent
+
+## what i want to automate
+
+i want two cursor automations that work together in one slack issue channel.
+
+### automation 1: triage issue reports
+
+- trigger: when someone posts a new top-level report in my configured source slack channel, i want this automation to start on that report and keep its original thread coordinates.
+- behavior: i want it to read the thread and attachments, classify the report as a bug or performance issue, feature request, question or feedback, or reroute, and trace the likely owning layer before routing.
+- tracker: i want it to search my configured tracker for duplicates, update a confident duplicate, and create a ticket only for a clear net-new bug.
+- tools: i want slack thread read and reply access, my configured tracker integration, and my optional routing map.
+- outcome: i want exactly one reply in the source thread with a short verdict and `[benny:bug]`, `[benny:performance]`, or `[benny:other]`. a bug or performance marker may include the tracker url.
+- boundary: i never want this automation to post a root message in the source channel.
+
+### automation 2: reproduce and fix confirmed bugs
+
+- trigger: i want this automation to start from the same new top-level report, or another supported trigger chosen during setup, then wait for the trusted triage marker in the original thread.
+- gates: i want it to stop when someone clearly owns the fix. if an existing pull request or merged commit may fix the report, i want verification instead of a competing change.
+- behavior: i want it to use my configured control adapter and feature map, reproduce the exact symptom twice through the real ui, and capture screenshots, video, and a read-only state cross-check.
+- fix: i want it to verify existing pull requests without authoring over them. after a confirmed repro, it may attempt one bounded root-cause fix, use tdd when the test is cheap, smoke the blast radius, and open a draft pull request only when before-and-after proof passes.
+- tools: i want slack thread read and reply access, repository and history access, draft pull request creation, my configured tracker, and my control adapter.
+- outcome: i want evidence and a verified result in the source or optional operations threads, plus an optional draft pull request. updates should be concise.
+- boundary: i never want this automation to post a root message in the source channel.
+
+### shared rules
+
+- i want the source channel and root thread coordinates to stay immutable for the whole run.
+- i treat utility and debug bots as evidence, not delegation or fix ownership.
+- i allow subagents to help, but they cannot post to slack or receive slack credentials.
+- i want this entire pack committed at `.cursor/automations/benny/` in the target repository. its `SKILL.md` files are direct automation instructions, not registered plugin skills.
+- i want pstack enabled through the target repository's committed `.cursor/settings.json` only for shared dependencies such as `how`, `why`, `tdd`, `unslop`, and the required principle skills.
+- i want each live automation prompt to read its committed operational file directly. i do not want plugin cache paths, copied excerpts, or slash-skill discovery.
+- i keep user-owned configuration, feature maps, routing maps, and secrets outside `.cursor/automations/benny/` so pack refreshes cannot overwrite them.
+- i want both automations to fail closed when channel coordinates, tracker access, the control adapter, or the feature map are missing or uncertain.
+- i want draft pull requests only. do not merge or deploy.
+
+### my configuration
+
+- source slack channel: `<channel>`
+- optional operations channel: `<channel or none>`
+- repository and default branch: `<repo>`, `<branch>`
+- tracker: `<type, team, project, labels, intake status>`
+- routing map: `<path or none>`
+- triage identity: `<slack identity>`
+- control skill: `<configured skill or adapter>`
+- feature map: `<committed same-repo path outside the copied pack, or behavior to paraphrase>`
+- models: `<triage, reproduce, code, media review>`
+- status emoji strings: `<seen, reproducing, reproduced, blocked, fixing, failed, pull request opened>`
+- budgets: `<polling, verdict wait, follow-up, repro, rejection, fix>`
+- optional bot token capability: `<none, file download, or editable operations status>`
+
+start from [`configuration.example.yaml`](./templates/configuration.example.yaml) and [`feature-map.example.md`](./skills/reproduce-and-fix-issues/references/feature-map.example.md). copy and fill them outside this pack, for example under `.cursor/benny/`. keep secret values in a secret manager or environment.
+
+## for the agent
+
+the human enters setup by pointing cursor at this file. do not look for or invoke a discovered benny slash skill.
+
+1. ask which repository will run the automations.
+2. treat the directory containing this `FOR_AGENTS.md` as the source pack.
+3. merge the entire source pack into `<target-repository>/.cursor/automations/benny/`.
+4. preserve every destination-only file. never delete unrelated files or overwrite user-owned configuration, feature maps, or routing maps.
+5. when an existing destination file at a source-managed path differs, review the diff and merge without discarding local edits. if ownership is ambiguous, stop and ask before replacing it.
+6. verify that the copied `FOR_AGENTS.md` and `skills/setup-benny/SKILL.md` exist in the target repository.
+7. read and follow `.cursor/automations/benny/skills/setup-benny/SKILL.md` directly from the target repository.
+
+i want you to merge this entry into the target repository's `.cursor/settings.json`:
+
+```json
+{
+	"plugins": {
+		"pstack": { "enabled": true }
+	}
+}
+```
+
+preserve every unrelated setting and plugin. preserve comments and valid jsonc syntax when the existing file uses jsonc.
+
+i want verification from a fresh agent rooted in the target repository. confirm that pstack's `how`, `why`, `tdd`, `unslop`, and the principle skills used by benny resolve in project scope. do not count skills loaded from the current session or a user-scoped install.
+
+if project-scoped plugins are unavailable or any shared dependency does not resolve, stop and explain what failed. do not add `.cursor/automations/benny/skills/` to a plugin manifest or expect its files to appear in the slash-skill list.
+
+tell me that `.cursor/settings.json`, `.cursor/automations/benny/`, and any referenced secret-free configuration must be committed before either automation is enabled. do not create or update an automation until i explicitly ask.
+
+for first-time creation, use built-in `/automate` once for triage and once for repro and fix. complete the draft review, approval, readiness check, and Automations editor handoff for the first automation before starting the second.
+
+paraphrase this intent and the finished configuration into each draft. the triage prompt must read and follow `.cursor/automations/benny/skills/triage-issue-reports/SKILL.md`. the repro prompt must read and follow `.cursor/automations/benny/skills/reproduce-and-fix-issues/SKILL.md`. use these repo-relative paths only after `/automate` confirms they are committed in the repository where the automation will run.
+
+for existing automations, do not use `/automate` to inspect or update them. validate the configuration, then use the concise field checklist in the copied setup file so i can edit each automation directly in its editor. do not create duplicates.

pstack/automations/benny/README.md

@@ -0,0 +1,23 @@
+# benny
+
+benny gives you two cursor automations for slack issue reports. one triages each report. the other reproduces confirmed bugs and may prepare a small draft fix.
+
+the files in this directory are dormant setup and automation sources. they do not appear as slash skills.
+
+## set it up
+
+1. point cursor at [`FOR_AGENTS.md`](./FOR_AGENTS.md) and name the target repository.
+2. let setup merge this whole directory into the target at `.cursor/automations/benny/`. it must preserve destination-only files and review conflicts instead of overwriting local edits.
+3. let setup enable pstack in the target repository's `.cursor/settings.json` for shared dependencies:
+
+```json
+{
+	"plugins": {
+		"pstack": { "enabled": true }
+	}
+}
+```
+
+4. keep user-owned configuration outside the copied pack, for example in `.cursor/benny/`. adapt [`configuration.example.yaml`](./templates/configuration.example.yaml) and [`feature-map.example.md`](./skills/reproduce-and-fix-issues/references/feature-map.example.md).
+5. commit `.cursor/settings.json`, `.cursor/automations/benny/`, and any secret-free configuration before enabling either automation.
+6. review each new automation draft or update existing automations in their editors. then send a harmless test report and verify every source-channel post stays in the original thread.