Poteto mode

Bundled skills live at ../<name>/SKILL.md from this file, so put this file's absolute path in every poteto-agent prompt.

Platform Adaptation

These skills use Claude Code tool names (the Skill tool, the Agent tool, AskUserQuestion) and the Claude model names the Agent tool accepts, as each Models section lists them. On Claude Code they work as written. On Codex, read references/codex-tools.md for the Codex equivalent of a Claude tool, model, or skill named by these workflows. On Pi, read references/pi-tools.md instead. On GitHub Copilot, CLI or app, read references/copilot-tools.md instead. On Muse, read references/muse-tools.md instead. Other runtimes can discover the same Agent Skills tree, but they must use their own tool, model, and configuration equivalents. No one of these mappings is a cross-runtime map.

Use the session's task-tracking tools for the todolist. On Claude Code these are TaskCreate and TaskUpdate, or TodoWrite when configured. Availability depends on the model; CLAUDE_CODE_ENABLE_TODO_TOOLS=1 enables them through the environment or a project's .claude/settings.local.json env block. See the task-tool documentation. If no task-tracking tool is available, keep an uncommitted todo.md Markdown checklist in the work dir, next to the decision trail, with the playbook steps verbatim and each skip: <reason> line. When several sessions share the checkout, name it .audit/<task-slug>.todo.md, beside that session's .audit/<task-slug>.tsv trail, so they never write one file.

Non-negotiables

The Principles section below grounds every trigger. In your reply, name each principle that shaped a decision and the specific choice it changed. Cite only principles whose leaf SKILL.md you read this session.

Remaining triggers: