Skip to content

fix(pstack): handle tiny known bug fixes inline #363

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
zhanfeng-alpha wants to merge 3 commits into
base: main
Choose a base branch
from
+13 −1
Open

fix(pstack): handle tiny known bug fixes inline #363

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
29ba8ad
fix(pstack): handle tiny known bug fixes inline
Sep 11, 2026
67b8ddd
fix(pstack): route delegated tasks only to poteto-agent
Sep 11, 2026
9eaeaf1
fix(pstack): restore Cursor-native subagent routing
Sep 11, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions pstack/skills/poteto-mode/SKILL.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -14,6 +14,8 @@ reminder: New task? Playbook match or rigor needed -> apply /poteto-mode. Casual

The Principles section below grounds every trigger. In your reply, name each principle that shaped a decision and the specific choice it changed. Cite only principles whose leaf SKILL.md you read this session.

For tiny known-mechanism bug fixes, use the [inline fast path](playbooks/bug-fix.md) instead of the fanout triggers below. Laziness and subtraction take precedence over routine delegation. Use subagents for real parallel investigation or large diffs, not as the default for tiny known fixes.

Remaining triggers:

- Nontrivial change, architecture decision, or "are we sure?" → the **how** skill.
Expand Down
12 changes: 11 additions & 1 deletion pstack/skills/poteto-mode/playbooks/bug-fix.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,6 +1,16 @@
### Bug fix

**You own this task. Plan, review, verify.** Delegate investigation and the fix to subagents, stay in the lead.
**You own this task. Plan, review, verify.** Choose the path by the surviving mechanism and the scope of the fix.

#### Tiny known-mechanism fast path

When evidence already establishes the surviving mechanism and the fix is about one predicate or a few-line local change, the parent edits and verifies inline. Do not fan out `how`, `why`, `architect`, `worker`, or `reviewer`, including a parallel worker+reviewer workflow. This path overrides the general delegation and function-boundary triggers.

Use the existing evidence, make the smallest fix, and run the focused repro and relevant checks yourself. Commit the fix with its regression test when applicable. Do not require a failing-test-first commit, approval of test order, or confirmation that the diff is frozen for review. Run **Opening a PR** without adding a delegation gate. Report the mechanism, changed lines, and verification results.

#### Full scientific path

Use this path when the mechanism is unknown or the change is cross-cutting. Delegate investigation and the fix to subagents, stay in the lead. A larger local fix with a known mechanism can reuse the evidence and follow the applicable steps without reopening the investigation.

Be scientific. Every shipped line traces to runtime evidence. Belt-and-suspenders that "might help" is a hypothesis, not a fix. It does not ship. When evidence refutes a hypothesis, revert what it motivated. The smallest change the evidence justifies ships, nothing more.

Expand Down