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 README fell behind recent merges. Add sequence-verifiable-units to the
principle index (nineteen to twenty), add the pause-safely playbook to the
table (fourteen to fifteen), and broaden the prototype one-liner to match
its empirical-fork scope.
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.
* fix: match root planner by exact name in kickoff dedupe
findActiveRootPlanner adopted any active cloud agent whose name merely
started with the kickoff slug (`name.startsWith(rootSlug)`). Because the
kickoff command names every root planner exactly `${rootSlug}-root`, a
slug that is a prefix of another goal's slug would wrongly adopt the
unrelated planner: kicking off goal `auth` while `auth-ui-root` is
active matched `"auth-ui-root".startsWith("auth")`, silently attaching a
fresh run to the wrong goal's planner instead of starting a new one.
Match the deterministic canonical name `${rootSlug}-root` exactly. Adds
a regression test asserting a prefix-only slug overlap does not adopt.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
* orchestrate: tighten kickoff-dedupe comments
---------
Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com>
Co-authored-by: lauren <lauren@anysphere.co>
* 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
The skill and agent originally landed in cursor-team-kit via PR #70
and were unintentionally removed when the Thermos plugin (PR #92)
relocated them. Restoring here so they remain available in team-kit
alongside the standalone Thermos plugin.
- Restore cursor-team-kit/skills/thermo-nuclear-code-quality-review/SKILL.md
using the cleaned-up version (no internal-only references) that
Thermos already ships.
- Restore cursor-team-kit/agents/thermo-nuclear-code-quality-review.md
verbatim from the original PR (points at the cursor-team-kit plugin
for skill lookup).
- Add the skill + agent rows back to cursor-team-kit/README.md and
remove the now-misleading "moved to Thermos" pointer.
Users installing both plugins will see the same skill name in two
places; this is a known overlap and is fine for now.
Co-authored-by: Cursor <cursoragent@cursor.com>
- Remove provenance sentence referencing Sualeh, the lukas-pr-review
internal skill, and the "Improve code quality" IDE feature name from
thermo-nuclear-code-quality-review.
- Rephrase thermo-nuclear-review description and intro to drop the
"web Deep review quick action" framing; describe the audit on its
own terms.
- Fix typo: memdium-to-high -> medium-to-high.
- Generalize the "Delete the database" example: drop the company name.
Co-authored-by: Cursor <cursoragent@cursor.com>
Thermos is a new plugin that packages thermo-nuclear branch review:
- thermo-nuclear-review (skill) — deep security/correctness audit
- thermo-nuclear-code-quality-review (skill) — harsh maintainability audit
- thermos (skill) — orchestrator that runs both reviews in parallel
with shared diff context and synthesizes findings
- Two Task subagents (one per review skill) for diff-scoped audits
The code-quality review previously lived in cursor-team-kit. Moved it
into Thermos alongside the new deep-review rubric so the two reviewers
sit together with their orchestrator. cursor-team-kit bumped to 1.2.0
with a pointer to the new plugin.
Marketplace and root README updated with the new entry.
Co-authored-by: Cursor <cursoragent@cursor.com>
lauren