From 15d859c46fba26f189089e9f41615a71997badf9 Mon Sep 17 00:00:00 2001 From: Cursor Agent Date: Mon, 26 Oct 2026 03:15:17 +0000 Subject: [PATCH] fix: restore benny install paths and prompt drafts Copy the pack to .cursor/automations/benny and keep .cursor/benny for user config. Codex has no .cursor/settings.json, so shared skills come from the project's .agents/skills. Draft the two prompts instead of calling /automate. Co-authored-by: Kaitian Xie --- .../references/control-adapter.md | 2 +- .../references/feature-map.example.md | 2 +- .../benny/.agents/skills/setup-benny/SKILL.md | 112 +++++++++++++++--- .../references/routing.example.md | 2 +- automations/benny/FOR_AGENTS.md | 28 +++-- automations/benny/README.md | 15 ++- .../templates/configuration.example.yaml | 4 +- .../templates/reproduce-automation-prompt.md | 4 +- .../templates/triage-automation-prompt.md | 4 +- 9 files changed, 124 insertions(+), 49 deletions(-) diff --git a/automations/benny/.agents/skills/reproduce-and-fix-issues/references/control-adapter.md b/automations/benny/.agents/skills/reproduce-and-fix-issues/references/control-adapter.md index fa4096d..3399491 100644 --- a/automations/benny/.agents/skills/reproduce-and-fix-issues/references/control-adapter.md +++ b/automations/benny/.agents/skills/reproduce-and-fix-issues/references/control-adapter.md @@ -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 `.agents/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 `.cursor/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. diff --git a/automations/benny/.agents/skills/reproduce-and-fix-issues/references/feature-map.example.md b/automations/benny/.agents/skills/reproduce-and-fix-issues/references/feature-map.example.md index b06f5b0..620dded 100644 --- a/automations/benny/.agents/skills/reproduce-and-fix-issues/references/feature-map.example.md +++ b/automations/benny/.agents/skills/reproduce-and-fix-issues/references/feature-map.example.md @@ -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 `.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. +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. ## Per-feature template diff --git a/automations/benny/.agents/skills/setup-benny/SKILL.md b/automations/benny/.agents/skills/setup-benny/SKILL.md index 3be5b63..2807fd4 100644 --- a/automations/benny/.agents/skills/setup-benny/SKILL.md +++ b/automations/benny/.agents/skills/setup-benny/SKILL.md @@ -5,21 +5,22 @@ description: Configure Benny and prepare its triage and repro automations. Use w Before following this workflow, resolve the installed **poteto-mode** skill and read its `references/codex.md` adapter. Apply it to all tool calls, model choices, and automation steps below. + # 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 Codex 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`. +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`. -Benny needs external configuration and two live Codex automations. +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 configuring a live automation integration. +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 `/.agents/automations/benny/`. +Ask which repository will run the automations. The source pack is the directory containing `FOR_AGENTS.md`. The destination is `/.cursor/automations/benny/`. Merge the entire source pack into the destination: @@ -32,7 +33,7 @@ Merge the entire source pack into the destination: If this file is already being read from the target destination, treat the copy as complete and run the same verification before continuing. -Resolve shared pstack skills from the target project's `.agents/skills/`. If missing, copy pstack's full skill tree and its companion root `agents/` and `docs/` resources, preserving unrelated files and reviewing conflicts. Do not write editor settings or assume a personal installation will reach the runner. +Codex has no `.cursor/settings.json`. Resolve shared pstack skills from the target project's `.agents/skills/`. If missing, copy pstack's `.agents/skills/` tree into the target project, preserving unrelated files. Do not write editor plugin settings. Reload the target project or start a fresh agent rooted there. Verify that these shared pstack skills resolve from project scope: @@ -47,13 +48,13 @@ Reload the target project or start a fresh agent rooted there. Verify that these - `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 `.agents/skills/`. +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 the project's `.agents/skills/`. 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 `.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. +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 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. +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. 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. @@ -64,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 `.agents/automations/benny/`. These are configuration files, not pack files. Example locations: +Create user-owned copies outside `.cursor/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` +- 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` @@ -98,7 +99,7 @@ Ask for or confirm: - Polling and effort budgets - Model slug for triage, repro, code work, and media review -Use inherited models by default, or validated Codex model IDs and separate supported reasoning levels as described by the adapter. Do not guess a slug and do not carry over a private default. +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 identity, repository, tracker adapter, control skill, and feature map must be explicit. Fail setup if any required value stays ambiguous. @@ -122,7 +123,7 @@ The repro automation needs: - A pull request action that can open a draft pull request - The configured control-adapter skill -Prefer the connected Slack integration for reads and posts, within the user's explicit authorization. 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. +Prefer configured Cursor Slack 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. @@ -130,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 `.agents/automations/benny/`. +1. Copy `../triage-issue-reports/references/routing.example.md` outside `.cursor/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. @@ -155,17 +156,90 @@ If any capability is missing, leave the repro automation disabled. It must fail ## 7. Prepare the live automations -Read `../../../FOR_AGENTS.md` as the primary intent source. Use the copied templates to draft two prompts: `benny-triage` reads `.agents/automations/benny/.agents/skills/triage-issue-reports/SKILL.md`, and `benny-reproduce` reads `.agents/automations/benny/.agents/skills/reproduce-and-fix-issues/SKILL.md`. Both read the configured secret-free files and the installed pstack Codex adapter by a path available inside the runner checkout. Preserve all source-thread, identity, evidence, bounded-fix, and draft-only rules. +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: + +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/`. +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. +7. Finish this draft before starting the next one. + +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. +- 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 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. +- 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 an eligible file is committed 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. + +Do not call a Cursor backend. + +### Existing automations + +Do not call a Cursor backend to search for, inspect, or update existing automations. + +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 `.cursor/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 +- Paraphrased triage instructions, thread-only rule, and Benny verdict markers + +For the existing repro automation, update: + +- Name and description +- Direct instruction to read `.cursor/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 +- Pull request action +- Tracker, control-adapter, and feature-map requirements +- Paraphrased marker wait, evidence, verification, and bounded-fix instructions + +Ask the user to update each existing automation directly in its Automations editor. Do not create replacements or duplicates. + +### Creation boundary -Discover an actual automation integration or existing external event runner. Verify its API, repository checkout, Slack trigger, credentials, available tools, model settings, and run lifecycle. A Codex scheduled task alone does not receive arbitrary Slack events. If no suitable runner is available, leave activation pending and hand back the two drafts plus the exact missing capability. Do not call a Cursor service or fabricate an editor handoff. +Never call a direct automation backend service or backend automation tool. Never use a browser URL that carries draft fields. Never build or open a Cursor protocol deep link. For new automations, draft the two prompts. Do not call a Cursor backend. -For existing jobs, locate and update their actual IDs when authorized; do not create duplicates. For new jobs, finish one draft and any host-required review before creating the second. Create or update live jobs only when the user has explicitly requested it. Keep both disabled until the thread-safety test passes. Do not claim a trigger is active without an observed run from that trigger. +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 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. +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. Verify: diff --git a/automations/benny/.agents/skills/triage-issue-reports/references/routing.example.md b/automations/benny/.agents/skills/triage-issue-reports/references/routing.example.md index 193ea07..d71aea7 100644 --- a/automations/benny/.agents/skills/triage-issue-reports/references/routing.example.md +++ b/automations/benny/.agents/skills/triage-issue-reports/references/routing.example.md @@ -1,6 +1,6 @@ # Routing map example -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. +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. The triage skill treats this as data. A route needs evidence from the report or cause trace. A keyword match alone is not enough. diff --git a/automations/benny/FOR_AGENTS.md b/automations/benny/FOR_AGENTS.md index 8955fb4..ad80049 100644 --- a/automations/benny/FOR_AGENTS.md +++ b/automations/benny/FOR_AGENTS.md @@ -2,7 +2,7 @@ ## what i want to automate -i want two Codex-compatible automation jobs that work together in one slack issue channel. +i want two cursor automations that work together in one slack issue channel. ### automation 1: triage issue reports @@ -28,10 +28,10 @@ i want two Codex-compatible automation jobs that work together in one slack issu - 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 `.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 repository's committed the target project's `.agents/skills/` installation only for shared dependencies such as `how`, `why`, `tdd`, `unslop`, and the required principle skills. +- 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 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 `.agents/automations/benny/` so pack refreshes cannot overwrite them. +- 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. @@ -50,28 +50,30 @@ i want two Codex-compatible automation jobs that work together in one slack issu - budgets: `` - optional bot token capability: `` -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. +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. ## for the agent -the human enters setup by pointing Codex at this file. do not look for or invoke a discovered benny slash skill. +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 `/.agents/automations/benny/`. +3. merge the entire source pack into `/.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 `.agents/skills/setup-benny/SKILL.md` exist in the target repository. -7. read and follow `.agents/automations/benny/.agents/skills/setup-benny/SKILL.md` directly from the target repository. +7. read and follow `.cursor/automations/benny/.agents/skills/setup-benny/SKILL.md` directly from the target repository. -Resolve shared pstack dependencies from the target repository's `.agents/skills/`. If absent, copy the complete pstack `.agents/skills/` tree and companion `agents/` and `docs/` resources from this source. Preserve unrelated files and review conflicts. Do not write editor plugin settings. +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 `.agents/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 `.cursor/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, `.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. +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. -For live creation or updates, use an available documented host automation integration or the user's existing external event runner, following the copied setup file. A schedule does not itself provide a Slack event trigger. Never call a Cursor backend, invent an automation tool, or create duplicates. When an event runner is absent, prepare both prompt drafts and configuration and report activation as pending. +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. -Each triage prompt reads `.agents/automations/benny/.agents/skills/triage-issue-reports/SKILL.md`; each repro prompt reads `.agents/automations/benny/.agents/skills/reproduce-and-fix-issues/SKILL.md`. Include the installed pstack adapter path and the configuration path. Verify these files in the runner's actual repository checkout before activation. +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. + +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. diff --git a/automations/benny/README.md b/automations/benny/README.md index 9e8a488..3b55e05 100644 --- a/automations/benny/README.md +++ b/automations/benny/README.md @@ -1,16 +1,15 @@ # benny -benny gives you two Codex-compatible automation jobs for slack issue reports. one triages each report. the other reproduces confirmed bugs and may prepare a small draft fix. +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 Codex at [`FOR_AGENTS.md`](./FOR_AGENTS.md) and name the target repository. -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. resolve shared pstack skills from the target project's `.agents/skills/`, with companion `agents/` and `docs/` resources. No editor plugin settings are needed. -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. +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 resolve pstack from the target project's `.agents/skills/` installation for shared dependencies. codex has no `.cursor/settings.json`. -A live Slack trigger requires a documented external event runner or an available host integration with event support. Without one, setup prepares prompts and configuration and leaves activation pending. +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. +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. diff --git a/automations/benny/templates/configuration.example.yaml b/automations/benny/templates/configuration.example.yaml index 7faf568..8616f5f 100644 --- a/automations/benny/templates/configuration.example.yaml +++ b/automations/benny/templates/configuration.example.yaml @@ -39,14 +39,14 @@ tracker: require_compensation_action: true routing: - map_path: ".agents/benny/routing.md" + map_path: ".cursor/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: ".agents/benny/feature-map.md" + feature_map_path: ".cursor/benny/feature-map.md" environment: "safe-test-environment-placeholder" artifact_directory: "/tmp/benny-artifacts" artifact_retention_hours: 24 diff --git a/automations/benny/templates/reproduce-automation-prompt.md b/automations/benny/templates/reproduce-automation-prompt.md index 7551039..2637406 100644 --- a/automations/benny/templates/reproduce-automation-prompt.md +++ b/automations/benny/templates/reproduce-automation-prompt.md @@ -1,8 +1,8 @@ # Reproduce automation prompt -> Source material for the copied setup workflow. Paraphrase this intent into a built-in `automate` draft after `automate` confirms that the copied pack is committed in the repository where the automation will run. +> 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 `.agents/automations/benny/.agents/skills/reproduce-and-fix-issues/SKILL.md` for this run. +Read and follow `.cursor/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: diff --git a/automations/benny/templates/triage-automation-prompt.md b/automations/benny/templates/triage-automation-prompt.md index 0ad4de0..8450b5a 100644 --- a/automations/benny/templates/triage-automation-prompt.md +++ b/automations/benny/templates/triage-automation-prompt.md @@ -1,8 +1,8 @@ # Triage automation prompt -> Source material for the copied setup workflow. Paraphrase this intent into a built-in `automate` draft after `automate` confirms that the copied pack is committed in the repository where the automation will run. +> 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 `.agents/automations/benny/.agents/skills/triage-issue-reports/SKILL.md` for this run. +Read and follow `.cursor/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: