Setup Benny

Read Benny runtime preflight before this workflow.

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 the agent at the pack's FOR_AGENTS.md. The bootstrap flow copies the whole pack into the target repository, then reads this file directly at .agents/automations/benny/skills/setup-benny/SKILL.md.

Benny needs external configuration and two live host 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 live automation provisioning. Read the runtime preflight first.

Ask which repository will run the automations. The source pack is the directory containing FOR_AGENTS.md. The destination is <target-repository>/.agents/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.

After authorization, install PStack through native plugin controls: codex plugin add pstack@agent-kit on Codex or /plugin install pstack@agent-kit on Claude. Verify marketplace source and version first; a local unpublished port is not supplied by a remote marketplace. Do not write .cursor/settings.json.

A host install does not prove the upstream fresh-runtime delivery contract. Verify discovery in the actual automation runtime before claiming that guarantee.

Reload the target project or start a fresh agent rooted there. Verify that these shared pstack skills resolve in the actual fresh automation runtime:

• 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 alone. The check must show that a fresh automation agent in the target repository receives the installed PStack version and all required skills.

If the required project-scoped delivery guarantee is unavailable, the fresh automation runtime cannot load PStack, or any shared dependency does not resolve, stop and explain the failure.

The Benny files are read directly from .agents/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 .agents/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 .agents/automations/benny/. These are configuration files, not pack files. Example locations:

• Project config, such as .agents/benny/configuration.yaml
• Project feature map, such as .agents/benny/feature-map.md
• Project routing map, such as .agents/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 verifying 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 IDs and reasoning settings exposed by the actual host task or subagent tool used for that role. Use PStack's bundled model roles as starting choices; task and subagent availability can differ. Do not guess a slug or carry over a private default.

The source channel, triage identity, repository, tracker adapter, control skill, and feature map must be explicit. Fail setup if any required value stays ambiguous.

Use pstack's unslop skill on the final automation names, descriptions, and prompt shims before saving them.

4. Check integration capabilities

The triage automation needs:

• Read access to the configured source Slack channel and its threads
• Thread-reply access in that channel
• Attachment metadata and file download access when reports include media
• Search, read, create, and update access through the configured issue-tracker adapter

The repro automation needs:

• Read access to the source thread
• Thread-reply access in the source channel
• Optional post and edit access in the configured operations channel
• Repository read and history access
• A pull request action that can open a draft pull request
• The configured control-adapter skill

Prefer configured host Slack connector actions for reads and posts. The optional BENNY_SLACK_BOT_TOKEN may fill a narrow gap such as editing one operations status message or downloading an attachment. Store the value in a secret manager or environment, not in YAML.

Do not use undocumented integration endpoints.

5. Prepare the routing map

If the user wants reroutes or owner pings:

1. Copy ../triage-issue-reports/references/routing.example.md outside .agents/automations/benny/.
2. Replace every placeholder with public or organization-local values.
3. Keep owner pings off by default.
4. Allow a ping only for a configured feature owner or a confirmed likely regression author.

If no routing map is configured, triage may classify a report but must not guess a destination or owner.

6. Verify the control adapter

Read ../reproduce-and-fix-issues/references/control-adapter.md and the user's completed feature map.

Confirm that the named skill can:

• Bring up the target app
• Navigate every mapped feature through the real UI
• Exercise mapped states through declared adapter actions
• Inspect state without forcing the result
• Capture screenshots
• Start and stop a recording
• Clean up its processes and temporary data

If any capability is missing, leave the repro automation disabled. It must fail closed rather than claim a reproduction it did not perform.

7. Prepare the live automations

Ask whether this is first-time creation or configuration of existing automations.

Read ../../FOR_AGENTS.md from the copied pack as the primary user-intent source for either path. Use it to understand the two triggers, tools, instructions, outcomes, and shared rules.

First-time creation

Create one automation at a time.

For each automation, only after the runtime preflight proves native trigger support:

1. Read the matching copied prompt template as secondary internal source material.
2. Turn FOR_AGENTS.md, the finished Benny configuration, and the template intent into a complete natural-language request.
3. Tell the live prompt to read and follow its exact committed operational file under .agents/automations/benny/.
4. Use the stable repository-relative path, not a plugin source or cache path. Do not copy the operational file contents into the live prompt.
5. Discover the current native automation tool and read its schema.
6. Verify Slack channels, repository, and connected integrations using available tools.
7. Verify the copied pack and referenced configuration are committed in the repository where the automation will run.
8. Present the complete draft, verify existing authorization, and check readiness before enabling it.
9. Finish and read back this automation before starting the next one.

The current automation_update tool supports scheduled heartbeat and cron jobs, not Slack event triggers. Stop before creation; do not coerce either into this workflow.

Prepare this complete triage intent, filled from configuration:

• Name benny-triage.
• Read and follow .agents/automations/benny/skills/triage-issue-reports/SKILL.md for every run.
• Trigger on each new top-level report in the configured source Slack channel.
• Read the triggering thread and reply only inside it.
• Use the configured issue-tracker integration.
• Classify, inspect evidence, trace cause, dedupe, and create only clear new bugs.
• End one thread-only verdict with the configured [benny:bug], [benny:performance], or [benny:other] marker and optional tracker URL.
• Never post a source-channel root message.

After triage provisioning is supported and complete, prepare this complete repro and fix intent:

• Name benny-reproduce.
• Read and follow .agents/automations/benny/skills/reproduce-and-fix-issues/SKILL.md for every run.
• Trigger on the same new top-level reports in the configured source Slack channel.
• Use the configured repository and default branch.
• Read the source thread and reply only inside it.
• Include pull request creation and the configured tracker, control-adapter, and feature-map requirements. Paraphrase mapped user paths and states unless you verify an eligible committed file in the same repository.
• Wait for a trusted triage marker before acting.
• Reproduce the exact symptom twice through the mapped real UI and capture evidence.
• Verify an existing fix without authoring over it.
• Attempt an optional bounded fix only after confirmed repro, then open a draft pull request when proof and checks pass.
• Never post a source-channel root message.

Reuse native tool checks for Slack, repository, integration, completeness, authentication, draft review, authorization, readiness, and readback. Do not bypass missing capabilities.

Existing automations

Inspect the existing native automation before proposing an update. Preserve fields outside the requested change and do not create a duplicate. The current scheduler cannot represent the required Slack trigger; fail closed instead of changing the trigger to a schedule.

Finish configuration, routing, control-adapter, and feature-map validation. Then give the user this concise editor checklist.

For the existing triage automation, update:

• Name and description
• Direct instruction to read .agents/automations/benny/skills/triage-issue-reports/SKILL.md
• New top-level Slack report trigger and source channel
• Slack thread read and reply capabilities
• Issue-tracker integration
• Paraphrased triage instructions, thread-only rule, and Benny verdict markers

For the existing repro automation, update:

• Name and description
• Direct instruction to read .agents/automations/benny/skills/reproduce-and-fix-issues/SKILL.md
• Matching Slack trigger and source channel
• Repository and default branch
• Slack thread read and reply capabilities
• Pull request action
• Tracker, control-adapter, and feature-map requirements
• Paraphrased marker wait, evidence, verification, and bounded-fix instructions

Use only supported native update capabilities after authorization and the runtime preflight. Read back the exact updated automation. Do not create replacements or duplicates.

Creation boundary

Use the native automation tool only with arguments supported by its current schema. Do not call an undocumented backend, craft protocol links, create a trigger service, or substitute scheduled polling for Slack events. The current host cannot complete faithful provisioning.

Do not enable either automation until the thread-safety test passes after the editor save.

8. Test thread safety

Use a test channel or a harmless test report.

Before testing, confirm that the target repository's .agents/automations/benny/ and every referenced secret-free configuration file are committed on the branch used by the automation checkout. Confirm that both live prompts point at their exact committed operational files. If any check fails, stop. Tell the user that the automation cannot be enabled yet.

Verify:

1. Triage stores the root thread_ts and posts exactly one verdict as a reply.
2. The verdict contains one configured marker.
3. Repro accepts the marker only from the configured triage identity.
4. Repro keeps the same immutable source coordinates.
5. No source-channel root message appears.
6. A delegated worker cannot use any Slack write action.
7. Missing coordinates, a deleted parent, or a failed preflight produces no post and no tracker issue.

Enable normal traffic only after all seven checks pass.