poteto-mode

Orchestrates multi-step engineering work through playbooks, principles, and verified subagent delegation.

Updated Sep 2, 2026
One-click install
npx skills add https://github.com/jnyross/pstack-muse --skill poteto-mode-jnyross
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: poteto-mode
Source: https://github.com/jnyross/pstack-muse/tree/main/skills/poteto-mode
Command: npx skills add https://github.com/jnyross/pstack-muse --skill poteto-mode-jnyross

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires commander, and includes scripts (resource) and references (resource) components.

What problem does it solve? Multi-step engineering work with AI agents often drifts: unverified claims of done, bloated diffs, blocking questions to the human, and prose full of filler. This Skill enforces a disciplined operating style where every task routes to a named playbook, every change is verified against the real artifact, and every reply follows strict writing rules. ## Core Features & Use Cases - Playbook routing: Matches incoming tasks (bug fix, feature, investigation, perf issue, PR babysitting, shipping, autonomous runs, orchestration) to step-by-step playbooks under playbooks/ and executes their steps verbatim. - Principles system: Applies named engineering principles (model the domain, prove it works, fix root causes, sequence verifiable units, guard the context window) with mandatory citation of which principle drove each decision. - Subagent delegation with verification: Spawns background subagents with per-role model assignments, reviews their diffs directly, and requires runtime evidence before declaring work done. - Use Case: Ask the agent to fix a reported bug. It reproduces the bug on the real surface, binary-searches the root cause with runtime evidence, delegates the fix to a subagent, verifies the original repro now passes, and opens a PR with the failing repro committed before the fix. ## Quick Start Invoke poteto-mode on your next task by asking the agent to work in poteto mode, for example to investigate and fix a bug with full runtime verification.

Frequently Asked Questions about poteto-mode

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I use poteto-mode for a bug fix?

Invoke poteto-mode and describe the defect. The Bug fix playbook reproduces the bug on the matching surface, binary-searches the root cause with runtime evidence, delegates the fix to a subagent, verifies the original repro passes, and opens a PR.

What playbooks does poteto-mode include?

It ships playbooks for investigation, bug fix, perf issue, hillclimb, feature, refactoring, prototype, eval, babysit, shipping, autonomous run, orchestrate, autopilot-full, autopilot-stack, session pickup, multi-phase plans, and opening PRs, each with verbatim steps.

How does poteto-mode handle Bugbot or automated review comments?

It triages each comment skeptically using references/bugbot-triage.md, classifying it as fix, dismiss, or ask. Real findings get fixed in the lowest owning PR; noise is dismissed with a concrete reason rather than churning code.

Does poteto-mode work outside Cursor?

This repository is a Muse Code adaptation of the original Cursor pstack plugin. Cursor-specific features like model panels, /loop, and cloud agents do not apply in Muse; the skill bodies are otherwise upstream-verbatim.

When should I not use the babysit playbook?

Do not start babysitting when a PR is merely opened; it begins when the user asks to get a PR green or merge-ready. Requests to land or ship a stack route to the Shipping playbook instead, which verifies each PR independently.