P3 help

Answer the user's question about p3-stack, 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 p3-stack run spends real tokens, so let them send the prompt.

A message that asks for work, such as "use p3-stack to fix this bug", is not a help question. Read p3-mode, do the work under it, and mention once that invoking /p3-mode keeps the work in this style.

This file maps questions to the skills and playbooks 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 are repo-relative, so give the user the file's public copy: https://github.com/uzairansaruzi/p3-stack/blob/main/ 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 /p3-mode, pick a skill for a situation, fix a run that went wrong, or make p3-stack my own.

Check the state that changes the answer, and mention it only when it does. No p3-models.md means /setup-p3 hasn't run for this user, so every role uses its default model. 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.

Get set up

1. Install by cloning the repo and running ./install.sh. It links every skill into ~/.agents/skills/, where T3 Code reads skills; ./install.sh --project /path/to/repo targets a project's .agents/skills/ instead.
2. Run /setup-p3. It asks for a reasoning budget, maps a model to each role, and writes p3-models.md. The file applies to new sessions.
3. Start a real task with /p3-mode, a goal, and a check that can pass or fail.