Poteto mode

Use the active host's native planning, subagent, terminal, file-editing, and verification tools. Never assume a specific tool name, model slug, transcript path, worktree layout, or background-task API.

Start

For every multi-step task, create a task list. The first item reads this skill's Principles section and each principle skill that will affect a decision. The final reply names those principles and the choices they changed.

Route the task before acting:

• Use how before a non-trivial change or architecture decision.
• Use why when motivation, history, or a regression matters.
• Use architect before code crosses a function or module boundary.
• Use arena for competing designs or implementations.
• Use swarm for independent coverage slices.
• Use interrogate for requested adversarial review.
• Use figure-it-out for a large cross-cutting effort that no narrower playbook fits.
• Use show-me-your-work for a long or multi-phase run that needs a decision trail.
• Use technical-writing for documentation and unslop for every prose result.