Skip to content
  1. How-to
  2. Prompts
  3. Not sure which skill to use

Not sure which skill to use

In one lineNot sure? Use /pstack:poteto-mode. Name a specific skill only when you want more or less checking than it gives.

2 minutes to look upFor: You have something to do and don't know which command to typeFull guide step 3: Your first task

Not sure? Use /pstack:poteto-mode

When you’re not sure, the answer is almost always /pstack:poteto-mode. You say the goal and what “done” means. It picks an approach (a playbook) and calls skills like /pstack:how and /pstack:architect itself when needed.

Name a skill directly only when you want more or less than it gives. For example, to understand code without it changing anything, use /pstack:how.

Except for /pstack:setup-pstack, every skill runs only when you type it yourself.

I want to… → use this

  • Understand code: how it works now /pstack:how; why it was done this way /pstack:why; explain it fully /pstack:teach
  • Get aligned before starting: check it understood /pstack:in-your-own-words; make the prompt more precise /pstack:sharpen
  • Pick up where you were: across conversations /pstack:recall; what changed in this one /pstack:ketchup
  • Settle a design: structure first /pstack:architect; several takes on one task /pstack:arena; check many things separately /pstack:swarm
  • Check: several models pick at it /pstack:interrogate; what else might break /pstack:blast-radius; failing test first /pstack:tdd; check performance numbers /pstack:benchmark-checklist; let the AI drive your app /pstack:create-verification-skill
  • Writing: remove the AI feel /pstack:unslop; docs and PR descriptions /pstack:technical-writing; say it in plain words /pstack:bro
  • Big jobs and long runs: something very big /pstack:figure-it-out; keep a decision record /pstack:show-me-your-work; stop a repeated mistake /pstack:correct
  • Setup: pick models, set the budget /pstack:setup-pstack; make a mode of your own /pstack:automate-me

For details and example prompts for each skill, see Skills reference.

Still not sure? Ask /pstack:poteto-help

It answers, gives you a prompt you can send as-is, and links the source. It doesn’t start work. Whether to send the prompt is up to you.

Ask it to do the work, and it will

If you tell it something like “use pstack to fix this bug,” it goes straight to work under /pstack:poteto-mode’s rules.

Pairs people mix up

  • /pstack:arena and /pstack:swarm: /pstack:arena does one task several times, picks the best, and grafts in good ideas from the rest. /pstack:swarm splits a pile of work, does it separately, and merges one report.
  • /pstack:how, /pstack:why, /pstack:teach: /pstack:how explains what the code does, /pstack:why explains why it’s that way, and /pstack:teach runs one or both and then explains it fully.
  • /pstack:interrogate and /pstack:blast-radius: the first reviews the change itself. The second finds what might break outside the change.
  • /pstack:recall and /pstack:ketchup: the first finds your progress across conversations. The second covers only changes in this one.
  • /pstack:architect: starts writing as soon as the design is settled. To see the design first, say “with checkpoint.”

How much design a job deserves

Most changes need none. Step up by size:

  • Done writing, but unsure: just /pstack:interrogate.
  • One standalone choice (naming, format, algorithm): /pstack:arena directly.
  • The change crosses function boundaries: /pstack:architect.
  • A question one run can answer (layout, timing): build a prototype instead of arguing.
  • Disputed and expensive to change: /pstack:architect first, then /pstack:interrogate before shipping.
  • Spans several PRs: once the design is settled, write the plan.

/pstack:poteto-mode already climbs this ladder on its own.

Don’t order skills in your prompt

Don't write this
/pstack:poteto-mode first use /pstack:how, then /pstack:architect, then /pstack:arena, and finally /pstack:interrogate, and help me add an export feature.

It already has the order worked out. Ordering it again tends to scramble or drop steps. State the goal and requirements instead:

Write this
/pstack:poteto-mode add a CSV export. The existing JSON export must stay byte-for-byte identical. Verify both.

Name a skill only to change one default choice, like “use /pstack:arena with 5 options this time.”

Stuck?

I typed /pstack:how, and it didn't go on to fix anything.

That’s right. /pstack:how only explains. It doesn’t touch code. Once you understand it, use /pstack:poteto-mode to say what you want done.

What I want to do isn't in the list.

Hand it to /pstack:poteto-mode. When no ready-made approach fits, it passes the job to /pstack:figure-it-out to design one on the spot.

There's an /orchestrate in the slash menu. Is that pstack's?

No. Orchestrate is one of the approaches inside /pstack:poteto-mode. The one in the menu comes from another plugin.

An unofficial beginner's guide to pstack, not its official docs. pstack is made by poteto; the official repo is the source of truth for commands and behavior. The original guide source is on GitHub.

Hosted by airali. Adapted from Xiaoxiaodong's MIT-licensed guide.