/setup-benny

name: setup-benny
description: Configure Benny and prepare its triage and repro automations. Use when installing Benny or changing its Slack, tracker, repository, routing, control, model, or budget settings.
disable-model-invocation: true

Set up Benny

Benny ships as a dormant automation pack inside pstack. The plugin manifest exposes only pstack's normal skill root; this file and the two operational files are not slash skills.

The human enters setup by pointing Cursor at the pack's `FOR_AGENTS.md`. The bootstrap flow copies the whole pack into the target repository, then reads this file directly at `.cursor/automations/benny/skills/setup-benny/SKILL.md`.

Benny needs external configuration and two live Cursor automations.

Do not create or update an automation until the user explicitly asks. Never put a secret value in plugin files, prompts, or committed configuration.

1. Copy the pack and enable shared pstack skills

Do this before asking for Benny configuration and before invoking the built-in `/automate` skill.

Ask which repository will run the automations. The source pack is the directory containing `FOR_AGENTS.md`. The destination is `<target-repository>/.cursor/automations/benny/`.

Merge the entire source pack into the destination:

1. Create the destination when it is absent. 2. Copy every source file to the same relative path. 3. Preserve destination-only files. Never delete unrelated files during install or refresh. 4. Keep user-owned configuration, feature maps, and routing maps outside the destination. Never overwrite them. 5. When an existing source-managed file differs, inspect the diff and merge without discarding local edits. If ownership is ambiguous, stop and ask before replacing it. 6. Verify that the destination contains `FOR_AGENTS.md`, this setup file, both operational files, their references, and the templates.

If this file is already being read from the target destination, treat the copy as complete and run the same verification before continuing.

Add pstack to the target repository's `.cursor/settings.json`. If the file or `.cursor` directory does not exist, create it.

Merge this entry into the existing JSON or JSONC:

{
	"plugins": {
		"pstack": { "enabled": true }
	}
}

Preserve every unrelated top-level setting and every other plugin entry. If `plugins.pstack` already exists, change only its `enabled` value. Preserve comments and valid JSONC syntax when the file uses JSONC. Validate the file after editing it.

Reload the target project or start a fresh agent rooted there. Verify that these shared pstack skills resolve from project scope:

• `how`
• `why`
• `tdd`
• `unslop`
• `principle-separate-before-serializing-shared-state`
• `principle-minimize-reader-load`
• `principle-guard-the-context-window`
• `principle-sequence-verifiable-units`
• `principle-fix-root-causes`
• `principle-prove-it-works`

Do not count a skill loaded from the current session or a user-scoped plugin. The check must show that a fresh agent in the target repository receives pstack through project settings.

If project-scoped plugin installation is unavailable or any shared dependency does not resolve, stop and explain the failure.

The Benny files are read directly from `.cursor/automations/benny/`. Do not add that directory to a plugin manifest or expect its `SKILL.md` files to appear in the slash-skill list.

Tell the user that `.cursor/settings.json`, `.cursor/automations/benny/`, and any referenced secret-free configuration must be committed before either automation is enabled. Do not commit them unless the user asks.

Once this check passes, live automation prompts may read the committed operational files by their stable repository-relative paths. They must not embed a plugin cache path or copy the file contents.

2. Adapt the configuration

Open these copied examples:

• `../../templates/configuration.example.yaml`
• `../reproduce-and-fix-issues/references/feature-map.example.md`

Create user-owned copies outside `.cursor/automations/benny/`. These are configuration files, not pack files. Example locations:

• Project config, such as `.cursor/benny/configuration.yaml`
• Project feature map, such as `.cursor/benny/feature-map.md`
• Project routing map, such as `.cursor/benny/routing.md`
• User config, such as `~/.config/benny/configuration.yaml`
• User feature map, such as `~/.config/benny/feature-map.md`

Fill one feature-map section for every user-facing feature the automation may reproduce. Keep it at the user point of view. Do not freeze implementation details or current code paths in the map.

Do not edit the copied examples. Pack refreshes may update source-managed files after conflict review, but they must never touch the user-owned copies.

Prefer committed, secret-free files in the target repository when a fresh automation checkout must read them. Otherwise paraphrase the required values into the live prompt. Reference a repository file only after the built-in `/automate` skill confirms that the file is committed in the repository where the automation runs.

Use stable repository-relative paths for committed pack and configuration files. Never reference the plugin source directory or a plugin cache path from a live automation.

3. Fill the required choices

Ask for or confirm:

• Source Slack channel ID
• Optional operations or status channel ID
• Repository URL and default branch
• Triage identity or Slack user ID
• Issue tracker type, team, project, labels, and intake status
• Tracker adapter skill or MCP actions
• Optional routing map path
• Required control skill name
• Required user-facing feature-map path
• Status emoji strings
• Pull request URL format
• Polling and effort budgets
• Model slug for triage, repro, code work, and media review

Use only model slugs shown as available in the user's Cursor model picker or supported model list. Do not guess a slug and do not carry over a private default.

The source channel, triage iden