Cursor plugin specification and official plugins
TypeScript
pstack: add skeptical-reviewer trigger and arena routing for multi-shape work (#116)
lauren97d645a60133
diff --git a/pstack/skills/poteto-mode/SKILL.md b/pstack/skills/poteto-mode/SKILL.mdindex a00df8cb..4f70a5f6 100644--- a/pstack/skills/poteto-mode/SKILL.md+++ b/pstack/skills/poteto-mode/SKILL.md@@ -21,6 +21,7 @@ Remaining triggers:- Before commit → the `deslop` skill from the `cursor-team-kit` plugin (`/deslop`).- Shipping UI / IDE / CLI → the matching control skill. `cursor-team-kit` publishes `control-cli` (CLIs and TUIs) and `control-ui` (browser / Electron / web UIs). For bug fixes, reproduce first on the same surface yourself; hand to the user only under the narrow Bug fix step 1 exception.- After opening a PR → Cursor's built-in **babysit** skill.+- Bugbot or the agentic security reviewer commented → skeptical posture. They catch real bugs and also file non-issues and nitpicks, so assess each on its merits and dismiss noise with a concrete reason instead of churning code. Triage fix / dismiss / ask via the built-in **babysit** skill.- Broken skill mid-task → fix it in its own PR. Don't block. Don't silently work around it.- Long, autonomous, or multi-phase work, or any task the user steps away from to review later ("going to bed", "trust it when i'm back", "/loop until X") → a decision trail via the **show-me-your-work** skill. Commit it when stakes need an auditable record; keep it local otherwise.diff --git a/pstack/skills/poteto-mode/playbooks/feature.md b/pstack/skills/poteto-mode/playbooks/feature.mdindex d53826b5..b1f545fd 100644--- a/pstack/skills/poteto-mode/playbooks/feature.md+++ b/pstack/skills/poteto-mode/playbooks/feature.md@@ -9,7 +9,7 @@- **Independent workstreams.** Disjoint files, services, or layers parallelize. Shared writes serialize.- **Shared mutable state.** Default to splitting the target (the **separate-before-serializing-shared-state** principle skill). Serialize only for real invariants.- **Smallest safe decomposition.** If one worker is best, name why.-4. Delegate code-writing to a `composer-2.5-fast` subagent with a specific scope (file paths, named data shape, success criteria); review its diff yourself. Mandatory: no skip-with-reason escape, and Laziness Protocol does not override it (the gain is review separation, not lines saved). You can spawn a subagent even though you are one; "the app is small" and "a subagent cannot spawn one" are both wrong. A subagent forbidden to spawn satisfies this by owning the diff directly with the same review separation; no "standing by" reply that waits on a nested agent. Comments per **Comments**. Surgical edits, re-ground against the source for upstream-derived files. Port shared-primitive improvements to all consumers and verify each. Commit liberally.+4. Delegate code-writing to a `composer-2.5-fast` subagent with a specific scope (file paths, named data shape, success criteria); review its diff yourself. When the implementation admits multiple valid shapes (error handling, abstraction layer, test structure), delegate via the **arena** skill instead so the runners surface the alternatives and the cross-judge guards the pick. Mandatory: no skip-with-reason escape, and Laziness Protocol does not override it (the gain is review separation, not lines saved). You can spawn a subagent even though you are one; "the app is small" and "a subagent cannot spawn one" are both wrong. A subagent forbidden to spawn satisfies this by owning the diff directly with the same review separation; no "standing by" reply that waits on a nested agent. Comments per **Comments**. Surgical edits, re-ground against the source for upstream-derived files. Port shared-primitive improvements to all consumers and verify each. Commit liberally.5. Verify on the matching surface. "Inconclusive" or wrong-surface is not a pass; flag it.6. Rebase into small, ordered commits; stack follow-ups.7. If the design is contested, `interrogate` before shipping.