realsid08/p3stack/poteto-help

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`, do the work under it.

This file maps questions to the skills 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 skills directory, which the user may not be able to open, so give the user the file's public copy: https://github.com/RealSid08/p3stack/blob/main/skills/ followed by its path from the skills directory.

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 /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:

• No ~/.agents/pstack-models.md (and no .agents/pstack-models.md in the repository) means /setup-pstack hasn't run for this user, so every role uses its default model.
• No t3-code tools in the session means pstack is running outside T3 Code. The workflow skills need T3 Code's orchestrator to spawn subagents, so say so.
• No verify-* skill or other app harness in the project means agents have no scripted way to drive the app. Mention /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 /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 /maintain-formal-verification-skill if the question touches that code.

When the model 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 /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 /setup-pstack.

Get set up

1. Install the skills per the repository README, into ~/.agents/skills with ~/.claude/skills links, so every T3 Code provider sees them.
2. Run `/setup-pstack`. It asks for a reasoning budget, maps a model from T3 Code's catalog to each role, and writes ~/.agents/pstack-models.md. New runs read it. 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 /poteto-mode, a goal, and a check that can pass or fail.

Installing changes nothing until the user invokes a skill. Only /setup-pstack loads from the user's words. The README has the details. Offer to word their first prompt with them, per `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 /setup-pstack and pick a smaller budget or cheaper models. A role set to inherit-parent runs on the thread's own model, which saves tokens when the thread runs on a cheaper model. A shorter panel list runs fewer subagents, one for each entry. Save /poteto-mode for work that needs rigor.

This edition, p3stack, is pstack built for T3 Code. Its skills use the Agent Skills format, so any provider T3 Code runs can read them. The workflow skills, including /poteto-mode, /how, /why, and /teach, spawn subagents with per-role models through T3 Code's delegate_task, so outside T3 Code those parts run on the parent model only.

Start a task with /poteto-mode

/poteto-mode matches the task to a playbook, copies the playbook's steps into the todo list, 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` before you help word one. `references/recipes.md` has examples.

/poteto-mode attaches the skill to one message, and it fades as the thread moves on. Start each new task with /poteto-mode. Mid-thread, "new task" makes the mode match a fresh playbook. /poteto-mode already briefs the subagents its playbook steps spawn as poteto-agents. To get the same style from a subagent of your own, open its delegate_task brief with the preamble in `references/agents/poteto-agent.md`.

Pick a skill

The default answer is /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.

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:

• /how explains what the code does. /why explains the reasons. /teach runs one or both and explains the result plainly.
• /arena gives every worker the same brief and merges the best parts. /swarm splits work into slices or a race and returns one report.
• /architect implements right after it settles the design. Add "with checkpoint" to review the design before it writes code.
• /interrogate reviews the diff. /blast-radius looks for breakage outside the diff and proves the one fact that makes the change safe.
• /recall rebuilds context across recent chats. /ketchup covers only this chat since the user's last message. Resuming one specific chat or branch is the Session pickup playbook.
• /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:

• Driving the real app (the "control skill") uses a project verify-* skill or T3 Code's preview and device tools. See Driving the real app in `t3-runtime.md`.
• Timed wake-ups use T3 Code's schedule_task and watch_pull_request, not a pstack skill.
• pstack has no /orchestrate skill. Orchestrate is a /poteto-mode playbook. If the slash menu shows /orchestrate, another plugin provides it.

Playbooks and principles

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