What problem does it solve?
Agent-driven coding work often drifts into vague plans, unverified claims, bloated prose, and unreviewed subagent output. Poteto Mode enforces a disciplined operating style where every task routes through a named playbook, every principle cited traces to a real decision, and every change is verified against the real artifact before shipping.
Core Features & Use Cases
- Playbook routing: Matches each task (bug fix, feature, investigation, perf, babysit, shipping, autonomous run, orchestration) to a step-by-step playbook whose steps are copied verbatim into the todolist.
- Principle system: Applies named engineering principles (model the domain, prove it works, laziness protocol, sequence verifiable units) with mandatory leaf-skill reading before citation.
- Subagent discipline: Routes delegates through poteto-agent with per-role model defaults, background execution, and mandatory diff review by the parent.
- Use Case: A user says "get this PR stack green and ship it". The agent declares a babysit mode, works the merge frontier, triages Bugbot comments skeptically, then hands off to the Shipping playbook which independently verifies each PR before landing the contiguous verified run.
Quick Start
Ask the agent to work in poteto mode on your next bug fix or feature, for example by saying "use /poteto-mode to fix this bug and ship it as a PR".