Poteto Mode

Orchestrates disciplined agent workflows with playbooks, subagents, and verified engineering principles.

2|Updated Jun 27, 2026
One-click install
npx skills add https://github.com/imjasonh/playground --skill poteto-mode-imjasonh
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: Poteto Mode
Source: https://github.com/imjasonh/playground/tree/main/.cursor/skills/poteto-mode
Command: npx skills add https://github.com/imjasonh/playground --skill poteto-mode-imjasonh

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 sloppy prose, unverified changes, and ad-hoc workflows. This Skill enforces a rigorous operating style for the agent: concise writing, deliberate subagent delegation, root-cause debugging, and evidence-backed verification before any work is declared done. ## Core Features & Use Cases - Playbook-driven execution: Routes tasks (bug fixes, features, refactors, investigations, perf work, PR babysitting, shipping, autonomous runs) to step-by-step playbooks with explicit verification gates. - Named engineering principles: Applies principles like Prove It Works, Fix Root Causes, Model the Domain, and Sequence Work into Verifiable Units to every code decision. - Subagent orchestration: Delegates code-writing to background subagents with per-role model selection, parallel fan-out, and swarm verification of merge-ready PRs. - 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 original repro passes, and opens a PR with a conventional-commit title. ## Quick Start Ask the agent to work in poteto mode on your next bug fix or feature and watch it follow the matching playbook end to end.

Frequently Asked Questions about Poteto Mode

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

FAQPage Schema
How do I make an AI coding agent verify its work before declaring done?▼

Poteto Mode requires verification against the real artifact rather than proxies like compilation. Each playbook ends with a verification step on the matching surface, and inconclusive or wrong-surface results are flagged instead of accepted.

How to delegate code changes to subagents with different models?▼

The Skill spawns background subagents with explicit per-role models, using a fast code model for mechanical edits and a strong judgment model for cross-cutting design. The parent agent reviews every diff and writes its own summary.

What playbooks does poteto mode include for PR workflows?▼

It includes Babysit for driving PRs to merge-ready, Shipping for landing verified stacks bottom-up, and Opening a PR for commit hygiene, conventional-commit titles, and structured PR descriptions. Autopilot playbooks handle queues of independent PRs.

Does poteto mode handle bugbot or automated review comments?▼

Yes, it triages each comment skeptically using a decision rubric in references/bugbot-triage.md. Comments are classified as fix, dismiss, or ask, with documented patterns for recurring false positives and escalation for security or data findings.

When should I not use poteto mode?▼

Skip it for casual conversational turns or when the user explicitly opts out, as the frontmatter reminder states. Its rigor overhead suits nontrivial changes, architecture decisions, and multi-step work rather than quick questions.