Keep the inherit-parent/auto definition in setup-pstack (steps 1/3/4 and
the generated rule's header comment) and one poteto-mode clause; drop the
per-call-site resolution instructions from how, why, arena, architect,
reflect, and interrogate, restoring the compact configured-role pointers
with the current defaults. Make interrogate reviewer counts configurable:
the interrogate reviewers list sets the panel size and the Reviewer A/B/C
labels extend or shrink to the entry count. Bump 0.11.7 -> 0.11.8.
1. hillclimb.md: port steps 1-2 (workload grounding before choosing the
ruler; harness sensitivity proof before freezing), fold the how-skill
grounding into step 1 and rewrite step 4 to reference it.
2. refactoring.md: insert missing step 2 (name the structure the code is
missing per principle-model-the-domain), renumber 3-8, and restore the
"safety net" framing sentence in the intro.
3. feature.md + poteto-mode SKILL.md: expand the delegation scope and the
any-code trigger to choose the organizing structure per
principle-model-the-domain.
4. typescript-best-practices: restore the dropped "Real tests" and
"Structured telemetry" rules in generic form.
5. poteto-mode Subagents: add the difficulty tiering criteria (judgment vs
precisely specified vs trivial mechanical) and the setup-pstack rule
override semantics.
6. One-liner tells ported verbatim into bug-fix, runtime-forensics,
session-pickup, autonomous-run, and authoring-a-skill.
7. Bug fix: interrogate is "(multi-model adversarial)", not four-model;
the default panel is three models.
8. Leak fix: drop the dangling databricks-use-dbt-models skill reference
in why/references/sources/databricks.md.
Plus: arena cross-judge pool role line in setup-pstack, version bump to
0.11.3.
* pstack: add create-verification-skill and maintain-verification-skill
Generalizes the control-glass approach (feature map, doctor, proof
standards, harness-first) for any language or platform. The generator
interviews the repo, writes a project-local verify skill + seeded
feature map, and must prove its own output by running it once. The
maintainer is the upkeep loop: source wave per feature, one live pass,
at most one PR. setup-pstack gains an optional final step offering the
generator. Validated by 4 cloud agents generating against real repos
(go TUI, node CLI, HTTP service, full-stack web app) - all four proof
runs passed, and their friction reports drove 6 revisions.
* Address bugbot: frontmatter spec, teardown, launch-model deference, target discovery
* Rewrite live pass: per-session health checks, doctor-drift retry, per-failure cleanup, teardown after re-proof
## Summary
- add a dormant Benny source pack for thread-only issue triage and evidence-backed repro and fix workflows
- copy the pack into target repositories so live automations read committed files directly without exposing Benny as slash skills
- keep pstack enabled only for shared workflow dependencies and preserve user-owned configuration outside pack refreshes
## Test plan
- [x] `node scripts/validate-plugins.mjs`
- [x] validate the manifest exposes only `./skills/`, direct operational paths, Markdown links, JSON and YAML examples, frontmatter, and unique skill names
- [x] scan the branch for discovery contradictions, private names, IDs, credentials, endpoints, and local plugin paths
- [x] run `git diff --check origin/main...HEAD` and review the full branch diff
<!-- CURSOR_SUMMARY -->
---
> [!NOTE]
> **Low Risk**
> Documentation and dormant automation sources only; no runtime code paths in the plugin. Operational risk applies only after users enable automations with Slack, tracker, and repo write access in their own repos.
>
> **Overview**
> **Bumps pstack to 0.10.0** and documents a new **dormant Benny pack** under `automations/benny/` for Slack-driven issue workflows (not added to the plugin slash-skill manifest).
>
> The pack defines **two coordinated Cursor automations**: **triage** (classify reports, cause-aware routing, tracker dedupe, single thread reply with `[benny:bug]` / `[benny:performance]` / `[benny:other]`) and **repro/fix** (wait for trusted triage markers, double UI repro via a configured control adapter, verify existing PRs, optional bounded fix with **draft-only** PRs). Operational behavior lives in committed `SKILL.md` files with strict thread-only Slack rules, fail-closed gates, and coordinator-only posting.
>
> **Setup** is agent-driven via `FOR_AGENTS.md` and `setup-benny`: merge the pack into the target repo at `.cursor/automations/benny/`, enable **pstack** in `.cursor/settings.json` for shared skills (`how`, `why`, `tdd`, `unslop`, principles), keep user config outside the pack, and wire live automations through `/automate` (or editor updates for existing ones). Templates cover configuration, routing, feature maps, control-adapter contract, and prompt shims.
>
> <sup>Reviewed by [Cursor Bugbot](https://cursor.com/bugbot) for commit 1028dd3a69. Bugbot is set up for automated code reviews on this repo. Configure [here](https://www.cursor.com/dashboard/bugbot).</sup>
<!-- /CURSOR_SUMMARY -->
two new skills, a version bump, and README rows.
**`/recall`** rebuilds your recent working context on a topic from two records: your own chat history (mined in parallel by subagents) and the shared record the `why` skill searches (source control, issue tracker, chat, error tracking). hands back a tight current-state brief: a capsule, status-tagged threads, recurring problems, and the next move. explicit-invoke; composes `why` and `automate-me`.
**`/blast-radius`** maps what a change could break beyond the diff (consumers, dependency contracts, lifecycle and timing, serialized boundaries), then proves the one fact it's safe because of by running code instead of asserting it. includes a "how sure are you" trust ladder; any load-bearing safety claim that doesn't reach "ran it" is labeled unproven. explicit-invoke; composes `how`, `why`, `arena`, and `unslop`.
bumped to 0.9.2 and added both to the skills table.
<!-- CURSOR_SUMMARY -->
---
> [!NOTE]
> **Low Risk**
> Documentation and agent workflow definitions only; no application runtime or security-sensitive code paths change.
>
> **Overview**
> Ships **two new explicit-invoke skills** and bumps the plugin to **0.9.2**, with README table rows for when to use each.
>
> **`/recall`** adds a playbook for resuming work: scope a time window and topic, mine recent agent transcripts in parallel (with routing away from `session-pickup` / `automate-me`), optionally sweep the same shared evidence sources as **`why`** (rephrased toward current state and recurring failures), verify PRs/branches with `git`/`gh`, and return a fixed brief (capsule, status-tagged threads, problems, next move).
>
> **`/blast-radius`** adds a change-risk workflow beyond caller grep: identify the single load-bearing safety fact, hunt cross-boundary breakage (deps, lifecycle, wire formats), rate risks honestly, and **prove** safety via a trust ladder that requires runnable checks—unproven claims stay labeled; wide changes can use **`arena`**.
>
> Both skills set `disable-model-invocation: true` and compose existing skills (`why`, `how`, `unslop`, etc.); discovery is unchanged via `skills: "./skills/"`.
>
> <sup>Reviewed by [Cursor Bugbot](https://cursor.com/bugbot) for commit d7f9a4db02. Bugbot is set up for automated code reviews on this repo. Configure [here](https://www.cursor.com/dashboard/bugbot).</sup>
<!-- /CURSOR_SUMMARY -->
* pstack: per-role model configuration via /setup-pstack, drop codex
Makes pstack's model choices configurable per role instead of hardcoded.
- New /setup-pstack skill detects your available models and writes
~/.cursor/rules/pstack-models.mdc, an always-applied rule with one
line per role.
- poteto-mode gains a Model configuration section (default table and
precedence). Skills read the configured model per role and fall back
to the inline default when the rule is absent, so nothing breaks
with no setup.
- Review panels (arena, architect, interrogate, how critics) are now
config-driven and count-agnostic. One subagent runs per configured
model, with no fixed count or A/B/C/D labels.
- Dropped gpt-5.3-codex-high-fast. bug-fix and perf-issue default to
gpt-5.5-high-fast; feature and refactoring stay composer-2.5-fast.
Version bump to 0.8.0.
* pstack: keep model config out of poteto-mode
Drop the Model configuration section and table from poteto-mode. The
canonical defaults live in the setup-pstack rule shape, and each skill
already carries its inline default, so poteto-mode only needs a one-line
pointer in its Task defaults. Fixes the plan.md and setup-pstack
back-references to the removed section.
lauren tan's working style as a Cursor plugin. Bundles the poteto-mode
routing skill plus the workflow skills it routes through (how, why,
architect, arena, unslop, interrogate, automate-me, reflect, tdd) and
the full seventeen-skill set of first principles. Ships the poteto-agent
subagent that runs the same workflow end-to-end.
The why skill discovers available MCPs at run time and maps each to an
evidence category (source control, issue tracker, long-form docs,
real-time chat, infra observability, error tracking, analytics
warehouse). No third-party service integrations required.
cursor-team-kit's control-cli, control-ui, and deslop are referenced as
sibling-plugin dependencies for surfaces and commit cleanup; the kit
works standalone otherwise.
Marketplace entry registered at the root .cursor-plugin/marketplace.json.
lauren
