Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
Expand Up @@ -4,7 +4,7 @@ Benny does not know how to start or drive every app. The user must configure one

Set its skill name in `control.skill_name`.

Set the completed user-facing feature map path in `control.feature_map_path`. Copy and fill [`feature-map.example.md`](./feature-map.example.md) outside `.cursor/automations/benny/` instead of editing the copied example.
Set the completed user-facing feature map path in `control.feature_map_path`. Copy and fill [`feature-map.example.md`](./feature-map.example.md) outside `.agents/automations/benny/` instead of editing the copied example.

If the skill, feature map, or a required capability is absent, ambiguous, or incomplete, repro and fix work must fail closed.

Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -2,7 +2,7 @@

Map every user-facing feature Benny may reproduce. Read the relevant section before driving the app. Keep this map at the user point of view. Discover internals and current code paths at runtime instead of freezing them here.

Copy this file outside `.cursor/automations/benny/`, for example to `.cursor/benny/feature-map.md`, and set `control.feature_map_path` to the copy. Pack refreshes must not overwrite it.
Copy this file outside `.agents/automations/benny/`, for example to `.agents/benny/feature-map.md`, and set `control.feature_map_path` to the copy. Pack refreshes must not overwrite it.

## Per-feature template

Expand Down
30 changes: 15 additions & 15 deletions automations/benny/.agents/skills/setup-benny/SKILL.md
Original file line number Diff line number Diff line change
Expand Up @@ -10,7 +10,7 @@ Before following this workflow, resolve the installed **poteto-mode** skill and

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/.agents/skills/setup-benny/SKILL.md`.
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 `.agents/automations/benny/.agents/skills/setup-benny/SKILL.md`.

Benny needs external configuration and two live Cursor automations.

Expand All @@ -20,7 +20,7 @@ Do not create or update an automation until the user explicitly asks. Never put

Do this before asking for Benny configuration and before drafting either automation prompt.

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/`.
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:

Expand Down Expand Up @@ -52,9 +52,9 @@ Do not count a skill loaded from the current session or a user-scoped plugin. Th

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.
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 the target project's `.agents/skills/` installation, `.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.
Tell the user that the target project's `.agents/skills/` installation, `.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.

Expand All @@ -65,11 +65,11 @@ 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:
Create user-owned copies outside `.agents/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`
- 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`

Expand Down Expand Up @@ -131,7 +131,7 @@ Do not use undocumented integration endpoints.

If the user wants reroutes or owner pings:

1. Copy `../triage-issue-reports/references/routing.example.md` outside `.cursor/automations/benny/`.
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.
Expand Down Expand Up @@ -168,7 +168,7 @@ For each automation:

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 `.cursor/automations/benny/`.
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. Draft the prompt. Do not call a Cursor backend.
6. Confirm that the copied pack and any referenced configuration files are committed in the same repository where the automation will run.
Expand All @@ -177,7 +177,7 @@ For each automation:
Draft this complete triage intent, filled from configuration:

- Name `benny-triage`.
- Read and follow `.cursor/automations/benny/.agents/skills/triage-issue-reports/SKILL.md` for every run.
- Read and follow `.agents/automations/benny/.agents/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.
Expand All @@ -188,7 +188,7 @@ Draft this complete triage intent, filled from configuration:
After the triage draft is complete, draft this complete repro and fix intent:

- Name `benny-reproduce`.
- Read and follow `.cursor/automations/benny/.agents/skills/reproduce-and-fix-issues/SKILL.md` for every run.
- Read and follow `.agents/automations/benny/.agents/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.
Expand All @@ -210,7 +210,7 @@ Finish configuration, routing, control-adapter, and feature-map validation. Then
For the existing triage automation, update:

- Name and description
- Direct instruction to read `.cursor/automations/benny/.agents/skills/triage-issue-reports/SKILL.md`
- Direct instruction to read `.agents/automations/benny/.agents/skills/triage-issue-reports/SKILL.md`
- New top-level Slack report trigger and source channel
- Slack thread read and reply capabilities
- Issue-tracker integration
Expand All @@ -219,7 +219,7 @@ For the existing triage automation, update:
For the existing repro automation, update:

- Name and description
- Direct instruction to read `.cursor/automations/benny/.agents/skills/reproduce-and-fix-issues/SKILL.md`
- Direct instruction to read `.agents/automations/benny/.agents/skills/reproduce-and-fix-issues/SKILL.md`
- Matching Slack trigger and source channel
- Repository and default branch
- Slack thread read and reply capabilities
Expand All @@ -239,7 +239,7 @@ Do not enable either automation until the thread-safety test passes after the ed

Use a test channel or a harmless test report.

Before testing, confirm that the target project's `.agents/skills/` installation, `.cursor/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.
Before testing, confirm that the target project's `.agents/skills/` installation, `.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:

Expand Down
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
# Routing map example

Copy this file outside `.cursor/automations/benny/`, for example to `.cursor/benny/routing.md`, and replace every placeholder. Point `routing.map_path` at the copy. Pack refreshes must not overwrite it.
Copy this file outside `.agents/automations/benny/`, for example to `.agents/benny/routing.md`, and replace every placeholder. Point `routing.map_path` at the copy. Pack refreshes must not overwrite it.

The triage skill treats this as data. A route needs evidence from the report or cause trace. A keyword match alone is not enough.

Expand Down
16 changes: 8 additions & 8 deletions automations/benny/FOR_AGENTS.md
Original file line number Diff line number Diff line change
Expand Up @@ -28,10 +28,10 @@ i want two cursor automations that work together in one slack issue channel.
- 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 this entire pack committed at `.agents/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 project's `.agents/skills/` installation 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 keep user-owned configuration, feature maps, routing maps, and secrets outside `.agents/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.

Expand All @@ -50,30 +50,30 @@ i want two cursor automations that work together in one slack issue channel.
- 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`](./.agents/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.
start from [`configuration.example.yaml`](./templates/configuration.example.yaml) and [`feature-map.example.md`](./.agents/skills/reproduce-and-fix-issues/references/feature-map.example.md). copy and fill them outside this pack, for example under `.agents/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/`.
3. merge the entire source pack into `<target-repository>/.agents/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 `.agents/skills/setup-benny/SKILL.md` exist in the target repository.
7. read and follow `.cursor/automations/benny/.agents/skills/setup-benny/SKILL.md` directly from the target repository.
7. read and follow `.agents/automations/benny/.agents/skills/setup-benny/SKILL.md` directly from the target repository.

codex has no `.cursor/settings.json`. resolve shared pstack dependencies from the target project's `.agents/skills/` installation. if those skills are absent, copy the pstack `.agents/skills/` tree into the target project. preserve unrelated files. do not write editor plugin settings.

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/.agents/skills/` to a plugin manifest or expect its files to appear in the slash-skill list.
if project-scoped plugins are unavailable or any shared dependency does not resolve, stop and explain what failed. do not add `.agents/automations/benny/.agents/skills/` to a plugin manifest or expect its files to appear in the slash-skill list.

tell me that the target project's `.agents/skills/` installation, `.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.
tell me that the target project's `.agents/skills/` installation, `.agents/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, draft the two prompts, one for triage and one for repro and fix. do not call a cursor backend. finish the triage draft before starting the repro draft.

paraphrase this intent and the finished configuration into each draft. the triage prompt must read and follow `.cursor/automations/benny/.agents/skills/triage-issue-reports/SKILL.md`. the repro prompt must read and follow `.cursor/automations/benny/.agents/skills/reproduce-and-fix-issues/SKILL.md`. use these repo-relative paths only after you confirm they are committed in the repository where the automation will run.
paraphrase this intent and the finished configuration into each draft. the triage prompt must read and follow `.agents/automations/benny/.agents/skills/triage-issue-reports/SKILL.md`. the repro prompt must read and follow `.agents/automations/benny/.agents/skills/reproduce-and-fix-issues/SKILL.md`. use these repo-relative paths only after you confirm they are committed in the repository where the automation will run.

for existing automations, do not call a cursor backend 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.
6 changes: 3 additions & 3 deletions automations/benny/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -7,9 +7,9 @@ the files in this directory are dormant setup and automation sources. they do no
## 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.
2. let setup merge this whole directory into the target at `.agents/automations/benny/`. it must preserve destination-only files and review conflicts instead of overwriting local edits.
3. let setup resolve pstack from the target project's `.agents/skills/` installation for shared dependencies. codex has no `.cursor/settings.json`.

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`](./.agents/skills/reproduce-and-fix-issues/references/feature-map.example.md).
5. commit the target project's `.agents/skills/` installation, `.cursor/automations/benny/`, and any secret-free configuration before enabling either automation.
4. keep user-owned configuration outside the copied pack, for example in `.agents/benny/`. adapt [`configuration.example.yaml`](./templates/configuration.example.yaml) and [`feature-map.example.md`](./.agents/skills/reproduce-and-fix-issues/references/feature-map.example.md).
5. commit the target project's `.agents/skills/` installation, `.agents/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.
4 changes: 2 additions & 2 deletions automations/benny/templates/configuration.example.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -39,14 +39,14 @@ tracker:
require_compensation_action: true

routing:
map_path: ".cursor/benny/routing.md"
map_path: ".agents/benny/routing.md"
owner_pings_default: false
allow_feature_owner_ping: false
allow_confirmed_regression_author_ping: false

control:
skill_name: "control-target-app"
feature_map_path: ".cursor/benny/feature-map.md"
feature_map_path: ".agents/benny/feature-map.md"
environment: "safe-test-environment-placeholder"
artifact_directory: "/tmp/benny-artifacts"
artifact_retention_hours: 24
Expand Down
2 changes: 1 addition & 1 deletion automations/benny/templates/reproduce-automation-prompt.md
Original file line number Diff line number Diff line change
Expand Up @@ -2,7 +2,7 @@

> Source material for the copied setup workflow. Paraphrase this intent into a drafted prompt after you confirm that the copied pack is committed in the repository where the automation will run. Do not call a Cursor backend.

Read and follow `.cursor/automations/benny/.agents/skills/reproduce-and-fix-issues/SKILL.md` for this run.
Read and follow `.agents/automations/benny/.agents/skills/reproduce-and-fix-issues/SKILL.md` for this run.

Configuration source. Include this repository-relative path only when it is committed in the same target repository. Otherwise paraphrase the configured values. Never use a plugin source or cache path:

Expand Down
2 changes: 1 addition & 1 deletion automations/benny/templates/triage-automation-prompt.md
Original file line number Diff line number Diff line change
Expand Up @@ -2,7 +2,7 @@

> Source material for the copied setup workflow. Paraphrase this intent into a drafted prompt after you confirm that the copied pack is committed in the repository where the automation will run. Do not call a Cursor backend.

Read and follow `.cursor/automations/benny/.agents/skills/triage-issue-reports/SKILL.md` for this run.
Read and follow `.agents/automations/benny/.agents/skills/triage-issue-reports/SKILL.md` for this run.

Configuration source. Include this repository-relative path only when it is committed in the same target repository. Otherwise paraphrase the configured values. Never use a plugin source or cache path:

Expand Down
Loading