poteto-mode

Orchestrates multi-step coding workflows with playbooks, subagents, and verification gates.

Updated Jul 29, 2026
One-click install
npx skills add https://github.com/mmdmcy/fluttAIrbar --skill poteto-mode-mmdmcy
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: poteto-mode
Source: https://github.com/mmdmcy/fluttAIrbar/tree/main/plugins/pstack/skills/poteto-mode
Command: npx skills add https://github.com/mmdmcy/fluttAIrbar --skill poteto-mode-mmdmcy

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve? Complex agent-driven engineering work often lacks structure: tasks get planned ad hoc, verification is skipped, subagents are misused, and PRs ship without independent review. This Skill imposes a disciplined operating style with named principles, task-matched playbooks, and mandatory verification so multi-step work stays auditable and correct. ## Core Features & Use Cases - Task-matched playbooks: Routes work to dedicated playbooks for bug fixes, features, refactors, investigations, perf hillclimbing, PR babysitting, shipping, and autonomous runs. - Principle-driven decisions: Applies named engineering principles (model the domain, prove it works, sequence verifiable units, guard the context window) with required citations to the decisions they changed. - Subagent orchestration: Defines defaults for background subagents, per-role model selection, swarm verification, and adversarial multi-model review before shipping. - Use Case: A user asks to fix a reported defect. The Skill routes to the Bug fix playbook: reproduce on the real surface, binary-search the root cause, delegate the fix to a subagent, verify the original repro passes, then open a PR with staged commits. ## Quick Start Ask the agent to work in poteto mode on your task, for example by saying "use poteto-mode to fix this bug and open a PR".

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 coding task?▼

Invoke it by name or request work in this style. The agent starts a todolist, reads the principles, matches your task to a playbook such as Bug fix or Feature, and copies that playbook's steps verbatim before doing any task-specific work.

How does poteto-mode verify code changes before shipping?▼

It requires verification on the real surface the change touches, not just unit tests or compilation. Playbooks mandate reproducing bugs first, running live lanes through CLI or UI control tooling, and getting an independent swarm verdict before merging.

What playbooks are included in poteto-mode?▼

It ships playbooks for investigation, bug fix, perf issue, hillclimb, feature, refactoring, prototype, eval, babysit, shipping, autonomous run, orchestrate, autopilot variants, session pickup, multi-phase planning, and opening a PR.

How does poteto-mode handle subagents and model selection?▼

Every subagent runs in the background with file pointers instead of inlined context and an explicit model per role. Hard design work goes to a judgment model, precise mechanical steps to an instruction-following model, and trivial edits to a fast model.

When does poteto-mode pause to ask the human?▼

It proceeds autonomously on reversible work and only pauses for irreversible actions like force-pushes to shared branches, deploys, data deletion, or customer messages. Genuine product or preference decisions that no experiment can settle also go to the human.

What are the writing style rules in poteto-mode?▼

Replies and comments use short declarative sentences with one thought each. Long dashes and mid-sentence colons are banned, and comments are kept only for non-obvious rationale the code cannot express.