diff --git a/README.md b/README.md index 1505b72e..dcf0d431 100644 --- a/README.md +++ b/README.md @@ -5,7 +5,7 @@

ci license: MIT - upstream pstack 0.15.17 + upstream pstack 0.15.18 release

diff --git a/changes/pstack-t3%2Fd174.md b/changes/pstack-t3%2Fd174.md new file mode 100644 index 00000000..c35e3604 --- /dev/null +++ b/changes/pstack-t3%2Fd174.md @@ -0,0 +1 @@ +- Synced to upstream pstack 0.15.18 at ea32d9562a1c9f077d7cdd3be53d07383eb18866. Ketchup stays read-only except for visuals made from what the agent already has, shows each action item as a before and after, uses a screenshot or a video when the change is visible, uses another artifact such as a table of numbers, a diff, or a diagram otherwise, and prefers a table, a Mermaid diagram, a chart, or a generated image to dense prose. diff --git a/skills/ketchup/SKILL.md b/skills/ketchup/SKILL.md index d7fa4477..5d32ba26 100644 --- a/skills/ketchup/SKILL.md +++ b/skills/ketchup/SKILL.md @@ -9,7 +9,7 @@ Catch the user up on everything in this chat since the last message they wrote b ## Gather what changed -Keep this turn read-only. Collect your own work since that message, reports from subagents, and messages from anyone else in this chat. Check the current state of each PR, CI run, or agent this chat touched. Say which are still running and which you could not check. +Keep this turn read-only, except for visuals you make for the reply from what you already have. Do not change code, start an app or a job, or post anything to make them. Collect your own work since that message, reports from subagents, and messages from anyone else in this chat. Check the current state of each PR, CI run, or agent this chat touched. Say which are still running and which you could not check. An action item is a decision or step only the user can take, such as a product choice, an approval, an irreversible action, or access you lack. Include any still waiting on the user, even one raised before their last message. Work you can still do yourself is not an action item. @@ -20,3 +20,7 @@ Open with one sentence that says how many action items there are, or that there Then say what happened, most important first. Give each result and what it means for the user. Skip steps that changed nothing. Name in one line any work left that you can do yourself. Then give each action item a short executive summary. Cover the decision to make, why it matters now, the options and what each costs, your recommendation, and what happens if the user does not answer. If you do not know a part, say so instead of guessing. Link to the detail when there is one, and write the summary so the user can decide without opening it. + +Show each action item as a before and after, side by side. For a choice, put the current state beside each option, or the options alone when there is no current state. Use screenshots or a video when the change is visible. Otherwise use another artifact, such as a table of numbers, a diff, or a diagram. If no visual exists yet, make one. If you cannot, say plainly that none exists. Never invent a number, and never draw or generate a picture of a screen you did not capture. Link only artifacts that exist. + +Prefer visuals to dense prose. Use a table, a Mermaid diagram, a chart, or a generated image. diff --git a/upstream.json b/upstream.json index 19a549cf..ab7958f0 100644 --- a/upstream.json +++ b/upstream.json @@ -1,8 +1,8 @@ { "repository": "https://github.com/cursor/plugins.git", - "commit": "978ca6e9c0e012047cd5058b8e829240336e704e", + "commit": "ea32d9562a1c9f077d7cdd3be53d07383eb18866", "path": "pstack", - "version": "0.15.17", + "version": "0.15.18", "license": "MIT", "author": "Lauren Tan" } diff --git a/vendor/pstack/.cursor-plugin/plugin.json b/vendor/pstack/.cursor-plugin/plugin.json index 7d786382..5f95e747 100644 --- a/vendor/pstack/.cursor-plugin/plugin.json +++ b/vendor/pstack/.cursor-plugin/plugin.json @@ -1,7 +1,7 @@ { "name": "pstack", "displayName": "pstack", - "version": "0.15.17", + "version": "0.15.18", "description": "if you want to go fast, go deep first. pstack helps you write less, but higher quality code. rigorous agent workflows you can parallelize with confidence.", "author": { "name": "Lauren Tan" diff --git a/vendor/pstack/skills/ketchup/SKILL.md b/vendor/pstack/skills/ketchup/SKILL.md index f00fccbc..1c63f43f 100644 --- a/vendor/pstack/skills/ketchup/SKILL.md +++ b/vendor/pstack/skills/ketchup/SKILL.md @@ -10,7 +10,7 @@ Catch the user up on everything in this chat since the last message they wrote b ## Gather what changed -Keep this turn read-only. Collect your own work since that message, reports from subagents, and messages from anyone else in this chat. Check the current state of each PR, CI run, or agent this chat touched. Say which are still running and which you could not check. +Keep this turn read-only, except for visuals you make for the reply from what you already have. Do not change code, start an app or a job, or post anything to make them. Collect your own work since that message, reports from subagents, and messages from anyone else in this chat. Check the current state of each PR, CI run, or agent this chat touched. Say which are still running and which you could not check. An action item is a decision or step only the user can take, such as a product choice, an approval, an irreversible action, or access you lack. Include any still waiting on the user, even one raised before their last message. Work you can still do yourself is not an action item. @@ -21,3 +21,7 @@ Open with one sentence that says how many action items there are, or that there Then say what happened, most important first. Give each result and what it means for the user. Skip steps that changed nothing. Name in one line any work left that you can do yourself. Then give each action item a short executive summary. Cover the decision to make, why it matters now, the options and what each costs, your recommendation, and what happens if the user does not answer. If you do not know a part, say so instead of guessing. Link to the detail when there is one, and write the summary so the user can decide without opening it. + +Show each action item as a before and after, side by side. For a choice, put the current state beside each option, or the options alone when there is no current state. Use screenshots or a video when the change is visible. Otherwise use another artifact, such as a table of numbers, a diff, or a diagram. If no visual exists yet, make one. If you cannot, say plainly that none exists. Never invent a number, and never draw or generate a picture of a screen you did not capture. Link only artifacts that exist. + +Prefer visuals to dense prose. Use a table, a Mermaid diagram, a chart, or a generated image.