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.
* maintain-verification-skill: cleanup granularity, re-doctor, evidence checks
Follow-up to the four bugbot comments that landed on #150 seconds
before merge: failed-drive cleanup now matches the granularity of what
failed (never tearing down a shared instance mid-pass), a failed drive
on a long-lived instance triggers re-doctor before the next feature,
the doctor-drift retry includes cleanup and relaunch, and every cleanup
is followed by an evidence-survival check.
* State the live-pass recovery rules as invariants, not enumerated procedures
* Restore the per-session doctor check inside invariant 1
* 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
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 -->
* poteto-mode: add the Hillclimb playbook
A generic, metric-agnostic scientific hill-climb loop. Fix a metric and a
stop predicate, freeze a measurement harness, keep a decision.tsv, and loop
one hypothesis at a time with before/after measurement, a regression gate,
and one commit per accepted win. The agent supervises and delegates the
attempts. Registered in the playbook list; perf-issue points here for
sustained work.
* setup-pstack: add the hillclimb model role
The Hillclimb playbook reads a configured hillclimb model. Group it with
bug-fix and perf-issue on the gpt-5.5-high-fast default so /setup-pstack
offers the choice and the playbook reference is not dangling.
* setup-pstack: split bug-fix, perf-issue, hillclimb into separate model lines
* hillclimb: scope the autonomous-run deferral to the wake mechanism, not its stop rule
* poteto-mode: drop the two-no-progress stop from Autonomous run; keep going past plateaus
The sequence-verifiable-units continuation landed after "Run Opening a PR",
which read as open-then-shape. Fold it into the rebase sentence so commit
shaping comes before the PR step. Bugbot flagged this after the original
change had merged.
* poteto-mode: extend Prototype playbook to empirical forks
Prototype was UI-only (layout/interaction, the eye is the test). Broaden
the trigger and steps 1/5 so a throwaway sketch can settle a behavioral
or timing fork by observation (which behavior, which timing, which
approach), not just a visual one. This is the destination the new
self-unblock trigger routes to.
* poteto-mode: route the AskQuestion reflex to a sketch
Before asking the human a which-approach / how-should-I / what-should-this-do
question, classify it. If the answer is empirical (observable by running
something), sketch it via the Prototype playbook and let the result decide;
reserve the ask for a genuine product or preference call. Wires Never Block
on the Human to Prototype, and broadens the Prototype catalog entry to match.
* poteto-mode: finish the Prototype empirical-fork broadening
Three gaps in the partial broadening. Step 3 still assumed a UI build, so
it now names the script path for a behavioral or timing decision. The Reply
still demanded screenshots, so it asks for the matching evidence instead.
The AskQuestion trigger had no read-only carve-out, so a cited-answer
Investigation no longer routes to a build.
* poteto-mode: add "sequence work into verifiable units" principle
New principle leaf plus its index entry in the Verification group. Break
multi-step work into small units that each end in a check, verify each
before the next, and stack commits and PRs so the sequence proves itself
to a reviewer (the failing test first, then the fix).
* poteto-mode: thread sequence-verifiable-units into playbooks
Reference the principle where it applies: the iterate-and-verify steps of
perf-issue and autonomous-run, the commit-staging steps of bug-fix,
feature, and refactoring, and the figure-it-out loop.
* 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.
* pstack: build-the-lever defaults to building the tool for any non-trivial work
* pstack: plain wording in build-the-lever Balance
* pstack: add gold-plating to unslop abstract-metaphor list
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
