Cursor plugin specification and official plugins
TypeScript
Clarify ownership of autonomous run discoveries (#170)
laurenba7b5907843e
diff --git a/pstack/.cursor-plugin/plugin.json b/pstack/.cursor-plugin/plugin.jsonindex 1f355c96..8c035b8b 100644--- a/pstack/.cursor-plugin/plugin.json+++ b/pstack/.cursor-plugin/plugin.json@@ -1,7 +1,7 @@{"name": "pstack","displayName": "pstack",- "version": "0.11.9",+ "version": "0.11.10","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/playbooks/autonomous-run.md b/pstack/skills/poteto-mode/playbooks/autonomous-run.mdindex 6bac6a05..bc68ad73 100644--- a/pstack/skills/poteto-mode/playbooks/autonomous-run.md+++ b/pstack/skills/poteto-mode/playbooks/autonomous-run.md@@ -6,7 +6,8 @@2. Pick the wake mechanism using Cursor's `/loop` command (a built-in, not a pstack skill). An event to watch (CI, a merge, a ref advancing) gets a watcher subagent that wakes you on the event, with a long time-based heartbeat as fallback. No event gets a fixed-interval heartbeat sized to when the result is worth re-checking.3. Each iteration makes the smallest change the evidence justifies, verifies it against the predicate, commits if it advanced, discards changes that didn't help. Belt-and-suspenders that "might help" gets reverted, not left to ride.Sequence the work via the **sequence-verifiable-units** principle skill, verifying each unit before the next instead of batching checks at the end.-4. Checkpoint every iteration via the **show-me-your-work** skill, a row for what changed and whether the predicate moved. A run with no trail can't be audited or resumed.-5. Stop when the predicate is met. A plateau is not a stop, so keep going and pivot your approach to push past it. Surface a genuine dead end rather than spinning, and never relax the predicate to declare victory.+4. Mid-run discoveries are yours. Address broken skills, related bugs, flaky verifiers, review noise, tooling failures, orphaned follow-ups, and fixable drift yourself via poteto-mode. Put out-of-band fixes in their own PR. Do not park reversible work for the human or use `AskQuestion`. Surface only irreversible actions, genuine product or preference calls no experiment can settle, or a real dead end. Keep the predicate as the main drive, and return to it after each side fix.+5. Checkpoint every iteration via the **show-me-your-work** skill, a row for what changed and whether the predicate moved. A run with no trail can't be audited or resumed.+6. Stop when the predicate is met. A plateau is not a stop, so keep going and pivot your approach to push past it. Surface a genuine dead end rather than spinning, and never relax the predicate to declare victory.**Reply:** the exit condition, iterations run, what landed, what was discarded, final predicate state.