From da148d863567e253a6e2be36196d16a389e11d0e Mon Sep 17 00:00:00 2001 From: Cursor Agent Date: Sun, 26 Jul 2026 09:03:43 +0000 Subject: [PATCH 1/2] Clarify ownership of autonomous run discoveries Co-authored-by: lauren --- pstack/.cursor-plugin/plugin.json | 2 +- pstack/skills/poteto-mode/playbooks/autonomous-run.md | 3 ++- 2 files changed, 3 insertions(+), 2 deletions(-) diff --git a/pstack/.cursor-plugin/plugin.json b/pstack/.cursor-plugin/plugin.json index 1f355c9..8c035b8 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.md index 6bac6a0..cb33f4e 100644 --- a/pstack/skills/poteto-mode/playbooks/autonomous-run.md +++ b/pstack/skills/poteto-mode/playbooks/autonomous-run.md @@ -7,6 +7,7 @@ 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. +5. Mid-run discoveries are yours. Fix broken skills, related bugs, flaky verifiers, review noise, tooling failures, and orphaned follow-ups yourself via poteto-mode. Give an out-of-band fix its own PR. Do not park reversible work for the human or use `AskQuestion`. Only surface irreversible actions, genuine preference calls, or a real dead end. Keep driving the exit predicate. +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. From 60a9b5303bec9fbb291b617ce1dc4b1e056df6a1 Mon Sep 17 00:00:00 2001 From: Cursor Agent Date: Sun, 26 Jul 2026 09:12:17 +0000 Subject: [PATCH 2/2] Reorder autonomous run discovery handling Co-authored-by: lauren --- pstack/skills/poteto-mode/playbooks/autonomous-run.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/pstack/skills/poteto-mode/playbooks/autonomous-run.md b/pstack/skills/poteto-mode/playbooks/autonomous-run.md index cb33f4e..bc68ad7 100644 --- a/pstack/skills/poteto-mode/playbooks/autonomous-run.md +++ b/pstack/skills/poteto-mode/playbooks/autonomous-run.md @@ -6,8 +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. Mid-run discoveries are yours. Fix broken skills, related bugs, flaky verifiers, review noise, tooling failures, and orphaned follow-ups yourself via poteto-mode. Give an out-of-band fix its own PR. Do not park reversible work for the human or use `AskQuestion`. Only surface irreversible actions, genuine preference calls, or a real dead end. Keep driving the exit predicate. +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.