---
name: poteto-help
description: Guides users through pstack setup, $pstack:poteto-mode, and picking the skill, playbook, or principle for a task. Type $pstack:poteto-help with a question.
disable-model-invocation: true
---

# Poteto help

Answer the user's question about pstack, hand them a prompt they can send, and link the file the answer came from. For a help question, don't start the work. The user asked how, and a pstack run spends real tokens, so let them send the prompt.

A message that asks for work, such as "use pstack to fix this bug", is not a help question. Read [`poteto-mode`](../poteto-mode/SKILL.md), do the work under it, and mention once that attach `$pstack:poteto-mode` to each new task.

This file maps questions to the skills and guide pages that hold the answers. Those files own the details. Read the file you route to before you quote it, and trust it when it disagrees with this map. The links here point into the installed plugin, which the user may not be able to open, so give the user the file's public copy: `https://github.com/ScriptedAlchemy/pstack-t3code/blob/main/plugins/pstack/` followed by its path.

## Find out what they need

Infer the need from the message and the conversation. A named situation, such as "which skill reviews a PR?", goes straight to its section. If the need is still unclear, ask one multiple-choice question with these options, then answer only the section they pick:

- Get set up
- Start a task with `$pstack:poteto-mode`
- Pick a skill for a situation
- Fix a run that went wrong
- Make pstack my own

Check the state that changes the answer, and mention it only when it does:

- A missing models file uses server-resolved defaults. A missing required role in `<t3_pstack>` stops that spawn; configure choices with `$pstack:setup-pstack`.
- No `verify-*` skill or other app harness in the project means agents have no scripted way to drive the app. Mention `$pstack:create-verification-skill` when the question is about proving a change works.
- No formal verification skill in the project means no property is checked past what tests reach. Mention `$pstack:create-formal-verification-skill` when the question is about a race, an invariant, or another case tests rarely hit. When one exists and the code it covers changed after the commit it records as last in sync, mention `$pstack:maintain-formal-verification-skill` if the question touches that code.

When the models file is missing and it matters, ask whether the user wants to pick a model for each role and a reasoning budget now. It matters when the user is new, the question is about setup or cost, or the answer depends on which models run. Ask at most once per chat. If the need is also unclear, ask both questions together. Offer two choices:

- Now: give them `$pstack:setup-pstack` to type, and answer their question too.
- Later: answer their question, and add one line saying every role keeps its default model until they run `$pstack:setup-pstack`.

## Get set up

1. Use the T3-provided pack and `$pstack:` composer chips. The native pack must first be adopted at the server vendoring boundary; see the repository README.
2. Run [`$pstack:setup-pstack`](../setup-pstack/SKILL.md). It asks for a reasoning budget, maps a model to each role, and writes the environment models file. It applies on the next pstack invocation. Then it offers once each to generate a verification skill and a formal verification skill for the project, unless the project already has one.
3. Start a real task with `$pstack:poteto-mode`, a goal, and a check that can pass or fail.

Installing changes nothing until the user invokes a skill. Only `$pstack:setup-pstack` loads from the user's words. The [README](../../README.md) and [guide page 1](../../docs/guide/01-setup.md) have the details. Offer to word their first prompt with them, per [`references/prompting.md`](references/prompting.md).

If cost is the worry, say where the tokens go and how to spend fewer. pstack spends extra tokens on subagents and review panels. Rerun `$pstack:setup-pstack` and pick a smaller budget or cheaper models. A role set to `auto` or `inherit-parent` runs on the chat's model, which saves tokens when the chat runs on Auto or a cheaper model. A shorter panel list runs fewer subagents, one for each entry. Save `$pstack:poteto-mode` for work that needs rigor.

pstack runs through T3 Code's `$pstack:` composer chips and orchestration tools across its supported harnesses. Read bundled skills directly through the absolute pack path in `<t3_pstack>`. The native port needs no separate harness plugin installation. Configure roles with `$pstack:setup-pstack`.

Other tools can read the Agent Skills files. Executing these workflows requires T3 orchestration tools and a runtime `<t3_pstack>` block. Missing required targets stop the affected spawn; never reconstruct defaults or fall back to another harness's agents.

## Start a task with `$pstack:poteto-mode`

`$pstack:poteto-mode` matches the task to a playbook, copies the playbook's steps into the plan, and runs the other skills as the steps need them. A step it skips stays in the list as `skip: <reason>`. A good prompt states the goal and how to tell it's done. It doesn't list skills, because a hand-written sequence tends to drop or reorder steps the playbook would keep. Read [`references/prompting.md`](references/prompting.md) before you help word one. [Guide page 2](../../docs/guide/02-poteto-mode.md) has examples.

Attach `$pstack:poteto-mode` to each task. Mid-thread, "new task" selects a fresh playbook. For a poteto-style delegate use `delegate_task` and instruct it to read `<pstack>/agents/poteto-agent.md` and `<pstack>/skills/poteto-mode/SKILL.md`; pass both absolute pack/models paths and resolved role lines.

## Pick a skill

The default answer is `$pstack:poteto-mode`, which runs most of the others when its steps need them. Name a skill directly when the user wants more or less of something than the playbook gives. Read the skill before you recommend it, and give one example prompt.

| The user wants to | Skill |
|---|---|
| Do any non-trivial task with rigor | [`$pstack:poteto-mode`](../poteto-mode/SKILL.md) |
| Check that the agent understood their goal and the problem before it starts | [`$pstack:in-your-own-words`](../in-your-own-words/SKILL.md) |
| Get a prompt rewritten deeper, not bigger, before sending it: what a top professional would add, their raw material and methods, and an outside check. It returns the prompt and doesn't do the task | [`$pstack:sharpen`](../sharpen/SKILL.md) |
| Know how code works now, or where new code should live | [`$pstack:how`](../how/SKILL.md) |
| Know why code is shaped this way, or where a number came from | [`$pstack:why`](../why/SKILL.md) |
| Understand a change or subsystem, explained plainly | [`$pstack:teach`](../teach/SKILL.md) |
| Catch up on their own recent work on a topic | [`$pstack:recall`](../recall/SKILL.md) |
| Catch up on what changed in this chat since their last message, in plain words and small visuals, with every item waiting on them listed and decidable from the reply alone | [`$pstack:ketchup`](../ketchup/SKILL.md) |
| Catch up like `$pstack:ketchup`, in a short silent video of slides, with the waiting calls as text under it | [`$pstack:ketchup-video`](../ketchup-video/SKILL.md) |
| Know what a small diff could break outside itself | [`$pstack:blast-radius`](../blast-radius/SKILL.md) |
| Settle types and module shape before code that crosses a function boundary | [`$pstack:architect`](../architect/SKILL.md) |
| Get several attempts at one brief, merged into the best one | [`$pstack:arena`](../arena/SKILL.md) |
| Run parallel checks over slices, or race workers, as isolated workers | [`$pstack:swarm`](../swarm/SKILL.md) |
| Have different models review a diff and try to break it | [`$pstack:interrogate`](../interrogate/SKILL.md) |
| Fix a bug test-first when a cheap local test exists | [`$pstack:tdd`](../tdd/SKILL.md) |
| Apply TypeScript rules to `.ts` or `.tsx` work | [`$pstack:typescript-best-practices`](../typescript-best-practices/SKILL.md) |
| Strip comments before review, using a reviewer that didn't write them | [`$pstack:no-comments`](../no-comments/SKILL.md) |
| Clean AI tells out of prose | [`$pstack:unslop`](../unslop/SKILL.md) |
| Write docs, an RFC, a README, a PR description, or a commit message to a standard | [`$pstack:technical-writing`](../technical-writing/SKILL.md) |
| Hear the last reply again in plain words | [`$pstack:bro`](../bro/SKILL.md) |
| Give agents a scripted way to drive the app and prove behavior | [`$pstack:create-verification-skill`](../create-verification-skill/SKILL.md) |
| Bring a verification skill and its feature map back in line with the app | [`$pstack:maintain-verification-skill`](../maintain-verification-skill/SKILL.md) |
| Formally verify a race, invariant, or other property that tests rarely reach | [`$pstack:create-formal-verification-skill`](../create-formal-verification-skill/SKILL.md) |
| Bring a formal verification back in line after the code it covers changed, and learn whether a failure is drift or a bug | [`$pstack:maintain-formal-verification-skill`](../maintain-formal-verification-skill/SKILL.md) |
| Show a PM or designer what the user sees as a chart checked by a model, with each bug drawn as a numbered path, turn an agreed chart into a TLA+ skeleton, or audit the code against its TLA+ spec | [`$pstack:statechart`](../statechart/SKILL.md) |
| Vet a performance number before reporting or acting on it | [`$pstack:benchmark-checklist`](../benchmark-checklist/SKILL.md) |
| Run a large or cross-cutting change, or one to review after stepping away | [`$pstack:figure-it-out`](../figure-it-out/SKILL.md) |
| Keep a decision log during a run, and review it afterward | [`$pstack:show-me-your-work`](../show-me-your-work/SKILL.md) |
| Pick a model for each role and a reasoning budget | [`$pstack:setup-pstack`](../setup-pstack/SKILL.md) |
| Turn their own working habits into a personal mode skill | [`$pstack:automate-me`](../automate-me/SKILL.md) |
| Turn what a finished task taught into skill edits | [`$pstack:reflect`](../reflect/SKILL.md) |
| Stop agents from repeating the same mistakes in this repo | [`$pstack:correct`](../correct/SKILL.md) |
| Build a page whose buttons wake a Grok Bot over a webhook | [`$pstack:make-bot-ui`](../make-bot-ui/SKILL.md) |
| Find their way around pstack | `$pstack:poteto-help` |

If a skill directory next to this one is missing from the table, read its frontmatter and route by its description. The `principle-*` directories are covered under principles below.

Close calls:

- `$pstack:how` explains what the code does. `$pstack:why` explains the reasons. `$pstack:teach` runs one or both and explains the result plainly.
- `$pstack:arena` gives every worker the same brief and merges the best parts. `$pstack:swarm` splits work into slices or a race and returns one report.
- `$pstack:architect` implements right after it settles the design. Add "with checkpoint" to review the design before it writes code.
- `$pstack:interrogate` reviews the diff. `$pstack:blast-radius` looks for breakage outside the diff and proves the one fact that makes the change safe.
- `$pstack:recall` rebuilds context across recent chats. `$pstack:ketchup` covers only this chat since the user's last message. Resuming one specific chat or branch is the Session pickup playbook.
- `$pstack:figure-it-out` designs one rigorous run. The Orchestrate playbook runs a program that spans days and many PRs. The Autonomous run playbook drives one task to a finish condition.

Not in pstack:

- `a code simplification pass`, the shell, and the browser or device tools ship in the session tools.
- `schedule_task` supplies timed wakes. `watch_pull_request` supplies PR-event wakes. Use `skill-creator` when available, otherwise write Agent Skills files directly.
- pstack has no `/orchestrate` skill. Orchestrate is a `$pstack:poteto-mode` playbook. If the slash menu shows `/orchestrate`, another plugin provides it.

## Playbooks and principles

Playbooks are step lists inside `$pstack:poteto-mode`, not skills, so they have no slash command. Inside `$pstack:poteto-mode`, describing the task picks one, and these phrases name one directly:

- "babysit this pr" or "check on pr 123" runs Babysit. It drives the PR to merge-ready and stops there. It doesn't merge unless the user asks to merge, land, or ship.
- "land the stack" runs Shipping.
- "take over this branch" runs Session pickup.
- "pause safely" runs Pause safely.
- "full autopilot on this queue" runs Autopilot-full. "stack them, don't ship" runs Autopilot-stack.
- "run the eval playbook" runs Eval.

Use `schedule_task` for timed work and `watch_pull_request` for PR events. Use `skill-creator` when available, otherwise write the Agent Skills folder directly.

Principles are one-rule skills that `$pstack:poteto-mode` reads and cites in its replies. The user rarely invokes one. They steer with the names instead, as in "apply prove it works. show me the real output." Selecting `$pstack:principle-<name>` still loads one on demand. [Guide page 8](../../docs/guide/08-principles.md) lists them.

## Fix a run that went wrong

| Symptom | Fix |
|---|---|
| The mode stopped applying after a few turns | It was started with Enter. Start it as a task instruction, or start each task with `$pstack:poteto-mode`. |
| A question got treated as the next step of the last task | Say "new task", or say the turn doesn't need the mode. |
| A new model choice had no effect | The models file applies on the next pstack invocation. Invoke the skill again. |
| Runs cost more than expected | See the cost paragraph under Get set up. |
| A skill didn't load on its own | Only `$pstack:setup-pstack` loads from the user's words. The others load when the user types them or when `$pstack:poteto-mode` runs them, and it doesn't run every skill. |
| Parallel agents overwrote each other | Give each agent its own worktree, or run them as isolated workers, which each get their own machine. |
| An overnight run moved but finished nothing | `schedule_task` needs a check that can pass or fail, not a duration. See [guide page 7](../../docs/guide/07-overnight.md). |
| The reply claims success from a green build | Ask for the real command, flow, stored value, or profile. That's the prove-it-works principle. |

For a run that drifts, [`references/prompting.md`](references/prompting.md) has one-line steers. [Guide page 10](../../docs/guide/10-recipes-and-pitfalls.md) has more pitfalls and the recipes worth copying.

## Make pstack my own

- [`$pstack:automate-me`](../automate-me/SKILL.md) drafts a personal mode skill from the user's own history, to use alongside `$pstack:poteto-mode`.
- [`$pstack:reflect`](../reflect/SKILL.md) after a session turns its lessons into skill edits the user approves.
- `$pstack:poteto-mode write a skill for <workflow>` runs the authoring playbook. The eval playbook tests a skill change blind.
- Fix a misbehaving skill in its own PR, not inside the feature work where it went wrong.

[Guide page 9](../../docs/guide/09-make-it-yours.md) covers each of these.

## Reply

Lead with the answer. Give at most one example prompt in a code block, adapted from [`references/recipes.md`](references/recipes.md) when one fits, then the link to that file. Keep it short unless the user asked for the whole map.

## Custom maintainer modes

For named GitHub accounts, read [automate-maintainer](../automate-maintainer/SKILL.md). For discovering the active core and capturing its conventions, read [automate-team](../automate-team/SKILL.md). Both preserve evidence visibility, individual attribution, disagreements, and held-out evaluation.