poteto-mode

Orchestrates engineering tasks through playbooks, principles, subagents, and verified PR workflows.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve? AI coding agents often produce unverified, bloated code with no engineering rigor. This Skill enforces a disciplined workflow where every task routes through a matched playbook, named engineering principles, delegated subagents, and runtime verification before any PR ships. ## Core Features & Use Cases - Playbook routing: Matches tasks (bug fix, feature, refactor, perf, investigation, babysit, shipping, autonomous runs) to step-by-step playbooks with mandatory verification gates. - Principle-driven decisions: Applies named principles like Laziness Protocol, Model the Domain, and Prove It Works, requiring each cited principle to trace to a real decision. - Subagent orchestration: Delegates code to model-tiered subagents (haiku, sonnet, fable) with swarm verification, PR size budgets, and review-bot triage. - Use Case: Ask the agent to fix a reported bug; it reproduces the defect on the real surface, binary-searches the root cause, delegates the fix, verifies the repro passes, and opens a right-sized PR. ## Quick Start Ask the agent to work in poteto mode on your next bug fix or feature, for example: use poteto-mode to investigate and fix the login timeout bug.

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 issue on the real 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 is the PR size budget in poteto-mode?▼

The default budget is 20 files and 800 added lines per PR, excluding lockfiles, snapshots, and vendored code. The check-pr-size script enforces it, and PSTACK_PR_MAX_FILES and PSTACK_PR_MAX_LINES environment variables override the defaults.

Does poteto-mode work with Graphite stacked PRs?▼

Yes. The Babysit, Shipping, and Autopilot playbooks use Graphite (gt) for stack registration, restacking, and merge-when-ready. The Shipping playbook independently verifies each PR before landing the contiguous verified run.

How does poteto-mode handle review bot comments?▼

It triages each comment from tools like Bugbot or /code-review as fix, dismiss, or ask using the bugbot-triage reference. Real findings get fixed in the lowest owning PR; noise is dismissed with a concrete disproof, never code churn.

When should I not use poteto-mode?▼

Skip it for casual conversational turns or when the user opts out. It is designed for tasks matching a playbook or needing engineering rigor, not for quick questions or trivial one-off edits.