Cursor plugin specification and official plugins
TypeScript
Address swarm review feedback
Cursor Agent91dd7b711988
diff --git a/pstack/.cursor-plugin/plugin.json b/pstack/.cursor-plugin/plugin.jsonindex e0e6681f..f170fbd7 100644--- a/pstack/.cursor-plugin/plugin.json+++ b/pstack/.cursor-plugin/plugin.json@@ -1,7 +1,7 @@{"name": "pstack","displayName": "pstack",- "version": "0.11.15",+ "version": "0.11.14","description": "if you want to go fast, go deep first. pstack helps you write less, but higher quality code. rigorous agent workflows you can parallelize with confidence.","author": {"name": "Lauren Tan"diff --git a/pstack/skills/poteto-mode/SKILL.md b/pstack/skills/poteto-mode/SKILL.mdindex cff494c4..51a46341 100644--- a/pstack/skills/poteto-mode/SKILL.md+++ b/pstack/skills/poteto-mode/SKILL.md@@ -83,7 +83,7 @@ Read the leaf skill in full for any principle you apply. Each entry names when i## Subagents-**Use `subagent_type: "poteto-agent"` for any subagent you spawn inside a playbook step** (code-writing delegates, ad-hoc helpers). `/poteto-mode` and `poteto-agent` route through the same wrapper. Routed workflow skills (`how`, `why`, `interrogate`, `reflect`) set their own `subagent_type` for diverse-model review; respect what the skill prescribes, don't override to `poteto-agent`.+**Use `subagent_type: "poteto-agent"` for any subagent you spawn inside a playbook step** (code-writing delegates, ad-hoc helpers). `/poteto-mode` and `poteto-agent` route through the same wrapper. Routed workflow skills (`how`, `why`, `interrogate`, `reflect`, `swarm`) set their own `subagent_type` for diverse-model review; respect what the skill prescribes, don't override to `poteto-agent`.**Defaults for every `Task` call.** `run_in_background: true`, agent mode (readonly strips MCP), file pointers not inlined context, explicit model per role (configurable via `/setup-pstack`; defaults `grok-4.5-fast-xhigh` for code, `claude-fable-5-thinking-max` for prose and judgment). Code delegates tier by difficulty. The hardest changes (cross-cutting design, gnarly concurrency, subtle algorithms) go to your strongest judgment model (`claude-fable-5-thinking-max`) when the task needs judgment or the intent is vague, and to your strongest instruction-following model (`gpt-5.6-sol-max`) when the work is a precisely specified sequence of steps to execute to the letter; trivial mechanical edits go to your fast code model. Per-role lines in the `/setup-pstack` rule override these defaults and the model choices in the routed skills (`how`, `why`, `arena`, `swarm`, `architect`, `interrogate`, `reflect`); a role with no line keeps its default, and a role line of `inherit-parent` or `auto` runs that role on the parent chat model (omit Task `model`).diff --git a/pstack/skills/swarm/SKILL.md b/pstack/skills/swarm/SKILL.mdindex a84d4654..13f9a412 100644--- a/pstack/skills/swarm/SKILL.md+++ b/pstack/skills/swarm/SKILL.md@@ -20,14 +20,14 @@ Open a todolist with one entry per phase before launching anything.## Phase A: Frame1. State the done predicate and the artifact or report the swarm must return.-2. Choose the shape. Partition into slices, race N workers on identical briefs, or mix both.+2. Choose the shape. Partition into slices, race N workers on identical briefs, or mix both. For a race or mixed shape, declare `first pass`, `rank all`, or `best-of` before spawning.3. Set N from the user or derive it from the shape. N is total workers, not the cloud concurrency limit.4. Pick the worker model from `swarm workers` in `~/.cursor/rules/pstack-models.mdc` when present. Otherwise use `grok-4.5-fast-xhigh`. For a model race, name each arm's model up front.5. Give each worker its own writable output when it writes. Use a worktree, branch, or `/tmp/swarm-<slug>/worker-<n>/`.## Phase B: Fan out-Spawn workers with `subagent_type: generalPurpose`, `environment: "cloud"`, `run_in_background: true`, and the configured model. Use `environment: "local"` only when the worker needs access to something on the user's computer.+Spawn all N workers in one message with `subagent_type: generalPurpose`, `environment: "cloud"`, `run_in_background: true`, and the configured model. Use `environment: "local"` only when the worker needs access to something on the user's computer.When a worker must start from a non-default pushed branch, pass `cloud_base_branch`.