From 3b3c015322d9650b097770460b80dcc01e1f60a6 Mon Sep 17 00:00:00 2001 From: Kaitian Xie Date: Wed, 18 Nov 2026 18:58:17 +0800 Subject: [PATCH 1/2] fix: give Codex users working pstack install commands --- .agents/skills/poteto-help/SKILL.md | 22 ++++++++++++++-------- 1 file changed, 14 insertions(+), 8 deletions(-) diff --git a/.agents/skills/poteto-help/SKILL.md b/.agents/skills/poteto-help/SKILL.md index 42ec373..f54b8fc 100644 --- a/.agents/skills/poteto-help/SKILL.md +++ b/.agents/skills/poteto-help/SKILL.md @@ -25,24 +25,30 @@ Infer the need from the message and the conversation. A named situation, such as Check the state that changes the answer, and mention it only when it does: -- No `.agents/pstack-models.md` or `~/.agents/pstack-models.md` means `/setup-pstack` hasn't run for this user, so every role uses its default model. +- No `.agents/pstack-models.md` or `~/.agents/pstack-models.md` means `$pstack:setup-pstack` 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. - 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 rule 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`. +- 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. Install with `/add-plugin pstack` in chat, or from Customize in the sidebar. -2. Run [`/setup-pstack`](../setup-pstack/SKILL.md). It asks for a reasoning budget, maps a model to each role, and writes a rule. The rule applies to new chats. 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. +1. Run these commands in a terminal. -Installing changes nothing until the user invokes a skill. Only `/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). + ```sh + codex plugin marketplace add pstack-ports/codex-pstack + codex plugin add pstack@codex-pstack + ``` -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 `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 `/poteto-mode` for work that needs rigor. +2. Start a new Codex session in your project and run [`$pstack:setup-pstack`](../setup-pstack/SKILL.md). It asks for a reasoning budget, maps a model to each role, and writes a rule. The rule applies to new chats. 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. + +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. This port runs in Codex. Use `$pstack:poteto-mode` or `$pstack:setup-pstack`; skills live only in `.agents/skills/`. Read the local README for installation and the Codex adapter for host capabilities. From bf582882e9c1ba3a483ad07d786cac8adb6d4061 Mon Sep 17 00:00:00 2001 From: Cursor Agent Date: Wed, 18 Nov 2026 11:07:00 +0000 Subject: [PATCH 2/2] fix: restore the upstream sentence on which skill loads from words Installing still changes nothing until a skill is invoked, and only $pstack:setup-pstack loads from the user's words. Co-authored-by: Kaitian Xie --- .agents/skills/poteto-help/SKILL.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.agents/skills/poteto-help/SKILL.md b/.agents/skills/poteto-help/SKILL.md index f54b8fc..094dae7 100644 --- a/.agents/skills/poteto-help/SKILL.md +++ b/.agents/skills/poteto-help/SKILL.md @@ -46,7 +46,7 @@ When the model rule is missing and it matters, ask whether the user wants to pic 2. Start a new Codex session in your project and run [`$pstack:setup-pstack`](../setup-pstack/SKILL.md). It asks for a reasoning budget, maps a model to each role, and writes a rule. The rule applies to new chats. 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. -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). +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.